Lightroom 2.0 will not export to Photoshop CS3

[_jj_pod_]

OK,

So I downloaded and installed lightroom 2.0 this morning and things are not working well.

System: Macpro 2.8, 8 gb ram, os x 10.5.4, nikon d300 raw files

The problem...

It started with Lightroom not exporting any images to photoshop. Doesn't matter if I try to send 1 or 20, I get a spinning beach ball, then nothing. if photoshop is closed it will open it, but nothing gets loaded into it. Plain export, merge to panoramic, edit as smart object, nothing does anything.

Tried in both 32 and 64 bit modes, tried re-installing Lightroom 2.0 from scratch. still nothing. I sent a sample raw file into adobe and am waiting to hear back, but figured I'd see what everyone else thinks as well.

[_Mario_Coulombe_]

I have the same problem... a "ghost directory" in a duplicate of the same volume name...

Looking at the metadata of both files, i found a little difference in the folder field information in metadata...

My original cr2 file in the real volume has this in the folder field... E:\Wedding\Peter and Josée... notice it start with a capitale E

The file in "ghost folder" under the duplicate of the same volume has: e:\Wedding\Peter and Josée... lowercase for the drive letter

When i reinstall the previous version of Camera Raw, i have the message in LR saying i need 4.5 for full compatibility... i clic render using LR, and it works... But this time both file start with a capitale E in the folder field in metadata...

[_René_Box_]

Tried reinstalling the 10.01 update but no joy. Don't really fancy reinstalling Photoshop altogether. Edit in CS3 does not give me the pop up box whether I want to edit with LR settings etc. CS3 does fire up but the photo doesn't appear and am not getting an error message either.

I don't know why we have to go trough all this aggravation of reinstalling PS or its patches. It worked fine with LR1 and the issue appeared with either the install of LR2 but in my case it seems to have been caused after the CR 4.5 update.

[_Mario_Coulombe_]

Same here... i reinstalled the previous version or CR & it now works... this said, without full compatibility...

Try reinstalling the old CR...

[_Jim_Camelford_]

Mario, that's a terrific observation - that is the difference between e:\ and E:\ - resulting from the 4.5 CR update. I'd bet the code in LR would be handily fixed by UPCASING all the drive letters in LR.

jc

[_Linwood_Ferguson_]

I could edit before, but installed update again, no change. Still get the ghost directory, still am not prompted for edit-copy (etc) if I am editing a NEF, still comes back separate from the original file.

Note this works fine for a TIF, it's only raw (NEF) that fail for me.

And they fail every time now. I thought I had it work once, but cannot reproduce at all with default link.

I think this has been clearly said but in case not -- if you set up CS3 as an additional editor (i.e. navigate to the .EXE) it works fine. It is pretty slow, but it works, comes back stacked, does not create the ghost directory, etc.

[bob frost]

This problem of strange behaviour when opening into CS3 is known to Adobe, but they haven't been able to cure it yet in all versions of the LR2 program. I get round it by using CS2; everything works fine opening files from LR2 into CS2. Using Vista64.

Bob Frost.

[rmeier01]

I'm encountering similar problems on Macs with multiple disk volumes. I've been able to analyze the problem and reproduce at will. So I've filed the following bug with Adobe this morning.<br /><br />Roland<br /><br />******BUG******<br />Concise problem statement:<br />Lightroom 2.0: Editing a RAW file in Photoshop CS3 (Cmd-E) the resulting Photoshop file will not be stacked with the original RAW. Instead it will be imported as a new file into the catalog. The bug only manifests itself on Macs with multiple disk volumes with the "Users" folder relocated to a non-system volume. The bug has not occurred with any of the 1.x versions or in the 2.x public beta. <br /><br />Steps to reproduce bug:<br /> 1. System configuration: Mac Pro Intel, dual 2.66 GHz dual-core CPU, 8GB RAM, NVIDIA GeForce 8800 GT , OSX 10.5.4, all patches installed; LR 2.0 (final). Two volumes, "System" and "Data"; /Users relocated to /Volumes/Data/Users; /Users replaced by a symbolic link to /Volumes/Data/Users; LR catalog in /Users/<username>/Lightroom; Photos referred to in the catalog are stored in a hierarchy /Users/<username>/Pictures/<year>/<month>/<day>/<location><br /> 2. In LR's Library Folders Panel there is only one volume listed at this point: "Data"<br /> 3. Now select any RAW file, e.g. /Users/rolandmeier/Pictures/2008/07/12/Iceland/200807121234.cr2 and edit in CS3 via Cmd-E<br /> 4. Make edits and CS3, save and exit<br /> Results: <br /><br />The new file will be saved to /Users/rolandmeier/Pictures/2008/07/12/Iceland/200807121234-Edit.psd (my preferences). However it is not stacked with the original RAW. Instead Lightroom's Library Folders Panel now lists two volumes: Data and System; the PSD file is associated with the System folder. This is reproducible at will with any raw file in the catalog.<br /><br />Please note that this has nothing to do with the configuration of my Mac. When creating a new catalog from scratch outside of my home directory, e.g. in /Volumes/Data/Lightroom editing in CS3 works as before. I'm convinced the bug is related to the new "Folders" feature in the library module. <br /><br /> Expected results:<br /><br />After saving and exiting from CS3 the resulting "psd" file will be stacked with the original RAW file as in all LR 1.x versions.

