Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: dgerth on October 03, 2012, 10:11:21 am
-
I am having trouble with the Lightroom-Photoshop connection. I am running LR 4.1, and just upgraded to CS6. System is Win 7, 64 bit. Lightroom is still looking for the old 32 bit CS3 version of Photoshop, and all the export options (export as layers, smart object, etc.) are greyed out. I have had no luck in figuring out how to point LR to the new version of Photoshop. What am I missing?
Thanks in advance.
-
... just upgraded to CS6...
You might need to update it first, before LR4 can recognize it.
-
Not sure what you mean - I have updated to the latest versions of both LR and CS; still no luck.
-
Just uninstall both then reinstall PS first then LR
-
LR should, I believe, default to the most recent version of PS that's installed.
Check the preferences and if needed, change the connection in the External Editing preference for Lightroom.
Uninstalling CS3 could also fix the issue.
-
dgerth,
Did you ever get this problems solved? I just went through a similar experience earlier this week. I removed CS4 & 5 from my windows machine & all of a sudden LR was looking for CS4. It would not see CS6. I could not open files as a smart object or merge to HDR pro etc.
LR simply did not see CS6. It was fine before I removed the old versions of PS. I have no idea what happened, but I reinstalled LR4.2 as I thought perhaps the upgrade was corrupt. did not fix it. so I reinstalled PS CS6 and all is well now.
-
I did get the problem solved. I inspected the registry entries for the Photoshop path, and it was pointed to the old CS3 file. I uninstalled CS6, reinstalled it, and all was well. Checking the registry again showed it pointing to the correct file.
No idea why it happened, but at least it's fixed. Thanks to all for the assistance.
dan
-
Unfortunately, this rather erratic and "sticky" external editor behavior of Lightroom is well known and persists into the current version. I had rather hoped they would fix it by now, but apparently that is not the case.
Deep sigh .... perhaps the next version? ???
Jack Winberg