Lightroom 2.0 will not export to Photoshop CS3

Folks, if you haven't seen this already, we've released a public release candidate for the Lightroom 2.1 update. I'm just going to post our project manager's announcement here, since she says it better than I could:

I am pleased to announce that the Lightroom team declared and released a public Release Candidate of Lightroom 2.1 on Adobe Labs this afternoon. http://labs.adobe.com/wiki/index.php/Lightroom_2.1
This Release Candidate includes some key bug fixes as well as official support for the following new cameras:
Fuji Finepix IS Pro
Nikon D700
Nikon D90
Nikon Coolpix P6000
And preliminary support for these new camera models:
Canon Rebel XS
Canon 50D
Olympus SP-565 UZ
Sony A900
Sigma DP1

And then there are those of us who do try to actually read the posts looking for an answer!

-------------
From:
Kevin Tieskoetter - 2:59pm Aug 13, 08 PST (#228 of 328)
"5. I've seen a couple reports of files not coming back into Lightroom at all when saved out via Edit in Photoshop. If you're having this problem, and you aren't using any of the problematic characters in your file path (' or &), and you're not using Smart Objects, please post about it here in this thread."
------------
To Which I replied:
"I'm having this problem and scratching my head. Recently updated from PS CS2 & LR 1 where this was working fine. Now, in PS CS3 & LR2 I can edit in PS3 (primary) but LR2 does not automatically add the edited file to the catalog."
-----------

I will admit that I started from the end of the thread and worked backwards. When I reached Kevin's post, that lead me to believe there was probably not yet an answer to this particular problem and so I posted my message.

I should have also added that this problem is happening on a machine running XP Media Center SP3. When doing the upgrades, I first upgraded to CS3 and then did the upgrade to LR2.

Regards,
David

Betty:

The length of this thread is probably a function of people not reading the earlier posts and then asking the same questions over and over again. Not unusual.

I'm sure you know that while designating CS3 as an alternate editor works, as far as it goes, it does default to the LR1 behavior. So, it creates an additional file even if you abandon the edit, would create 5 additional files if you sent them to CS3 and then manually created a layered image from them, would not automatically create that layered image, would not create a panorama, would not merge to HDR etc.

For most people, the workaround is fine. Some of us use these new featuires and would like to see the issue resolved sooner rather than later. But since there are so many new cameras being announced this time of year, and each with its own RAW format, I don't expect to see an update to LR2 until at least some of those RAW formats can be incorporated. Otherwise, there would have to be two complete updates in a short time span.

And in addition, we have PS CS4 coming. That may mean new integration features that LR2 would need to take into account. My guess is early to mid October for the LR2 release.

I am surprised to see over 300 messages on this thread. I had put out message #10 which stated that all I had to do was change my preferences and then things started working.

Since that time I did have to delete a ghost folder, but that has been the only other problem. Things are working very smoothly for me -- CS3 opens properly from LR, and when I save a picture in CS3, it stacks nicely back into LR. And if I don't save the picture in CS3, I don't have to delete those extra copies that LR had created in LR 1.x.

The difference for me--I believe--is that I put LR 2.0 and CS3 on a brand new Vista 64 machine. Thus there were no previous old scripts or old betas to contend with.

So if everyone can hang in there, they will be quite pleased with the interface between CS3 and LR2.0 when Adobe puts out their fix.

I also have an exporting problem, but it is slightly different and happens seemingly at random: from time to time I am suddenly unable to export any of my NEF's. I usually hit cmd-E on my Mac to export the NEF's to CS3, but there is just no respons - nothing happens. Trying to open the NEF by using the right mouse button or choosing the menu makes no difference.

Extra weird is that when that happens, I can still export any other file format by any of the methods mentioned above - it's only the NEF's.

It doesn't matter whether they are recent NEF's or very old ones, or which camera I made them with - all NEF's. Restarting, reinstalling, changing from 64 to 32bit and back, nothing happens.

I work around it by making adjustments in LR 2, saving the metadata to file, choose Show in Finder in the contextual menu and manually drag the NEF to the CS3 icon in my dock. This opens the CR window with the NEF in it. The file doesn't have the -Edit at the back of the filename and when I save it, it doesn't appear alongside the original NEF - I have to synchronize the folder to get it there.

Every now and then this problem is suddenly gone, and I don't have a clue what causes it and what solves it again.

I thought I'd mention it here, because it's very similar to the rest of the issues, but it is different as well.

Maybe it can be added to the To Do List.

I only realised the other day that as I edit photos in Photoshop they are being seen and catalogued in bizarre locations by LR2. My folders area of LR has become unusable, files are all over the place often out of context i.e. under incorrect folders. It's a nightmare and is trashing my workflow. I'd rather it not recognise edited files at all than do what it's doing.

Sorry, forgot to subscribe. - David

"5. I've seen a couple reports of files not coming back into Lightroom at all when saved out via Edit in Photoshop. If you're having this problem, and you aren't using any of the problematic characters in your file path (' or &), and you're not using Smart Objects, please post about it here in this thread."

I'm having this problem and scratching my head. Recently updated from PS CS2 & LR 1 where this was working fine.

Now, in PS CS3 & LR2 I can edit in PS3 (primary) but LR2 does not automatically add the edited file to the catalog.

Solution??

Thanks,
David

I said earlier that my "open in CS3" was working now. This was only half true, so here is the more exact situation. I have discovered that telling whether your attempts to rectify the situation actually worked is not as simple as it looks.

History - What I did (Win XPSP2, LR2, CS3 always updated)
***********************************************************
When I first found this thread I tried downloading and re-applying the CS310.0.1 patch. This did not work. Then I uninstalled CS3 and applied the patch again. This still did not seem to work (but - see below). When I looked at CS3 Scripting Support version, it was still 10.0.

Then I read this thread in more detail and modified and applied the batch file suggested by Fredrik in post #256. This seemed to work - I could open files from LR in CS3, and when I checked CS3 Scripting Support it was now version 10.0.1.

However...

What I now discover
*******************
If I have LR open but not CS3, and I right click on an image in LR, and select "Edit in Adobe PS CS3" and then "Edit a copy with LR adjustments", Photoshop opens but the image does not. Eventually I get the message as before that it can't open photoshop. AND, when I look at this newly opened photoshop, the Scripting Support version is 10.0, not 10.0.1.

If I then close Photoshop, and reopen it myself (i.e. not through LR), it opens and the Scripting Support now reads 10.0.1. And NOW if I try to open a file from LR it opens OK.

So somehow PS opened by LR is opening with at least one different file from if I open PS myself. In summary...

CS3 opened by me - Scripting Support version 10.0.1
CS3 opened by LR - Scripting Support version 10.0

One consequence of this is that I now realise that I don't know which of my early attempts to fix the problem actually worked, since I can't remember whether I tried to open CS3 from LR or it was already open, and I can't remember how it was opened when I checked the Scripting Support version. So the very first attempted update might have worked after all.

Adobe never 'tips there hand' in advance of a release. It is also likely to be awhile, if past situations are anything to go by. We will all know of its availability when it is released.

And this forum is one of the first places to get posted.

Don