[_Peter_Balogh_]

Hi Kevin,
I'm having the same problem as Pekka.
Reinstalled PSCS3 and the patches with no luck.
Still an "Open as" box comes up via "Edit in Photoshop CS3" and "Open as a smart object" instead of the raw image was selected in LR2.
Any other suggestions?

Peter

[MethodPhoto]

Check you have CS3 10.0.1.
As a workaround try adding CS3 as an external editor as well

[_Mario_Coulombe_]

Yes... do not re-install CS3... re-install the previous version of camera raw

[_Peter_Balogh_]

Richard,
I do have CS3 10.01,because I've installed the update.
CS3 as a 2nd editor works,but creates unwanted copies,
and I'm still not able to open anything as a smart object from LR2.

Mario,
Reinstalling the previous ACR and than choose "Render using Lightroom"
in the warning dialog just the same as working with CS3 as a 2nd
editor.

Peter.

[bo_callesen]

Have observed the same behavior and found that going back to ACR 4.4 did work as a temp workaround to solve the problem with opening in CR3.

br,
Bo

[_Robert_Munoz_]

I'm running LR 2.0 on a Mac with a single volume and I'm experiencing this problem, so the bug is not limited to multiple-volume Macs. The file is created on the correct drive, but it is not stacked or imported into LR and CS3 often hangs after I save the file and close CS3.

Robert

[bo_callesen]

More observations and test.

After playing around with the LR2 to CS3 transfer, can I see that it's only on some older pictures that I have problems (with both cr2 and tif). All from the period 1. AUG 2006 to 30. SEP 2006. At that time using PSE 4 and ACR 3.4-3.5.

If I take a copy of one of the cr2's who don't work and place it in another folder without it's xmp file, and then do a import can I afterwards do the LR2 to CS3 transfer! But if I do the same with a tif, it doesn't work (the tif still holds the xmp info). Then tested with an exported ver. of the tif and minimized the meta data on export, then import and it can now be transferred to CS3.

So it could look like some error in the info database/xmp file, from that periods use of ACR 3.4-3.5.

br,
Bo

[_Carol_Allen_]

I found out that when I re-imported files from Lightroom 1.4.1, every
Raw image in those folders would not go into CS3 from LR 2.

I had to rebuild my LR 2 database from scratch; i.e. import my Raw files
into LR 2 from memory cards and folders on my Hard drives. Then and
only then did LR2 Raw files go into CS3 and open up as CR2 files.

The bug is not, "per se", in LR2 or ACR 4.5; but, in the re-import
section of LR 2 when you first install it. And attempt to rebuild the data base
from previous versions of Lightroom.

Actually my friend hit this problem but can not log in for some reason even though he registered for this forum.

The point is this problem has to do with re-importing from a 1.4.1 version. The problem does not seem to occur if I import directly into 2.0 without reimporting from 1.4.1.

Carol

[_robert_a_meade_]

Kevin,
What's the solution for those who are using Photoshop CS2 (9.0)?

Robert

[WickSmith]

You and Bo have solved it. You haven't given us the answer. Only Adobe can do that, but you seem to have pinpointed the problem.

I went to a folder in my catalog that only had a few pictures. I removed them from the catalog. I then imported them as if they were new. From then on, the transfer from LR2 to CS3 worked as it should
b except
that the two files (the original CR2 and the PSD) did not stack and
b would
not stack, even manually. LR reports that the two files are in different folders, even though they aren't. The reason, of course is as others have noticed. LR returns the image to a folder with a
b lower case drive letter,
which it then sees as a separate folder. The only workaround for that is the tiresome process of removing the spurious directory and synchronizing the correct one, thereby reinstating the edited file.

b So...
the upshot of it is as you two have noted. Images updated from an older catalog do not behave well with CS3, while those imported newly into the catalog work almost correctly. something must not have been tested with the catalog updating code.

-wick

[WickSmith]

Carol:

