Batch Action ignoring 'Overide Action "Save As" Command'

[Jeff Clatworthy]

Can anyone offer any advice on fixing the Export location step in the Action I build for interractively batch processing product images? When I run the action as a batch process, it ignores the  'Overide Action "Save As" Command' setting in the Batch panel, and instead insists on using the original Test location that was recorded in the Action (it will error and fail if this Folder  isn't present in the original location).

I don't know if it is relevant, but both the Source folder and the intended Target folders are on Server volumes. 

[Stephen Marsh]

@Jeff Clatworthy 

You need to use Save As, not Export for the override to work.

You would need to add extra steps to remove metadata or perform other operations that Export Save for Web performs. Or process the output files as a second pass step.

[Jeff Clatworthy]

Unfortunately I need to use Export: Save for Web to optimise the files suitably for our new website. This action's purpose it to streamline the uniform cropping and optimising of likely thousands of product images for web use.

[Stephen Marsh]

Unfortunately, this is the wrong tool for the job, batch override doesn't work with export.

A script could batch using your S4W settings.

EDIT: It is risky to work to/from remote volumes, best practice to copy the files and work locally.

[Jeff Clatworthy]

I also forgot to add that one of the perks of 'Export Save for Web' is that it forces output as  flattened RGB. We have a mix of CMYK and RGB high res images in various layer states, which would otherwise require a lot of complicated conditional steps that are beyond my skillset.

[Jeff Clatworthy]

I took your advice and rebuilt the Action to include a conditional "If CMYK, then convert to RGB, else None" step, then used Save As with more aggressive compression. As you stated, it now behaves correcting when batching. The files are still slightly, but not significantly, larger (any saved paths are not disposed of, plus some previews and metadata are presumably still inlcuded), but your method was the correct one. Thank you for your help 🙂

[Stephen Marsh]

The files are still slightly, but not significantly, larger (any saved paths are not disposed of, plus some previews and metadata are presumably still inlcuded), but your method was the correct one. Thank you for your help 🙂

By @Jeff Clatworthy

You're welcome. Please mark my previous reply as the correct answer.

The following script will remove all paths, no matter the name:

https://snipit.io/public/collections/22396/22396/74743

This can be installed and recorded into the action:

https://prepression.blogspot.com/2017/11/downloading-and-installing-adobe-scripts.html

Just make sure that you don't save over the original file and lose the path/s!

Metadata can also be removed via scripting or perhaps the application of a metadata template in the action.

[Stephen Marsh]

As this is interactive batching you could set the modal control next to the export step and possibly manually override each save. You have done this for the crop step in your action screenshot.