Thank again Jeffrey for the plugin 🙂 But I have bad news… I can’t run it on a droplet without getting an error at the end, even though the droplet executed perfectly. It looks as if the Photoshop droplet is returning some error code which your plugin treats as such (obviously). So as a result, after the first image, I have to manually choose to ignore the error and keep going, and I have to do that for every single photo.

The solution I propose is the addition of a small box in the plugin configuration to ignore errors and keep going…

Thanks.

Okidokie, added that to .3. —Jeffrey

I’m struggling to fully understand what exactly happens. I am assuming that this approach gets around the Windows problem of trying to run a large batch of files (with long path/filename strings) to a droplet. If so, what is the specific way to run a droplet on each file (such as a noise reduction and sharpening droplet). Thanks.
Nick

I don’t exactly know what a “droplet” is (except that it’s something you can run to invoke a Photoshop action on a file) so perhaps I won’t be be able to address your exact concern, but the the problem that this plugin solves is the ability to do something to a file while it’s being exported, as opposed to a simple “do this to the images after they’re exported”. This is particularly helpful when the images are uploaded somewhere (e.g. to Flickr) during the export, because in that case the images are already gone when the export completes. This also lets you do what you want to an image before other “post-process action” plugins are invoked, such as adding borders or watermarks with LR2/Morgrify. If your export is a plain vanilla export to “Files on Disk”, there’s little benefit to using this plugin compared to the built-in after-export action, except perhaps the issue you mention about filenames (this plugin invokes the command on each image in turn, while the after-export action does them all at once). —Jeffrey

Oops… I read your info more carefully, and I see that the commands are applied after the image is rendered in Lightroom. Thanks.
Nick

Thanks, Jeffrey!

Conor, are you doing that from Lightroom’s Export module? I don’t see a way to specify the whole folder. If you meant that a folder can be dragged onto a droplet icon on the desktop, then yes I’m aware of that — I just wanted to be able to do it all at once from within Lightroom. And that is exactly what Jeffrey’s plugin does for me.
Nick

Hi,

I would like to share with the other this tip: if you want to execute two commands a time with this plugin, you need to put a && without quotes between the two. It worked for me for the command

'/opt/local/bin/mogrify' -raise 50 '{FILE}' && '/opt/local/bin/composite' '-gravity' 'SouthEast' '/path/to/Pictures/lightroom/identity.png' '{FILE}' '{FILE}'

Hope it will help someone, and hope this was not obvious to anyone but me.

Giovanni

Jeffrey,
Can you help me understand what this error code means? My droplet seems to be running the first command of the Action, but not the second. Hopefully there is a simple setting involved. Thanks,
Nick

+92.9: [144527E0] line 6608: STATUS is 1
+92.9: [144527E0] line 6625: Ignoring the error, as per the user setting
+92.9: [144527E0] line 6606: Running: ""C:\NR+Pre-Sharp.exe" "S:\2009\2009-05-17 Roeper Choir\Pass 1\2009-05-17 Poeper Choir Requiem-2.psd" 1> "C:\DOCUME~1\Parents\LOCALS~1\Temp\LR-571" 2>&1"

I’ve never tried putting multiple commands, but at a minimum you’d have to separate them by semicolons, but perhaps even then it won’t work, and you’d need to drop them into a batch file that you then reference from the plugin. —Jeffrey

Hi Jeffrey! Greetings from Japan!
I’m in the U.S. Navy and trying to figure out a better workflow for all the photos I take for my office.
Your export plug-in seems like a great idea. I’d like to apply it to have the photos open up in the Windows XP built-in CD burner. I’m trying to find the command-line arguments for it, but haven’t had any luck yet.
Do you by any chance know how to execute it?
Thank you again.

I don’t know anything about XP’s CD burning, sorry, but you know that it’s built in to the normal export, right? —Jeffrey

I have built a simple command-line email sender to use with Lightroom 2. It is fully configurable from the command-line parameters and/or a config file. I use it with this plug-in and love it! Thanks for proving a simple way to do additional processing!
http://www.redheadcentral.net/MailAttache.zip

Hi Jeffrey,

I am trying to create a command with tokens to copy a photo to a sub-folder on my desktop (Mac). That sub-folder should be named to today’s date, in the format of dd.mm.yy
So for example if I were to run it today, the command would create a folder “8.11.09” on my desktop, and copy the photo to that folder.

Can help me with the syntax? I’m a bit computer challenged…
Many thanks,
N

It depends on your system (Win? Mac?), but it should be easy to do with exiftool. Check out the renaming examples in particular. —Jeffrey

understood.
Now I have some Phil Harvey wisdom to read…
Cheers,
N

Hello Jeffrey,

Thank you for your answer.

