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

  • 10
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
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
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like

Posted 3 years ago

  • 10
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
no one?
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
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!
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
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..
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
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!
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
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.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
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.]
(Edited)
Photo of Colin Mulcahy

Colin Mulcahy

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled 2015.4 Export Post Processing with Droplets Broken.

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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4369 Posts
  • 1160 Reply Likes
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
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..
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15434 Posts
  • 2277 Reply Likes
Our engineering team is investigating this issue.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
Good, thanks for the update.
Photo of Angus Jenkinson

Angus Jenkinson

  • 3 Posts
  • 1 Reply Like
This is bad, its part of a series of problems I have been having. Adobe's quality is getting unreliable. 
Photo of Robert Moroto

Robert Moroto

  • 3 Posts
  • 1 Reply Like
This reply was created from a merged topic originally titled PHOTOSHOP - Droplet acts differently on own VS after export on LightRoom.

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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4377 Posts
  • 1160 Reply Likes
In the original topic, Robert reported he is using CC 2015.4 on OS X 10.11.
Photo of Kelly C.

Kelly C., Senior Lightroom QE

  • 86 Posts
  • 39 Reply Likes
We have tested and identified this issue. A fix will be included with the next release of Lightroom.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4377 Posts
  • 1160 Reply Likes
Great, thanks for the update.
Photo of Angus Jenkinson

Angus Jenkinson

  • 3 Posts
  • 1 Reply Like
I think we are seeing the early warning signs of Adobe losing the plot. They have offered robust apps for years and now they are routinely buggy.
Photo of Tricia Mennell

Tricia Mennell

  • 11 Posts
  • 7 Reply Likes
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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
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.)

I had previously posted a workaround to this, which requires the use of the Run Any Command plugin: https://feedback.photoshop.com/photoshop_family/topics/lightroom-6-4-export-problem-with-droplets?to...
(Edited)
Photo of Angus Jenkinson

Angus Jenkinson

  • 3 Posts
  • 1 Reply Like
What I am doing is creating droplet. Selecting the relevant files in Finder (Explorer), if necessary by moving them into a particular folder temporarily, dragging the m onto the droplet, and then importing the files. A pain but functions.
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
Calling Adobe tomorrow, last time they told me the next release would have fixed it  but it's not the case, I'll keep you updated!
Photo of Kelly C.

Kelly C., Senior Lightroom QE

  • 86 Posts
  • 39 Reply Likes
@alfeel - It's not necessary to call. The multi photo droplet case has been verified, the bug re-opened and the developer notified. I apologize for this oversight; I know that for those of you that use droplets regularly in your workflow, this is a major drag. We'll investigate a workaround and try to get a more complete fix out as soon as possible.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4377 Posts
  • 1160 Reply Likes
Thanks much for the prompt reply.
Photo of alfeel

alfeel

  • 17 Posts
  • 1 Reply Like
ah ok super! thanks for the prompt update!
Photo of Butch_M

Butch_M

  • 314 Posts
  • 133 Reply Likes
Let's review ... I pay a monthly subscription fee so I can receive updates and new features 'when they are ready' only to discover that Adobe refuses to perform due diligence in testing and assessing that work before they release an update, relegating it's license holders to pay-to-play beta tester status.

I skipped Lr v6.2/2015.2 because of the abysmal Import Dialog fiasco. I did successfully update to Lr v6.3/2015.3 ... but then skipped v6.4/2015.4 due to this Droplet bug (actually another removal of function) and that the installer was arbitrarily removing files/folders in the user's root folder on Mac OS X.

Supposedly, the update to v6.5/2015.5 corrected these issues ... only to discover that the Droplet issue is only corrected to address single image export and not batch export like it was capable of from as far back as v2.0. In which case forced me to revert back to v6.3/2015.3 in order to maintain my long established workflow.

The whole impetus of Lightroom was to enhance a photography workflow ... I'm here to tell you, workarounds are not solutions ... just more work. I'd love to know how Adobe has improved my workflow with these past several updates. In my mind, we would all be better off if they would do absolutely nothing more and let well enough alone. At least then we could avoid the down time troubleshooting their mistakes to only end up reverting back to something that does work.

