This is all done on CS6 with Lightroom 4.1 using a PC with windows 7. It opensPhotoshop but nothing happens. The droplet should create a number of layers to carry out a complex process, which works fine when the action is run. I'm sure I tested the droplet on its own too a few days ago but I will repeat that tomorrow. I will also create a simple action and droplet to see if that works. Teh thing is I have the same version of Lightroom on another computer, along with the last version of CS5 and that worked fine with the action. The action itself is from a well respected photoshop guru.
The only addition I made was the one he stated was needed to make it work as a batch. That is add a save command at the end. With or without nothing happens after export from lightroom though beyond photoshop opening if it is closed.
This one is getting messy! I thought I had checked the droplet on its own but apparently not as it did not work. I did then get a droplet to work with Photoshop in adminitrator mode. I then turned off the dreaded user control interface in windoze 7 and managed to get a droplet working with photoshop normally BUT.
While it seemed to run properly, when I went back to the folder I had told the export dialogue to save to the image still did not have the action applied.
Eventually I swapped over to bridge and tried from there. Fine. That was when I finally twigged that the action was indeed now being run on export from Lightroom. The only snag is instead of saving the result into the folder designated in the export dialogue box it was instead saving it back to the original folder! Of course I had not way of realising this in lightroom unless I synched the folder manually, something I had no reason to do.
To summarise. The export preset is set to
Export to original folder -but-
put in subfolder called processed
Add to catalogue
Rename to add '-processed' on the end
Do this as an 8 bit PSD
Post process run the specified Droplet, (which now has no save , save as or close in the action in case they were causinga conflict, just save and close selected in the droplet itself.)
Logically the last should just save over the previously exported PSD having run the action in the droplet. After all according to Adobe it runs this droplet AFTER the export is completed so should be running it on the image in the Processed folder.
Instead it is putting it back in the original folder, which suggests the action is actually being run as part of the initial export routine and screwing everything up.
Or am I missing something here?
So having done all that, does the droplet run and save correctly when you just drop photos on it?
And if you were to export to a completely different folder, does the droplet run and save correctly? (I'm wondering if there's a bug with that 'put in subfolder' option)
The droplet seems to now runs and creates the required file correctly with the layers and changes I expected, although I had to disable windows security feature to get it running. It just does not save it where instructed, which is a pretty big 'just' as I am trying to create a clean consistant workflow for the studio so I am not wasting hours on bread and butter editing that could be automated.
My guess is the same as yours but I've not found any serious threads on it despite a search. I guess there are not many people out there who have tried to make use of this feature. Which seems odd as there is scope for some pretty impressive workflow automation
Europe, Middle East and Africa