P: Opening photos in Photoshop from LrC using Edit In does not work correctly for some operations

Hello,

can anyone please be so kind and give me an example how the config.lua looks like for windows PCs.

Many thanks in advance !

Robert

I have this same issue. Here is some regarding my experience with the problem.

I have 2 computers, one is a Mac (10.12) and the other is a PC (Windows 7 Ultimate)

The issue is exactly the same on both computers.
It is impossible to use any of the Photoshop launch tools that open more than one file from Lightroom and merge it into a single file in Photoshop. CC 2015. Stacking, merge, layers... all fail with the following message:

The files could not be edited because Adobe Photoshop CC 2015.5 could not be launched.

That said, if I open PS first, then it works fine.

 

If I am working a single file, LR will launch PS just fine; Edit in Photoshop CC 2015.

 

Tom

You were right. Thanks for catching that. The thing is I've made the correction and still have the problem. LR System Info now reads,

Config.lua flags:
EditExternally.OverridePhotoshopPath = /Applications/Adobe Photoshop CC 2015.5/Adobe Photoshop CC 2015.5.app

...which is the same as the contents of my Config.lua file

Here is the OS system info about the PS app. As far as I can see, the path I've specified above should be correct, right?
 

Something strange just happened. I restarted LR (PS was already open), immediately selected one picture and had "Edit in" appear functional. I then selected several items and tried "Edit in" and it was non functional. I then restarted LR, choose one item, "Edit in" appeared functional so I choose it... but nothing happened. PS is running, but the item did not open in it. Going back to LR, "Edit in" is now greyed out!

After some experiments, it seems "Edit in" mostly appears (although it still does not work) with the image that is preselected when LR first opens. After selecting an image "Edit in" goes grey.

Could you check again? What is the name of your Photoshop app? On my system it is Adobe Photoshop CC 2015.5.app (note the .5 after 2015), I suspect yours will be the same. In which case you need to correct the config.lua entry to add that .5 to the app name.

My Lightroom system info says

Config.lua flags:
EditExternally.OverridePhotoshopPath = /Applications/Adobe Photoshop CC 2015.5/Adobe Photoshop CC 2015.app


My Photoshop system info says
Application folder: /Applications/Adobe Photoshop CC 2015.5/

Thanks Simon for the update on these problems. It is very much appreciated.

@1287334 Thanks for the clarification. Rikk has logged a bug on the original "Open as Layers ...." issue, which is under investigation.

@2571961 When the menu items are greyed out, that means Lightroom could not locate Photoshop. If you setup the config.lua file correctly, Lightroom's system info should show an entry like the following

Config.lua flags: 
EditExternally.OverridePhotoshopPath = /Applications/Adobe Photoshop CC 2015/Adobe Photoshop CC 2015.app

where on your system, EditExternally.OverridePhotoshopPath should point to the actual installed path for your copy of Photoshop. What does your Lightroom system info say?

With 10.11.6 I've tried editing the config.lua file, making PS the default editor for psd  files in the OS and have also specified the direct path to PS for the additional editor in LR preferences. When I try to "edit in" I get photoshop as both options, but everything is still greyed out.  Opening PS first and then opening LR does not seem to work for me either. I've also tried killing the com.adobe.Photoshop.plist file and uninstalling and reinstalling PS.  Nothing seems to work. 

I think there are TWO different problems being discussed on  this thread which should be split into two different threads.  One is Photoshop not opening up ever and the other is your problem and the original topic of the thread.  The original topic, the opening of layers worked previous to 6.7 so it is just a new bug as acknowledged.  The other problem of Photoshop not ever opening is a longer standing problem for some people and is apparently what Simon is referring to above.  Hopefully Simon is working on the original problem also.