The standard export command is too basic and I believed that your solution could bring to me of the assistance.
I need to make several operation after for a batch photographs. This batch passed in argument towards other programs.

Best regards.
Julien

This plugin can’t do what you want because it has access to the exported images only for a moment during the export of each image, and doesn’t know when the overall export has finished, nor what the final image filenames might be. But the overall Export Action should be able to do what you want, because it will pass all the image filenames to the command you specify. You can make it a batch file (Windows) or script file (OSX), so you can have it do as complex an operation as you know how to program. —Jeffrey

Update July 2010 – I figured out a way process all the files at the end of an export, as of version .27 —Jeffrey

Dear Jeffrey
(This from Sydney, Australia)
Any chance of a run any command on *Import* filter?
Currently I tediously run exiftools on files where LR (or my camera) won’t recognize the lens (such as CV manual focus lenses). What I do is copy new files to disk, run exiftools in the terminal, then import them. Things have got a bit better with the new beta, since updating exifdata didnt’ work relaibly before, I suppose now I could use LR to import, then exiftools then update.

But how cool if there were a way to run extra commands on import!

Not possible yet in LR3 )-: —Jeffrey

I was wondering if this plugin helps you run any command on the image before it becomes JPEG — not sure I described it right, I would like to run a command on the intermediate image (may it be a BMG or TIFF,) sort of pre-processing the image.

You can do that by having Lightroom export a TIFF/PSD, then using the command to do your processing and, finally, if you want a JPEG, have it do that as well. —Jeffrey

Jeffrey that helps, however when I use the {Path} token it gives the path with “>” not “\” on Win 7.

example:
D: > users > username > path > to > file

Can you specify the “\” character?

D:\users\username\path\to\file

Thanks,
-Jacob

Yikes, not sure how that happened, but I’ve pushed a new release that fixes it. —Jeffrey

I have an answer to my own question but if anyone has any better suggestions let me know.

I can use an ImageMagick command to make a unique filename based on the input names. My execute on completion command looks like this:

convert -loop 0 -delay 50 {FILES} -set filename:f “output_%t” “{pictures}\TEST\%[filename:f].gif”

Note the use of the -set to make a filename based n the input. It turns out that IM uses the 1st filename in {FILES} which is perfect for my needs.

It is very cool how you can mix the Plugin template values and IM escape variables in the same command.

Robin

i would like to be able to digimarc photos on export using your direct to smugmug plugin (via temporary files). is it possible to do that using a photoshop droplet (app) with your “run any command” post process filter? thank you for your plugins!

Lee

Yes, seems reasonable. I’ve heard folks run Droplets from “Run Any Command” successfully. —Jeffrey

that worked! thank you.

