Export preset where you chose "Open in other application" and you have selected a droplet (I have a folder with many droplets) does not work, because the droplet utilized by photoshop is not the one chosen in the export preset
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!
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..
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 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.
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.
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.
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've created two actions in Photoshop - one for landscape and one for portrait photos. I created a third action that does a few things, and then using the conditional argument it chooses one of the first two. I made a droplet of the third action. When I drop files onto the droplet it works fine. When I export in LR and ask it to run the droplet after export - it says: The command “If” is not currently available.
I am exporting from LRCC and selecting my droplet in the Post Processing section of the export folder and the droplet opens in my toolbar, but does not run. Lost an hour today messing around with this. Not loving how much time I lose to CC bugs only to have to find a thread like this. Adobe should recognize the immense inconvenience and expense we are all going to while they test their software on us. My bill is not for a 'beta' version of this software so it really is unacceptable.
Btw at least the droplet used is the correct one at least, but it's not applied to all the photos so it's kind of useless.. do we have to wait 2 other months for another update? 😞 Hope not!
Unfortunately, though the bug was listed as fixed in the LR CC 2015.5 / 6.5 release notes, the export now applies the correct droplet to the first photo only -- subsequent photos in the export don't get any droplet applied. (To avoid confusion, I removed my previous post, to which @ALFEEL had called out the new, incorrect behavior.)