When you rebuilt your database from scratch, didn't you lose all the adjustment information that LR was storing for each image? I couldn't afford to rebuild all that work. Better to wait until Adobe figures this out and provides a workaround.

By the way, I am assuming that all users of LR2 who updated their database from LR1 are having the same problem. Can this be a problem confined to a few people with some odd configuration?

[_Peter_Balogh_]

Just imported two raw files from my camera with LR2 into a new empty
catalog.Than tried to export them via "Edit in Photoshop CS3",but nothing has changed.PS starts,than an "Open as" dialog comes up.
So what works for some,just don't for others.

[_Simon_Garrett_]

No, for me it is not just stuff imported pre-LR2. It affects new photos imported directly into LR2. I have the setting "Automatically write changes into XMP" - don't know if that makes a difference.

By the way, that option (write changes to XMP) is how you cope with having to rebuild the LR catalog from scratch. If all LR edits are written to the sidecar (XMP) file, then not only can Bridge/ACR read the edits, but you can restart Lightroom's catalogue from scratch - I think.

[_Jim_Camelford_]

Right after Carol did her post, I created a new empty LR2 catalog and imported a folder of NEF's. No improvement when using a clean catalog. While I do not have a problem getting CS3 to fire-up, as some have reported, I still have the problem of the saved PSD file going into a phantom/virtual folder that must be manually re-imported back into LR2 and manually stacked with the original.

Gee, we need to come up with a 'name' for this phenom.

BTW - Tom Hogarty, since you are monitoring this blog and there DOES seem to be a real issue here .... can you please acknowledge that this issue is now on the LR team's radar and provide some statement regarding it since we all seem to be banging about it...but we're in the dark 'cause we don't have the code to look at and debug it and the team does !

jc

[Ian Lyons]

>BTW - Tom Hogarty, since you are monitoring this blog and there DOES seem to be a real issue here .... can you please acknowledge that this issue is now on the LR team's radar and provide some statement regarding it since we all seem to be banging about it...but we're in the dark 'cause we don't have the code to look at and debug it and the team does !

I think you will find that it's very much on the Lr team radar - click the button labelled "Show All Messages" then locate posts by Melissa Gaul (Lightroom Technical Evangelist), Julie Kmoch (Lightroom QE) and Kevin Tieskoetter (Lightroom Engineer).

[bo_callesen]

I can confirm also to have the shadow folder issue, when saving back to LR2 from CS3, shadow folder on my C-drive, but my photos are stored on the D-drive. I'm running Windows Vista 32-bit.

Regarding the problem with opening into CS3 from LR2, have I tested more since my last post. Because I in the past have been using another tool to add info to the xmp file, have I tried to erase that portion of info in one of the files with problems. Then did a read metafile from file, for then to be able to open into CS3.

That same portion of xmp info are in a lot of my older files and I'm still able to open these direct into CS3, so I do not think that the fact I have deleted the info direct are responsible for the effect, but there may be some treatment in LR2 when re-reading the changed xmp file.

But strangely just doing a read metadata from file (without erasing anything) did not get the opening to CS3 to work!

Br,
Bo

[_Robert_Munoz_]

I just discovered another flavor of this problem. I have previously restricted my "Edit in CS3" activity to DNG files, but I just edited a PSD file and chose "Edit with LR Adjustments". The file opened in CS3, I did a few edits and saved it. Just as with the DNG files, LR did not import it or stack it and I resorted to synchronizing the folder to find the newly-created PSD file and import it. And now there's a new twist -- even though I imported the file in the folder where it was created, and the file now appears in the LR folder grid view for that folder, it doesn't appear in the LR folder grid view for the parent folder. And as I was carefully looking through the parent folder grid view, I discovered that there are several other files that are in sub-folders and can be viewed in their sub-folders, but do not appear in the parent folder grid view. I have to admit this is getting a little worrisome.

Robert

[_Brent_Walton_]

Well, I'm first off glad that I'm not the only one having problems with this.

Secondly, I'm appalled that Adobe is not addressing this issue.

I can only speak to those using the Windows OS, but here is what I have been able to prove:

This problem is associated with the drive where your files are located. (Not the catalog, but the actual image files.)
When the files are on your C: drive, LR2 will open them and edit them in Photoshop.
When the files are located on any other drive, it will run Photoshop and then nothing opens.
File ownership has nothing to do with the issue

For example. I create a catalog called test, and import images off drive C: everything works fine. I create a catalog called test2, and import images off drive E (my other hard drive inside my PC), it will not open any of the images in Photoshop CS3. Drive E is NOT compressed.

So, I sure hope someone from Adobe is reading this and they address it.

Sincerely,
D. Brent Walton, cpp