Lightroom 2.0 will not export to Photoshop CS3

"... if I 'Edit in CS3' a raw file-it now opens and I can make changes to it in CS3. When I save it, the resultant saved file is not stacked beside the original. All my folders are on my L: drive, in a hierarchal structure. After saving, I have a second occurrence of L: in the volume list, with a repeat of the original folder name ... and it contains 1 file (the one I saved). I have to manually synchronize the 'real' folder to pick up the file saved from CS3. Then I can delete the 'phantom' folder."

I am having this same problem. P: drive in my case. This is a 2nd internal HD.
Windows XP SP2
LR2
PSCS3
ACR 4.5

I'm experiencing the same thing as jc, if I choose 'Edit in CS3' with a DNG file, it opens and I can make changes to it in CS3. When I save it, the resulting saved file is not added to the LR library or stacked beside the original. I have to manually synchronize the folder to pick up the file saved from CS3.

I have tried re-installing LR. I have tried creating a new empty LR catalog and importing only a few random DNG files. I have tried changing all the settings in the LR external editor tab (PSD/TIFF, 8-bit, 16-bit, ProPhoto/Adobe RGB). I always get the same result. I should add to this description that during the 20 - 25 different tests of this functionality, CS3 hung up about half the time, and required a Force Quit.

I'm running OS X 10.5.4 on a Mac Pro.

rm

@jc:

>However.....that being said, if I 'Edit in CS3' a raw file-it now opens and I can make changes to it in CS3. When I save it, the resultant saved file is not stacked beside the original. All my folders are on my L: drive, in a hierarchal structure. After saving, I have a second occurrence of L: in the volume list, with a repeat of the original folder name ... and it contains 1 file (the one I saved). I have to manually synchronize the 'real' folder to pick up the file saved from CS3. Then I can delete the 'phantom' folder.

Replace the 'L:' with an 'E:' and you accurately describe what I observe.

crh

System Info:
Lightroom version: 2.0 [481478]
Operating system: Windows Vista Service Pack 1 (Build 6001)
Version: 6.0 [6001]
Application architecture: x64
System architecture: x64
Physical processor count: 4
Processor speed: 2.4 GHz
Built-in memory: 8124.8 MB
Real memory available to Lightroom: 8124.8 MB
Real memory used by Lightroom: 2565.8 MB (31.5%)
Virtual memory used by Lightroom: 2563.3 MB
Memory cache size: 1553.2 MB

I was experiencing the same problem earlier today. I kept trying it; and was even running LR2 and CS3 from different admin user accounts. Then it started working. All my files are 16-bit, but in my test folders I might have had some 8-bit JPG's and maybe ..... that fixed it. but I can't replicate it now.

However.....that being said, if I 'Edit in CS3' a raw file-it now opens and I can make changes to it in CS3. When I save it, the resultant saved file is not stacked beside the original. All my folders are on my L: drive, in a hierarchal structure. After saving, I have a second occurrence of L: in the volume list, with a repeat of the original folder name ... and it contains 1 file (the one I saved). I have to manually synchronize the 'real' folder to pick up the file saved from CS3. Then I can delete the 'phantom' folder.

This doesn't seem right.

I'm also experiencing some strange things with the smart object transfer - but I'll worry about that after I get the easy stuff going.

Anyone else seeing this ????

jc

Actually, it works fine on my copy of Vista Ultimate (32 bit). It is remarkably fast too....

Stephen

I am in the same position the work around does work I have emailed Kevin at Adobe. Funny thing is on my backup rig which is running XP Pro it works fine but not on Vista Ultimate x32.

Can someone who is having this problem drop me a line at kevint (at) adobe.com? I'd like to have you try a couple things to help me diagnose what's going on.

Thanks,

-kevin

"Has anyone else tried Betty Reed's trick of changing the bit depth in the preferences? I don't know why that would be a factor, but I'm intrigued by her success. "

Julie, it worked for me. After temporarily switching to 8 bit, I could then open as 16 bit or as a smart object. Well done Betty!

John

I am having the same problem with edit in CS3 too.

Works fine for me, no problems at all. Windows XP