Batch Convert Suggestion: Multiple saves/version for same file

[grandtreebo]

First off, I want to say that I love XnView. I've been using it for years and I want to thank the developers for making such an amazing program. It is my go-to viewing and my go-to batch conversion program.

All that out of the way I wanted to add a suggestion, if I might, to the batch conversion process. What I do a lot is watermark my comic book pages and then make a small thumbnail for each. What I'm wondering is - can I do the multiple versions required all in one batch file? As you may guess what I do now is I run two batch files - one makes the watermark and saves it at full size - then I run another batch to make a smaller thumbnail which I also save. In the end I get two versions of the same image. What I would love, is in the batch process to have a command that just saves the current version/progress in the batch with the current save settings. Maybe there's already a way to do this without a new add?!?

Example process
- Create a batch of images to be watermarked
- Batch run the various commands to add the text for the watermark
- USE THE NEW SAVE COMMAND ("add "X" prefix to file name and save with current settings") - this creates a copy of the image with everything done to it up to this point
- Continue batch with the various resizing and cropping needed to make a thumbnail
- BATCH ENDS and saves as usual.

I want to stress this is not a monumental thing of importance!!! I ask about this because I batch thousands of comic book pages and it would be helpful for me. I doubt most people would ever use this but I thought I'd put it out there as an idea. Maybe it would be useful for a few people to make multiple versions of images in the same batch.

THANK YOU!

[user0]

correct workflow - use 2 runs
use Presets to quickly switch settings

[cday]

Another possible solution if you need this regularly, possibly not for you, use an NConvert script if all required actions are supported as they may well be...

[jkm]

Welcome to the forums…

You could write a small batch file/script and do everything in one pass using ImageMagick.

ImageMagick is a free, open source tool for doing manipulation of image files. It’s very capable.

https://imagemagick.org/

[cday]

@jkm: I think we crossed...

ImageMagick is certainly a well-regarded and very capable software that supports a very large number of actions, but I think xnview.com's NConvert could probably also be used to create a minimal batch file, in the possibly unlikely event that the OP is open to that approach.

[jkm]

@jkm: I think we crossed...

ImageMagick is certainly a well-regarded and very capable software that supports many actions, but I think xnview.com's NConvert could probably also be used to create a minimal batch file.

Hi, yes I think we must have been writing at the same time. I'm sure Nconvert could probably do it as well. I'm more familiar with ImageMagick; been using it since the 90s.

[cday]

Actually, the XnConvert option to 'Export for NConvert...' should allow much of the required code to be obtained directly, although as far as I know input and export terms at least are still not supported.

[grandtreebo]

Yo and thank you all so much for the replies and info. Lots of useful stuff!

correct workflow - use 2 runs
use Presets to quickly switch settings

Uh yah, that is what I do now. I *think* I mentioned in my original post I process two batches and thousands of (large) images at a time. Because of that I normally work on other things or walk away from the process while it goes. Switching batch settings wasn't the problem per-se, the suggestion I was making was only to ensure a full two runs in the most efficient amount of time. For small batches it's not a big deal of course, and what you suggest is what is already happening.

Thanks for taking a quick moment to share the idea though! The later suggestions were more in line with what I was looking for.

Another possible solution if you need this regularly, possibly not for you, use an NConvert script if all required actions are supported as they may well be...

Thank you! I will look into that! (edit: just did and wow!)

Welcome to the forums…
You could write a small batch file/script and do everything in one pass using ImageMagick.
ImageMagick is a free, open source tool for doing manipulation of image files. It’s very capable.
https://imagemagick.org/

Did not know about it and I will check it out! (edit: checked the links and thank you!)

Thank you again cday and jkm! Appreciate everyone's info and time! Stay awesome!

[alee001]

Just passing by...

Haha, using Photoshop is the fastest and easiest if you have it.

[grandtreebo]

Just passing by...

Haha, using Photoshop is the fastest and easiest if you have it.

Appreciate the passing by. Don't have Photoshop and the answers above already hit the mark as I mentioned.

Thank you!

[xnview]

in next version i've added a way to export multiple resized version

[xnview]

This problem is supposed to be fixed in XnView MP 1.10.4. Please check and confirm the bug fix here.

[user0]

in next version i've added a way to export multiple resized version

well, this is not how it should be done
- it is not scalable. why multiple resolutions? the next user will ask for multiple formats, compression levels, ratios, etc.
- it breaks clean straightforward logic (input>actions>output), there simply shouldn't be any follow-up actions in output tab

that isn't even necessary, since you already can use multiple instances to achieve any result
(set watch/hot folder in the 1st-Nth instance(s) and modify files produced by the last instance)

the correct way of doing this unnecessary overengineering in a single instance:
- job queue / task system (eg like in video editors, 3d renderers)
- actions branching +new file operation actions if you want to share intermediate state

[xnview]

well, this is not how it should be done
- it is not scalable. why multiple resolutions? the next user will ask for multiple formats, compression levels, ratios, etc.
- it breaks clean straightforward logic (input>actions>output), there simply shouldn't be any follow-up actions in output tab

that isn't even necessary, since you already can use multiple instances to achieve any result
(set watch/hot folder in the 1st-Nth instance(s) and modify files produced by the last instance)

the correct way of doing this unnecessary overengineering in a single instance:
- job queue / task system (eg like in video editors, 3d renderers)
- actions branching +new file operation actions if you want to share intermediate state

so you would like to move 'multiple resolution' in an action 'save'?

[cday]

What is needed, perhaps, is something like the following suggestion:

Proposal to add support for output of alternative versions of input files

... implemented in a basic form that allows a set of actions to be duplicated to a second tab, and then edited in the same ways as in the copied 'thread', to allow output settings (and any other settings...) to be changed to provide the desired output versions.

Simple duplication to a second 'thread' shouldn't be too difficult, and probably wouldn't greatly increase the overall app size?

Edit:

The fact that code common to the two 'threads' would be run twice shouldn't be an issue, a small price to pay, and should significantly simply implementation.