if i understand this “filter” correctly though, the process only happens after the upload to smugmug. is there a way to make it happen to the image before going to smugmug (only choice seems to be to export to disk first — adding the digimarc — then upload to smugmug from the disk copy.

Lee

If you use it with the SmugMug plugin, it’ll happen before the upload, but you’ve got to make sure you update the image in place. —Jeffrey

Does this plugin work with LR Publish Services (such as jf Flickr)? I’m attempting to do some exiftool post-processing on images prior to publishing them to Flickr (e.g. remove/update CreateDate, CreateTime, etc.), but the capture time for the image on Flickr is set to the original photo’s capture time.

Yes, it gets control of the copy of the image that Lightroom creates for the export, before the overally controlling plugin (e.g. Flickr plugin) gets it. —Jeffrey

Jeffery,

i use the command as shown below, to set the file modified date:

touch -am -t ‘{YYYY}{MM}{DD}{HH}{MIN}.{SS}’ ‘{FILE}’

but this command only works for image file, video files do not take any effect.

do you have any idea to make it works for video files?

thank you.

It seems to work for me. Perhaps send a plugin log for a sample export. —Jeffrey

Hi Jeffrey,

Thanks for the previous answer about using with Python. I am using a Mac with Python 3 but I get ‘sh: python3: command not found’ when I try to run a Python script upon completion. Any idea why?

I tried on two separate Macs but got the same result. However, I don’t get the error with Python 2.7, only with Python 3.

Thanks,

Paul

Try using the full paths to the python binary and your script. —Jeffrey

I am registered user using Lightroom CC on Mac OSX El Capitan, I try to run a shell script .sh file with some tasks to run after my export.

——————————–
My command to execute upon completion is:
sh /Volumes/Macbook13\ 500GB/reportajes/list.sh
(I run sh script from terminal and it is running well)
———————————

I don’t get any message and I don’t get anything in log or diagnostic messages, but it doesn’t works.
This is my sh file:

#Create csv.csv file with list of jpg exported files.
rm csv.csv
echo “Title,Taxonomy,Path,Price” >> csv.csv;
for f in `ls *.jpg`; do
echo $f”,”${PWD##*/}”,”${PWD##*/}”/”$f”,100″ >> csv.csv;
done

—-
Thank you Jeffrey

You probably need to put something in there so that your script knows what directory it should work in. When run from Lightroom, you can’t assume you’ll know what directory is the script’s current working directory. —Jeffrey

Hi Jeffrey, all,

Nice plugin.
However, I am struggling on one point : is there any variable to access the original file ?
In my case, I am trying to run a command like “rm ORIGINAL_FILES” upon completion, basically to export to JPG and delete the NEF file.

Thanks !

Sure, click on the after-processing help link in the plugin and you’ll find it, but wow, it seems scary to delete the master this way. Unless you have copies saved elsewhere upstream in your workflow, considering moving the file rather than deleting, just so you have a chance to recover it if need be, at least until you next clear out the move destination. —Jeffrey

Jeffrey,

This plugin seems to be exactly what I need, but before I get lost trying to figure out HOW to do this, I’m wondering if you could tell me whether or not it’s even possible.

I publish photos to my WordPress website using WP/LR sync. This allows for the standard Lightroom publish settings such as image size and quality, but what I am really missing is some way to compress them appropriately for web, using a service such as jpegmini or some other… to be determined.

Will this plugin allow me to click publish on the WP/LR sync plugin, have this plugin intercept the created jpg, compress it, then continue the upload to my site?

Hopefully I haven’t misunderstood what your plugin is capable of…. thanks in advance!

Joe

Yes, but if you have jpegmini, you can just use their Lightroom plugin directly. In any case, you can use this plugin to do whatever you want to the image file…. so long as the file ends up in the same place when you’re done, you can do whatever you like to it. —Jeffrey

Hi again Jeffrey!

After aborting a publish operation I continue getting invocations from Run Any Command for files not actually published. In this case, three files are marked to be published: DSC05015.JPG, MAH02617.MP4 and DSC02612. I aborted the Publish operation immediately after starting it. NO files were actually ever copied to the final destination. My program received invocations for the two JPGs, but not for the MP4.

Sometime earlier, I had aborted a Publish with a large number of files yet unpublished. I can’t say how many of those received invocations, but it was also a large number.

It seems that this is not the desired behavior. Maybe a problem/limitation with LR? Also likely I can work around it easily enough. Haven’t tried yet.

Logs have been sent for Run Any Command and Folder Publisher as well.

Unfortunately, I don’t think there’s anything I can do here. Lightroom invokes the plugin when it’s got the rendered copy ready for export, so the plugin is just responding to that. You’d imagine that Lightroom would be checking whether the export is canceled at regular milestones, such as just before invoking a plugin, but from what you report it sounds as if they don’t. )-: I’m not sure what to do other than report it to Adobe. —Jeffrey

I just installed this to try to make animated GIFs as suggested above. When I ran Custom Command 1, I got this error:

Assert Failed run-any-command#93 U[1506302414]+5226.7:[x6080005612c8] @InitPlugin line 1044:
Assertion failed(!):
[x6080005612c8] @InitPlugin line 1044
[x6080005612c8] @CustomCommand line 146
[x6080005612c8] @Trap line 222

Followed by another dialog with “Assert @Debug:880”.

The command I was trying was:
convert -loop 0 -delay 50 {FILES} -set filename:f “output_%t” “{desktop}/animated/%[filename:f].gif”

But it seems to happen even with simpler commands.

From Berkeley, CA.

It’s hard to guess without the plugin log… please make sure you’re using the most recent version of the plugin, then if you encounter the error again, please send a log. Thanks. —Jeffrey

Thank you, Jeffrey. I was not aware of this restriction. Alternatively, is there a way to put the UUID in one of the iptc or exif meta fields? how long would that take for a library of about 600,000 pictures? Would the LR assets/pictures need to be ‘online’ (all external drives attached) for this to work? Also – on export – would it be possible to rename the files to something like FirstName_LastName_UUID?

You can fill in a standard field with the UUID via my bag-o-goodies plugin. No idea how long it might take for 600,000 photos, but I imagine a while. It’s a database-only operation, so image files don’t need to be online. As for naming files on export, it’s trivial if you’ve stuffed the data info fields available to Lightroom filename templates. You might stuff “FirstName_LastName_UUID” into, for example, the Caption field, and use a filename template that refers to the caption. Also, some of my plugins (such as Collection Publisher) have enhanced-renaming support. —Jeffrey

howdy. After years of getting “the droplet couldn’t communicate with photoshop” found your plugin.
I have got it to work running with each image, but it produces an error: ‘the command attempted by the “run any command” filter failed’. Then lists the command path and file path (correctly). (But the next bit – path sent to OS has a 1 appended and another path at the end that I dont understand).

This is my command per image:
“C:\Users\me\AppData\Roaming\Adobe\Lightroom\Export Actions\3-2013 REAL STYLE other agents with blur group.exe” “{FILE}”

Its working – the image is exported and the action applied. I just get the error at the end.
also how would I get the droplet to run on all the images after export? Do I use {manifest} or {FILES}??

About the error you’re seeing, please send a log the next time you encounter it. As for how to run just once after the export, on all the exported files, that depends on how your target command works. If your exe command can be given a bunch of files on the command line and then do the right thing, you’d want {FILES}. —Jeffrey

Hello! I was referred to the “Run Any Command” plugin as a way to get around the Lightroom to Photoshop Droplet error of “droplet couldn’t communicate with Photoshop”. I can run a droplet with a handful of images, when I export a larger batch (20+ it begins to error out)… I’m told it’s something to do with the limit of characters being passed (too many) with it being a limitation of Windows. I am wanting to export via a droplet (in PS run some plugins & save) and after it saves, I need it to stack with the original image in Lightroom. What do I need to change so that I stop getting this error? Thanks for your time! ~Cathy

I’m afraid that I can’t offer any help… I don’t really know anything about “droplets” nor how they communicate with Photoshop. Just guessing from what you’ve described, though, I wonder whether it’s not a problem of asynchronicity, that is, running more than one at a time. Perhaps they have to be synchronous, but aren’t? —Jeffrey

Hi Jeffrey,

I’m trying to export images to a folder named after the `Title` metadata tag. I used mkdir ‘{Title}’ but I get a `permission denied` error. I’ve tried the same command in terminal and it worked fine in the same folder as the export.

Exemple of what I’m trying to achieve:

Images 1 to image 10 have title tag: 101-345
Images 11 to image 15 have title tag: 101-346
Images 16 to image 29 have title tag: 101-350

Result would be:

Folder name: 101-345
Content: images 1-10

Folder name: 101-346
Content: images 11-15

Folder name: 101-350
Content: images 16-29

Thanks

The command is not run from within the folder of the export… it’s run, I suppose, from your home directory (but even that you shouldn’t count on). You probably want to use a fully-qualified path, such as with {folder}. —Jeffrey

Is there any way to set up a command for exporting in a master folder (e.g. /myphoto) and move the exported photo in a sub-folder named after the catalog name (eg: /myphoto/my_catalog_name/ ) ?
I use several LR catalogues and i don’t feel like changing the destination folder any time i switch to a different catalogue. Many thanks in advance and congratulations for excellent work

mkdir "/myphoto/{CatalogName}";  cp "{FILE}"  "/myphoto/{CatalogName}/"

Hi,

Is it possible to automatically export photos – simply put I want a smart collection to automatically or every “x” minutes export a jpeg to a specific folder -?

If not, I am attempting through “Run Any Command” so that upon publishing of a “Pixieset” set/collection another Pixieset smart set/collection publishes. The pulldown “Publish this Collection” under “Command to execute upon Completion” only shows you collections from other Publish Services. I created a duplicate publish service of my Pixieset and they appear on the dropdown now, but when I set it up and Publish, it simply Publishes the 1st set, no the automatic.

The scenario is this: I send all photos to clients through pixieset – I create a set/collection in LR then export. While editing I want to mark photos with a Color Label and have a Smart Collection created. When I export my clients set/collection, I want the color marked Smart Collection to publish automatically?

Thanks!

I just added the “Publish Continuously” feature to my Bag-o-Goodies plugin, so if you get your photos into a Publish Service (e.g. with my Collection Publisher plugin or my Folder Publisher plugin, it should do what you want. —Jeffrey

When ever I run this plugin using “Export Batch” I get the following error.
LrCollection:addToCollection: must be called from within a withWriteAccessDo block
In this case I have each export add the images to a collection, and I find when I run them as a batch I get this error and then some of the image are not added to one or more collections.

This is likely a bug on my part… could you send a plugin log next time you encounter it? Thanks. —Jeffrey

Hi Jeffrey,

just switched from Lightroom 6 to Lightroom Classic and performed a plugin update to current version of run-any-command for Lightroom Classic. Sadly, I cannot add the plugin via plugin manager as Lightroom reports an error while loading the newly added plugin.

Any hint?
I don’t want to miss this great plugin.

Best regards
Markus

It’s difficult to guess what the problem might be (“an error” doesn’t tell much), but perhaps it was a problem with the self upgrade attempt. Perhaps delete the copies you might have on your system, and download a fresh copy for a manual install? —Jeffrey