Lightroom 2.0 will not export to Photoshop CS3

Temporary fix to work around this issue: In the Preferences/External Editing dialog box, go down to Additional External Editor (I had Elements 4.0 there), and override that setting by choosing Custom and by pointing to Photoshop.exe. It will tell you that you are already using CS3 as your primary editor but do it any way. Then, when you attempt to open a file in CS3 from Lightroom 2, choose Edit in Photoshop.exe instead of Edit in Adobe Photoshop CS3. It worked (in 8 bit - haven't tried it in 16 bit).

Jim

I'm having a similar problem. When I try to edit in Photoshop CS3, Photoshop opens and then Lightroom gives me a message that it can't edit in Photoshop because it can't open Photoshop! It earlier told me that I should run the Photoshop update to get camera raw 4.5 which was already installed. I manually reinstalled it and got rid of that message but still can't get to Photoshop.

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

There are posts from *four* members of the Lightroom team IN THIS THREAD!!!

different for me. All my images are on my e drive. They all open in cs3, but save back in LR on the phantom drive, have to be synced to the real drive and then removed from the phantom.

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

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

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

>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).

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

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.