Saving Metadata to large PSD file problems

LR 2.1
XP Pro SP 3
4GB Ram
Dual Dual-core 3.6 Processsors (HP workstation)
Dual Dual-channel FC Arrays (4G/min)
LR 2.1 is consistantly failing to export metadata information to PSD files over 200Meg. Most of these files are layered.
Stuff under that seems AOK.
Any thoughts.

How are you saving the metadata - automatically or manually?

Similar Messages

Bridge locks briefly when updating metadata on large PSD files

When updating metadata on a large PSD file, Bridge "locks" up for a brief period of time. This is apparently when it's rewriting that large PSD file to update the metadata. I'd like to be able to use Bridge in an uninterrupted fashion while metadata is updated in the background. This normally works for smaller files, just not on large PSD files. You can reproduce this easily by just adding a keyword to a couple 100MB PSD files.
--John

Chris,
How large are the PSD files? If they are over 400MB, I think I know what's wrong.
Bridge has a file-size preference, and won't process files that are larger than your setting. You'll find this preference on the Thumbnails panel in the Bridge Preferences dialog. The default is 400MB--try bumping it up to a size larger than your largest PSD and then purge the cache for the folder containing those PSDs.
If that does not work, I'd like to have a copy of one of the PSDs that is not working for you.
-David Franzen
Quality Engineer,
Adobe Systems, Inc.

I created an image in Photoshop and saved it as the PSD file. Now when I try and open it it says it is not compatible with my version. How could this be when I created it in this version?

I created an image in Photoshop and saved it as the PSD file. Now when I try and open it it says it is not compatible with my version. How could this be when I created it in this version?

That depends on why it won't open. Most of the time it means the file is corrupted and unlikely to be recovered. If you saved it right after adding or copying a LOT of layers - then it might just be the layer limit and we can attempt to recover it.

Adding/Reading XMP Metadata in a psd file

Hi,
I'm having some troubles to understand how to add and read XMP metadata on a psd file. I followed the Panel developer guide tutorial, and try to look on the internet for some answers, but I'm still stuck ...
Here is the simple example I'm trying to make (using part of the code from the panel developer guide) :
     The function loads the XMP Script Library.
     @returns True if the XMP Script Library was loaded successfully.
     @type Boolean
