P: Droplets no longer work with export presets (CC 2015.4)

Our engineering team is investigating this issue.

I got a call from adobe the other day, they told me to roll back to the previous version and wait for the next one..

See my previous message in this topic for a workaround to the bug: https://feedback.photoshop.com/photoshop_family/topics/lightroom-6-4-export-problem-with-droplets?to...

When exporting a file as a PSD to run a PS Droplet it no longer works.

The break completely disrupts my automated processing workflow. It stops with a PS droplet showing in the task bar. Does nothing else. The droplet is working fine if I drop directly onto it.

Had to revert back to a previous version of Lightroom to get it to work again.

I wrote a script that works around the bug by letting the droplet's action be invoked directly rather than via the droplet:

1. Download and install the Run Any Command plugin.

2. Download the runaction.sh script and place it in some convenient folder.

3. Change the export preset to do After Export: Do Nothing (instead of running the droplet).

4. Insert the post-process action Run Any Command.

5. Enter this command line in Run Any Command's "Command to execute":

 sh "/Users/john/Desktop/scans/runaction.sh" "Auto Levels" "Default Actions" {FILE}

Replace "/Users/.../runaction.sh" with the location of where you placed the downloaded script. Replace "Auto Levels" and "Default Actions" with the Photoshop action name and containing action set that was formerly being run by the droplet.

[Updated 1/18/19 to use Dropbox's new URLs.]

Unfortunately, using the Run Any Command plugin as a workaround fails.  I tried using this command line to Run Any Command:

open -a path-to-droplet.app {FILE}

But when I exported more than 1 or 2 files, Photoshop crashed.  Apparently, the droplet .app doesn't wait for the droplet to finish, and Photoshop can't tolerate running multiple invocations of a droplet simultaneously.

Same problem occurs with a command line that invokes the executable directly:

path-to-droplet.app/Content/Droplet {FILE}

So the only workaround is to rollback to CC 2015.3.

I did some more testing and I've observed the same symptoms (CC 2015.4 / OS X 10.11.2).  I have a number of export presets, each with a different Photoshop droplet for the export's post-processing application.  When LR runs one of the export presets, it ignores the droplet specified in the preset and instead runs the last droplet that was successfully executed.  You can force an export to use its specified droplet by renaming all of the other droplets and restarting LR before doing the export.  Then that droplet becomes the last droplet that was successfully executed, and it will be run for all subsequent exports.

I rolled back to CC 2015.3 and the export presets started working correctly again.  See here for how to roll back: http://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/

Things that don't work around the bug:

- Resetting LR's preferences.

- Exporting from a new catalog.

- Recreating the droplets, contained actions, and export presets from scratch.

- Restarting LR and PS.

- Putting each droplet in a separate folder.

The bug didn't occur for me on Windows 10.

PS: I got OS X 10.11.3 (15D21). I noticed in the last mac update all my usb memories, sd, cf, and hard disk are now showing the real capacity, a 2tb hd shows up as a 2tb hd and not a little less as usual!

I tried changing the location of the droplet and put it on the desktop, creating another export preset with that droplet, but I get the same result It select a random droplet (I have tens of them) and process the photo with it..

if I select a photo and export it with the same export preset containing a droplet 5 times I get 5 different results. Droplets are working fine, the export function in Lr is working but ”open in other app” and selection a droplet five random result. It was fine before the last Lr update!