Lightroom 2.0 will not export to Photoshop CS3

Kevin,

I'm on a Mac and I don't have a ghost folder problem; I have a "LR not updating with saved files from CS3" problem. And I think there are other Mac users who are seeing something similar.

Is someone looking at this flavor of the issue?

-Robert

In case you're wondering why Edit in Photoshop works differently when you have Photoshop 10.0.1, it's because, starting with PS 10.0.1, we use a different pipeline to communicate with Photoshop which makes for a tighter integration and faster workflow. In Lightroom 1.4 (or LR 2.0 and PS 10.0), the file had to be rendered out by Lightroom to a TIFF or PSD, and then opened by Photoshop. With the new pipeline, Lightroom simply asks Photoshop to open the file directly, using Adobe Camera Raw.

The reason this doesn't work with Photoshop 10.0 is that we needed a few fixes present in 10.0.1 for this to work correctly.

Just a bit of trivia and it may shed some light on why the behavior is different. Obviously this is a small consolation for those who are seeing problems in the communication between LR and PS.

If you add PS as an external editor, it will go back to using the old (LR 1.4) method of opening the file in PS. This will fix the problem for most of you until we're able to address it in LR.

-kevin

Are we sure that the problem wasn't in the beta?
I used the beta on a handful of test JPEG and RAW files but I don't remember editing in CS3. I was just too interested in the new develop tools.

I have one more request for a catalog - I've received a few catalogs from users who were seeing the ghost folder problem, but they were all from Windows. I understand there are also people seeing this problem on the Mac...

If you're on a Mac and are seeing the ghost folder problem, please drop me a line at kevint (at) adobe.com.

Thanks!

-kevin

Let's be a little careful about accepting other systems/software as being the problem...as in "my external LaCie is not granting me appropriate permission through Lightroom."

Adobe had this process (both problem #1 and 2) working perfectly in LR1.4 (and all earlier versions) and in the beta version of LR2 - without the numerous user reports that it doesn't work for them...

Adobe needs to make this work regardless of the setup...especially since LR and CS3 are both Adobe products! Clearly they made changes in the released software over the beta version that have contributed to this problem. They should be able to figure it and soon...as we have businesses to run!! ;-)

Andrew

I too have the same problem as #1. After over three hours on the phone with someone from Adobe and trying various things we have isolated the problem.

I'm on a Mac with Leopard (10.5.4). My catalogue is stored on an external firewire drive (LaCie Rugged 160GB along with some of my images). Lightroom will export RAW/DNG to CS3 no problem unless the images are stored on the external drive. If a Raw/DNG file is stored on my desktop or any other external drive (we tried three additional ones), it works no problem.

They think that for some reason, my external LaCie is not granting me appropriate permission through Lightroom. However, I have no problems opening up those same images directly through Bridge or CS3. Only through lightroom is there a problem.

The only workaround was to uninstall Camera Raw 4.5 and use 4.4.1. You get a dialogue box when exporting from Lightroom where you have to click "Render Using Lightroom" every time. Don't know what I'm missing with 4.5 but that is the only solution for now.

P.S. Should mention that a friend with the identical setup and external does not have these issues. Also, updated the external's software but still no change.

Brent, John - I agree. It's surprising, however, that these features have arisen since they were not reported as bugs in the beta version. Integration with CS3 is one of the major selling points with Lightroom. Their help screens clearly and directly advocate these capabilities - they are even touted in the what's new section as having been improved. Certainly, delaying the write to disk when opening a raw file for editing should speed the integration...and I was looking forward to that. Also, the ability to open more than one overlapping image and have it create a single editable file with layers in place was a major enhancement. I do a lot of architectural work and layering bracketed exposures is a frequent need. I guess I'll just have to wait for the fix....

In the meantime, there are enough work arounds, at least for those who can actually get CS3 to open from LR2, it's worth waiting...

Maybe Adobe should allow firsttime buyers of LR2 to download a free LR1.4 so that they can use that in the meantime...I'm certainly tempted to return to 1.4 for the time being...

Andrew

Here's hoping Adobe extend the LR2 trial period.

It's not really possible to get hands on experience of LR2 with these issues in place. I'm back on Capture NX and Photo Mechanic at the moment.

Not being an LR1 user, I was keen to trial the tight integration with LR2 and Photoshop. Not possible so far...

John, I agree. For me, I'm done trying things as I have "real" work to get done. For now, I'm just going to wait for a fix/update. I have a suitable work-around. (I configured photoshop.exe as a secondary editor, and I select that when opening a file and it works just fine.)

Thanks, Brent, for your reply. WAY too many people having issues, whether of the "#1" or "#2" variety (mine is #1) for it to be considered anything other than a bug; and since this problem hadn't manifested itself prior to LR2, you almost have to lay it at the feet of the new release as the source of the problem. Hopefully a fix is released very soon.