I knew this subscription model would eventually usher in an increased level of complacency and stifle innovation, but I did't think it would transpire so soon. The level of professionalism and attention to detail has diminished greatly at Adobe and it seems to begin with management as evidenced by the poor decision making of late ... the results of their efforts speaking for themselves.

I have been an Adobe license holder for a fair list of application since 1992 and if I could find an alternative to Lightroom today, I'd be gone in a heartbeat. Not because I don't like Lr ... but because I am tired of being treated as nameless, faceless mind-numbed lemming that is willing to pony up my monthly stipend in silent submission.

There was a time when Adobe actually was proud to base their business activities on the merit system and flourished by pushing the envelope as well as treating their customers as a valuable asset.

Unfortunately, those days are gone.
Photo of Angus Jenkinson

Angus Jenkinson

  • 8 Posts
  • 0 Reply Likes
Butch, your analysis is on the mark. My refrain is that Adobe is going off the boil, losing its mojo. I had some of the most reliable apps in software, you could edit 1gb files with 200 layers in Photoshop, and now the apps are crashing. They have changed their development and charging philosophy and believe in failing often. and fixing sometimes. Sell your shares. 
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15411 Posts
  • 2260 Reply Likes
Are you seeing a crash with Photoshop or Lightroom? If you are, you should start a new thread, and submit crash log with your Adobe ID: https://helpx.adobe.com/photoshop/kb/submit-crash-reports.html The team is very aggressive at fixing crashing issues.
Photo of Butch_M

Butch_M

  • 314 Posts
  • 133 Reply Likes
So, Jeffrey  ...  if I tell you Lr crashes when I try to export a batch of images to a Ps Droplet ... it will be fixed sooner? You should have told me that a couple of updates ago ... I could have saved myself ... and many other users all the fun of beta testing and trouble shooting for you.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15434 Posts
  • 2277 Reply Likes
Official Response
This should be fixed in the Lightroom CC 2015.5.1/6.5.1 update that was released today: http://blogs.adobe.com/lightroomjournal/2016/04/lightroom-cc-2015-5-1-now-available.html
Photo of Gethin

Gethin

  • 46 Posts
  • 7 Reply Likes
Not fixed. Droplet in export preset processes about 1/2 to 2/3 of the files requested but gives the droplet cannot connect error message.
2015.5.1, photohop, bridge, camera raw all up to date.
Photo of Gethin

Gethin

  • 46 Posts
  • 7 Reply Likes
did you test on raw images? my d800 nefs each take quite a while to export.  120 images would take me a couple of hours to export
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
Yes - Canon 5DMKII images - My system is a little faster, it was less than 30 minutes but I didn't watch the time closely so I can't be more accurate than that.
Photo of Gethin

Gethin

  • 46 Posts
  • 7 Reply Likes
Were you doing anything else whilst it was exporting?  So my raws tend to have quite a lot stuff going on - blurry edges and noise reduction - hence the time.  I'll screencap the next time I run a batch (and of course it'll work fine I bet).  :)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
Normal other applications: Web, Mail, etc. 
Photo of Gethin

Gethin

  • 46 Posts
  • 7 Reply Likes
Well its still not working, I did take a screen cap.  is it possible that if photoshop is still saving a doc that the droplet wont be able to communicate? my output files are 550-700 MB each. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
I finally converted my workaround actions back into droplets, and they are working again as expected on LR CC 2015.6 / OS X 10.11.   I tested with 65 scanned TIFFs, each about 140 MB, with two different droplets.
Photo of Gethin

Gethin

  • 46 Posts
  • 7 Reply Likes
after the windows aniversary release droplets are now not working at all.  What a mess.  
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
Since you've reported that this issue affects Photoshop droplets in general on Windows, independent of LR, I think it's appropriate to leave this topic (which is about a LR-specific bug) marked as "Solved".  For reference: https://feedback.photoshop.com/photoshop_family/topics/-droplet-couldnt-communicate-with-photoshop-a...
Photo of John R. Ellis

John R. Ellis, Champion

  • 4385 Posts
  • 1162 Reply Likes
Uninstalling/reinstalling Photoshop appears to fix (or at least improve) this issue: https://feedback.photoshop.com/photoshop_family/topics/-droplet-couldnt-communicate-with-photoshop-a...