function loadXMPLibrary(){
     if ( !ExternalObject.AdobeXMPScript ){
          try{
               ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
          }catch (e){
               alert("Can't load XMP Script Library");
               return false;
     return true;
     The function unloads the XMP Script Library.
function unloadXMPLibrary(){
     if( ExternalObject.AdobeXMPScript ) {
          try{
               ExternalObject.AdobeXMPScript.unload();
               ExternalObject.AdobeXMPScript = undefined;
          }catch (e){
               alert("Can't unload XMP Script Library");
    Try to put a new property into the metadata
if( app.activeDocument || !loadXMPLibrary()){
    var xmp = new XMPMeta(activeDocument.xmpMetadata.rawData);
    xmp.setProperty( XMPConst.NS_EXIF, "myProperty", "test" );
    activeDocument.xmpMetadata.rawData = xmp.serialize();
    unloadXMPLibrary();
    Window.alert(activeDocument.xmpMetadata.rawData);
I don't really know where I'm wrong, could you help me please ?
Thanks,
Julien

Rather mess with EXIF and Dublin Core namespaces, wouldn't it be better to create your own?
IE:
#target photoshop
addtoMeta();
function addtoMeta(){
if(!documents.length) return;
if (ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject("lib:AdobeXMPScript");
var xmp = new XMPMeta( activeDocument.xmpMetadata.rawData);
var myNamespace = "http://my.fantastic.newspace/";
var myPrefix = "nsfns:";
XMPMeta.registerNamespace(myNamespace, myPrefix);
xmp.setProperty(myNamespace, "myProperty", "A Test String");
app.activeDocument.xmpMetadata.rawData = xmp.serialize();

Problem opening large PSD files

Helo, We have 5 designers sharing design files across a windows network. Everyone is running photoshop CS6 cloud subscriptions (which have auto updated to 13.0.1).
The team have created and opened PSD files fine since July. Over the last 3 weeks we have had 5 files so far become unopenable - we get the message: “could not complete your request because the file is not compatible with this version”. Could it be that they are too large? The problem files are larger than the rest at around the 1GB mark. We are running HPZ210 PCs with Windows 7, solid state drives for the software, regular HDD for the data, and 16 GB Ram. One file at least was housed on a hard drive as well as the server and neither the local or network version of the file opens so it doesn’t seem to be a server issue. Five people on different subscriptions and computers have tried opening the files to no avail. Files were working ok one day, then not opening the next. Anyone know of any possible fixes, or whether the files are just too large?
cheers, Liz

Hey Curt, thanks for replying so quickly. I found the guff below re PSB, will check out this and the pixel counts with the team and post back.
cheers, liz
PSB is a file extension for an image file used by Adobe Photoshop. PSB files are a large document format similar to a PSD file but for a larger image size. The largest image size supported by a PSD file is 30,000 by 30,000 pixels.
PSD file support has to be enabled in Photoshop's Preferences pane first, then PSB files can be saved at an image size up to 300,000 by 300,000 pixels. PSB files can be opened by Adobe PhotoShop CS or later. PSB files can be exported as TIFF for compatibility with other software.

Photoshop CS6 - Spot channels are not saved correctly in the psd files.

Hi,
I'm using Photoshop CS6 and something happent a few days ago....some Windows or Adobe update messed up everything...I don't know...
Here's how things are.
If I add to an image a couple of new spot channels (any Pantone color) and remove the informations from the CMYK channels (or not-the problem it's there anyway), I should have an image with 6 color plates (CMYK and the 2 Pantone). It doesn't happened anymore...
I'm using Corel to print the files and the previous saved files are fine, I have all the Spot colors there. Now, If I edit any file I've worked on before, and save it again, the spot colors dissapear when I'm importing the psd file in my Corel document. And if there is no information on the CMYK channels, I'm getting a blank image...
I hope someone will give me some ideas because I don't know what to do anymore...
Codrut

Right. It's not reading these new saved files correctly. The old ones are fine.
I forgot to mention one thing. I've got this CS6 as an upgrade and I still have the CS5 one running on the same computer. The CS5 version does the same thing...
Today I tryed again to open a PSD (CS6) with another CS5 version from another computer and came with an error message "Could not complete your request because the specified color book cannot be found". And the file didn't opened....
Who messed up my color book and how can I fix it?

Large PSD file overwritten with a PDF file

Hi everyone,
I've been searching google for this for a while but I can't find an answer.
Ok, so I'm working with a large PSD (100+ layers, over 170MB). I wan't to preview it as a PDF. I click Save As ... and I make a new file on the desktop. I minimize Photoshop, go to desktop and open the PDF. Ok everything's ok. I go back to photoshop (just maximize it). I work work work .... Ctrl+S every once in a while ... and I suddenly realize that the file I'm working on has changed its name from project2.psd to project2.pdf (I see this in the top bar of the window). I minimize photoshop, go to the folder where my psd file is stored and I check it for weight -> it's now 24MB instead of 170MB. Ok, now I'm stressed and I go crazy. Istead of going back in history I decide to Overwrite my original project2 (which is now a pdf as the windows explorere shows ... [oh yeah, and the pdf I've created on the desktop is still there as a totally separate file]) with the project I have currently opened in photoshop (I still have layers in the layers pallete and everything, it's just the photoshop shows the name of the file in the top bar "project2.pdf"). I do that. Now I close all the projects opened in photoshop (I guess that's the moment I really screwed up) - though I don't close the program itself if that matters at all - and I reopen my project2.psd.
Yes, it opens as a PSD ..... but it's flatten. No layers.
God I'm so angry with myself now.
I have no idea why after creating a new pdf file on the desktop the whole project I was still working with turned into a PDF file.
Is there any home-made cheap solution to this? I wan't to get my 170MB 100+ layers file
Does Vista store some temp files anywhere? I suppose it won't be there.
Sorry for being so emotional about all this but I'm really screwed if I don't get my original file back.
PS. I've found a file called Photoshop Temp631890 in the Temp directory. Can't open it with PS. Is there anything I can do with it?
Thank you in advance,
Auror

Much thanks Ronald .... yes Robert you too.
Sorry to answer this topic with such a delay. I've been busy finishing this project. Not re-doing the whole thing thank God!
Ok so I know that if I overwrite a file it's lost.
I didn't loose everything 'couse I was able to recover an earlier copy that was erased. Some data-recovery software found it on my drive and was able to recover it. Moreover while I was recovering it I remembered that I've left a copy of my PSD file on my clients FTP server 2 days earlier. I did loose a couple of hours of work but all wasn't lost.
I could swear to god I saved my PSD "AS A" PDF and somehow both files turned into PDFs. Well ... s**t happens right?
gonna be more carefull next time.
Thakns for everything.
Auror

Help, Invalid .psd file problem.

Hello, i will try to be clear with my problem:
For the past three days i have been working on a drawing in photoshop CS6.
I was working on it this morning and it went just fine. I save it and when i quite the program a message appeared saying Photoshop has stoped working.
The file was still in the place i saved it, everything seemed ok so i took a brake. A few hours later i tried to open it again and a message apeared saying Photoshop could not open the file because it is not a valid Photoshop file.
I have tried to open previous .psd files and they worked just fine. I fear that the file might be damaged, but i really hope i'm wrong.
If you have a solution i would be more than glad to hear it.
(I work with a Sony and Windows 8)

When working on even a mildly complex Image, I use a combo of Save, Save_As and Save_As_a_Copy, along the way. They have similarities, but also important differences.
After a complex bit of work, I will do the Save_As (keeping that a Layered PSD), and incrementing my file's name, then at the end of the day, do a Save_As_a_Copy, and often to another HDD. For intricate Images, I might end up with 30 versions, as I progress.
Along the way, I frequently use Save (Ctrl+S).
Good luck, and sorry about that file. I've sort of been there, as my computer had a major, systemic crash, while Saving a triple-truck pano HDR, with dozens of Layers. Fortunately, I only lost about 1 hour of work, because I had my Save_As. Took much longer to straighten out my poor computer.
Hunt

Large Data file problem in Oracle 8.1.7 and RedHat 6.2EE

I've installed the RedHat 6.2EE (Enterprise
Edition Optimized for Oracle8i) and Oracle
EE 8.1.7. I am able to create very large file
( > 2GB) using standard commands, such as
'cat', 'dd', .... However, when I create a
large data file in Oracle, I get the
following error messages:
create tablespace ts datafile '/data/u1/db1/data1.dbf' size 10000M autoextend off
extent management local autoallocate;
create tablespace ts datafile '/data/u1/db1/data1.dbf' size 10000M autoextend off
ERROR at line 1:
ORA-19502: write error on file "/data/u1/db1/data1.dbf", blockno 231425
(blocksize=8192)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
Additional information: 231425
Additional information: 64
Additional information: 231425
Do anyone know what's wrong?
Thanks
david

I've finally solved it!
I downloaded the following jre from blackdown:
jre118_v3-glibc-2.1.3-DYNMOTIF.tar.bz2
It's the only one that seems to work (and god, have I tried them all!)
I've no idea what the DYNMOTIF means (apart from being something to do with Motif - but you don't have to be a linux guru to work that out ;)) - but, hell, it works.
And after sitting in front of this machine for 3 days trying to deal with Oracle's, frankly PATHETIC install, that's so full of holes and bugs, that's all I care about..
The one bundled with Oracle 8.1.7 doesn't work with Linux redhat 6.2EE.
Don't oracle test their software?
Anyway I'm happy now, and I'm leaving this in case anybody else has the same problem.
Thanks for everyone's help.

Very large PSD files created in library ?

When I finish processing a NEF file in Lightroom and send to Photoshop CS3 to make a lens distortion correction then save the revised file as a PSD file, the resulting file size saved to my Lightroom library is more than 5 times the size of my original NEF (11MB-62MB).
This doesn't seem right and really discourages me from using CS3 - or maybe Lightroom (?). Am I doing something wrong ? Is there a work flow that will allow me to use CS3 for corrections not possible in Lightroom without generating such giant files to my library.
In my pre-Lightroom workflow I would import the original NEF to a photo library folder, open the NEF file in Bridge to make raw adjustments, then open in Photoshop to make the distortion corrections, etc, then save as a jpg. The resulting file sizes in my library folder would be 11MB for the original NEF and 3-4MB for the final JPG.
I really prefer sorting, developing and viewing photos in Lightroom rather than Photoshop, but am reluctant to accept an additional 58MB of storage requirement for each photo that requires Photoshop revisions.
Would appreciate any suggestions or ideas !!
NikonD300,MacOS10.4.11,Lightroom1.3.1,PhotoshopCS3

That's normal. A RAW file is usually 12-bit with only one greyscale value at each pixel. There are individual color filters in front of every pixel. This pattern is called a Bayer Mosaic. A RAW converter demosaics this into a picture that has RGB values defined at each pixel. If for example, you have a 10MP camera, your RAW file uncompressed will be at a minimum 15MB, or about 10MB compressed. Now demosaic this into a 16-bit file. This yields 10*3*16/8=60MB uncompressed. Adding compression gets you down to about 30-50MB depending on the complexity of the picture. Nothing you can do about this, but for using 8-bits instead of 16-bits, halving the necessary filesize.

PSD file problem with lighrooom when editing under CS3

Hi - Lets assume i am editing (invoked via LR) a copy of a jpg file under CS3 , say my copy file is now layered (with .PSD) and i hit file save..This PSD file is not automatically imported in LR and stacked with the other jpeg picture..I am doing something wrong here ? Cos this seems to work when saving a copied version of a jpg..

Hmm not sure i have explained thinsg properly.
I am in lightroom
I select a Jpeg picture
I hit Ctrl-e, i then have the choice to either use original or a copy
I select the copy option
the file is loaded in photoshop as filename-edit.jpg
lets say I add layers for example to this picture , the filename i will then be saving is filename-edit.psd
when i close photoshop i was expecting that this psd is stacked along with jpeg and this is not happening...

16bits/channel multilayer psd file problem.

Hi all,
Did someone already know about 16 bits/channel multilayer psd file parsing is different to that of 8 bits/channel multilayer psd file?
as far as I try, it seems 8 bits/channel model, image data is saved in RLE model, but it is quite different in 16 bits/channel,
we could easily find out once we load those two file into memory (with same context, only model changed).
Anyone who know which algorithm may 16 bits/channel multilayer psd taken for saving the layer image data?
Many Thanks!
Jerry Yu

yes, 16 bit/channel can be ZIP/FLATE compressed. (RLE doesn't work well for anything beyond 8 bit/channel)
You can find the details in the Photoshop SDK (you'll have to ask specifically for the PSD documentation).

How to open very large PSD files?

I am unable to open psd file - "could not open file as result will be too long"

PFF! WTF? Why wouldn't Illy CS3 be able to open Illy 1.1 files? That is **RETARDED**. Who at Adobe thinks "Gee, no one would Ever need to open old files any more!"? Some day I'm gonna want to open some old files just for nostalgia, and I'll be using Illy 2025 trying to open an Illy 6 file that I made in college.
If anyone has any input at Adobe, please tell them that we should **always** be able to open older versions of files in new applications. This goes for Ai, InD, PS, Acro, AE.
[/crazy rant]

Saving metadata directly to master file

I have 20,000+ photos (JPEG format) in iPhoto, which I have annotated with creation dates, titles, descriptions, keywords, GPS coordinates, place names, and faces. I wish to liberate myself from iPhoto and Apple, so I would like to transfer the metadata directly into the original/master JPG files, but I want to do that without mucking around with the original images. I was told in an iPhoto discussion topic that Aperture could do this, but I could not figure out how to do it, and the guy then refused to provide instructions.
When I had to add creation dates, I always checked the "Modify original files" box, so I believe that is already in all of the master files. I also believe (and have to accept the fact) that there is no way I will ever be able to retain the place names or faces metadata. So, that leaves the titles, descriptions (captions), keywords, and GPS coordinates.
I can add all of that metadata by exporting from iPhoto, but the option that allows inclusion of metadata also insists on recompressing the image with another pass through lossy JPEG compression. At "Maximum" quality, my ~2.5 MB files balloon to ~6.7 MB (on average). At "High" quality, they remain about the same size, and I suppose it is doubtful that any loss in quality would be minor, it just seems illogical and inelegant to recompress the images just to alter the metadata in the file header. A workaround I have discovered is to do the export, then use ExifTool to extract the metadata and then write it directly to the master file headers without mucking with the image itself. If the freeware ExifTool can do this, it would be nice if iPhoto could do it.
In the other topic linked above, the guy implied that Aperture could export some, a little, a lot, or all of the metadata (whatever I wanted). I did quite a bit of testing, but I could not figure out how to do that. Does anybody here know whether that is possible? He refused to tell me, as things devolved into a meaningless argument about whether iPhoto was "recompressing" images using JPEG when exporting as a JPEG (I claim it does). If I am wrong about that, I would like to correct that.
Below are the highlights of my findings in Aperture from the other topic, which I would like to correct, as well, if I am wrong.
Aperture Original export
Aperture Original export does not seem to alter some images, and it can embed Description and Keywords as IPTC fields. However, it substantially changed the size of some of my images (far more than could be accounted for by adding a tiny bit of metadata), so I am not sure it is really leaving all images untouched. More importantly, it does not seem to embed Title or GPS information. So, it seems like the most useless option.
Aperture Versions export
The Aperture Versions export, unlike the Aperture Original export, does include the GPS information, but, like Aperture Original export, it does not include the Title. And, like iPhoto export, Aperture Versions export modifies the original image, albeit with much lower inflation in file size. This also seems like a relatively useless option.

splinke wrote:
In any event, although the Aperture Original export can apparently embed Description and Keywords metadata in the original/master file when the IPTC option is selected, it does not seem capable of embedding Title or GPS coordinate metadata. So, it does not seem to be useful for my purpose. Am I missing an option somewhere to include all metadata in the export? It seems like this is my best bet, if I can just figure out how to include those other fields in the export.
When you export the original, select the metadata option IPTC4XMP Sidecar file.
In addition to your original Image file, you'll also get an extra file ending .XMP.
This contains all the metadata you're looking for, including others such as the colour label, star rating, etc.
When you import your images to your new software, just make sure you choose software that supports reading the XMP file (it's a pretty common standard).
Andy

Help: .psd file problem

Hello,
I am currently trying to solve an issue I'm having currently with Cs5 in opening a canvas I was working on last night.
Today I tried to open the canvas and found my layers were completely gone. The only layer visable is the background
layer and it is solid black, with a strange red bar at the top.
I am not sure how to solve this problem, any help would be very helpful.
Thanks in advance!
-Matt

There seems to be several users with similar problems with psd saves. By any chance are you using CS5.5?
For now my advice would be to save psd in mulltiple stages, and as tiff also. Increases your odds of having a good file.

Saving Metadata to large PSD file problems

Similar Messages

Maybe you are looking for