14 Messages
•
354 Points
Fri, Dec 21, 2018 12:03 AM
In progress
Lightroom/Photoshop: Fails to export with droplet if more than one file selected
I’ve tried the forums and Google regarding the following issue. It seems that after updating to PS 2019 v20 or later, the dropletfeature in LR’s export fails if more than one file is selected at a time. The only workaround seems to be to create thedroplet’s shortcut on the desktop or other directory, then manually select (byFile Explorer or File Finder) and then drag the whole folder to the shortcut. Not sure if this is the case with Mac since I’mon Windows, but others on the forum are having the same problem with notresolution as late as 10/16’s post (before mine today). Yes, this workaround seems to work, but that goes against all objectivesof Adobe to make things easier and more efficient, not less so by requiring anintervening export, then an out-of-application drag/drop. Please passthis along to the appropriate to see if we can get a fix a.s.a.p. I used this feature many times fordirect-to-slideshow alterations to cataloged files such as applying custom stroke lines or borders. Thanks for any help you can lend.
Problems
•
Updated
2 years ago
35
10
Helpful Widget
How can we improve?
Tags
No tags available
Responses
Official Solution
petegreen
Adobe Administrator
•
780 Messages
•
16.7K Points
2 years ago
Feel free to update Photoshop and let us know if this is resolved for you.
To update Photoshop CC to 20.0.3, click "Update" in the Creative Cloud desktop app next to Photoshop CC.
More detailed instructions for updating
Thank you for the report James!
Regards,
Pete
0
sunil_bhaskaran
Adobe Administrator
•
522 Messages
•
9.8K Points
2 years ago
We are investigating.
Thanks,
Sunil
0
0
John_R_Ellis
Champion
•
5.5K Messages
•
97.5K Points
2 years ago
0
0
james_smith_4570208
14 Messages
•
354 Points
2 years ago
Curious: Are you using Mac or Windows? I wonder if it is a Windows-specific issue. I just tried mine again, but haven't yet updated to LR8.1, so will do that and try again.
1
0
james_smith_4570208
14 Messages
•
354 Points
2 years ago
1
0
magnus_winterholler
3 Messages
•
100 Points
2 years ago
Since the update to version 20.0 I get this message when I try to run a droplet:
Could not run the droplet because the file could not be found.
Whenever I select 1 photo the droplet runs fine and does what it has to do. But whenever I select 2 or more photos the droplet gives me the error-message.
0
0
JeffreyTranberry
Adobe Administrator
•
15.8K Messages
•
295.1K Points
2 years ago
Sr. Product Manager, Adobe Digital Imaging
0
0
John_R_Ellis
Champion
•
5.5K Messages
•
97.5K Points
2 years ago
https://feedback.photoshop.com/photoshop_family/topics/lightroom-6-4-export-problem-with-droplets?to...
I wrote it to work around a previous droplet bug several years ago (they seem to happen every year or two), and I haven't tested it with this bug, since I can't reproduce the bug.
0
0
John_R_Ellis
Champion
•
5.5K Messages
•
97.5K Points
2 years ago
1. Download and install the Run Any Command plugin.
2. Download the runaction.vbs 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":
"c:\users\john\runaction.vbs" "Auto Levels" "Default Actions" "{FILE}"
Replace "c:\users\john" 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 (make sure they're quoted).
0
0
james_smith_4570208
14 Messages
•
354 Points
2 years ago
Previous PS v20 attempts made the droplet, but they would not work in LR if more than one file selected as a post-process droplet. This time, the droplet wouldn't even create in PS v.20.0.3.
As I did in previous troubleshooting (mentioned above), I retained the older PS CC2017 version, tried the exact same action, and the droplet was successfully created as in the past. Still unclear why this latest update that is supposed to fix this appears not to do so, at least in the Windows platform. Please continue to have this looked at.
Thank you.
0
0