Skip to main content
Known Participant
Jan 28, 2016 3:31 AM UTC
Released

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

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

This topic is closed to new replies. Start a new post to keep the conversation going.

52 replies

Known Participant
Apr 19, 2016 9:02 AM UTC
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. 
Translate
Inspiring
Apr 13, 2016 2:50 PM UTC
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.
Translate
Inspiring
Mar 21, 2016 12:31 PM UTC
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.
Translate
Inspiring
Mar 21, 2016 12:22 PM UTC
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.
Translate
Known Participant
Mar 16, 2016 11:08 PM UTC
ah ok super! thanks for the prompt update!
Translate
johnrellis
Legend
Mar 16, 2016 11:06 PM UTC
Thanks much for the prompt reply.
Translate
Kelly Castro
Adobe Employee
Adobe Employee
Mar 16, 2016 11:05 PM UTC
@10523507 - 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.
Translate
Known Participant
Mar 16, 2016 10:41 PM UTC
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!
Translate
johnrellis
Legend
Mar 16, 2016 10:37 PM UTC
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 @10523507 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...
Translate
Inspiring
Mar 16, 2016 8:14 PM UTC
Amazing betatesters....
Translate