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?
