Batch convert output 'sort order'

Ask for help and post your question on how to use XnView MP.

Moderators: XnTriq, helmut, xnview

rnmerchant
Posts: 26
Joined: Wed Nov 04, 2020 2:05 am

Batch convert output 'sort order'

Post by rnmerchant »

I've a batch of files names "filename-###.jpg" - i.e. filename-001.jpg; filename-002.jpg, and so on.

When I do a batch convert (simple resize and reduce jpg quality), and outputting into another folder, the output files are reversed in sort order...

That is, input file 'filename-001' becomes output file 'filename2-050' and input file 'filename-050' becomes 'filename2-001'...

I am using a different filename for the output dialogue - I guess if I used one of the options where the original filename is preserved this wouldn't happen. But, why is this happening?
cday
XnThusiast
Posts: 3696
Joined: Sun Apr 29, 2012 9:45 am
Location: Cheltenham, U.K.

Re: convert + "sort order"

Post by cday »

I have made a quick test, and I think your issue probably arises from the sort order of your loaded images on the Input tab.

Please check whether the images on the Input tab are in the expected sort order, and if not click on the Name heading at the top-left of the window, which should reverse the order.

You live and learn, not something I had thought about before... :wink:
rnmerchant
Posts: 26
Joined: Wed Nov 04, 2020 2:05 am

Re: Batch convert output 'sort order'

Post by rnmerchant »

Thanks for your thoughts.

This may be correct but I am not sure why this is so. In my main window, the files are sorted by name (and in fact the same order is by create date a picture date as I renamed them all once sorted by date/time.)

But you are correct that in the input tab the images show up in reverse order. I see that I can reorder them by selecting the sort order by name, ascending (by clicking on the header) but that is too me a bit odd - I can't say I have ever changed that setting before (maybe I forget from times back but I don't think so as the batch convert isn't something I've done frequently).

This rather suggests that the default sort order is by something different than in the main XP directory (thumbnail) window. Why would that be so? And if so it seems that there should/could be a configuration option for that.... Maybe there is and I don't know - and I didn't know to look for it - My bad).

Thanks, anyway, for clarifying it. I think that if it were my choice, I would have the convert option inherit the sort order from the main thumbnail window, for my 25 cent opinion.

Richard
rnmerchant
Posts: 26
Joined: Wed Nov 04, 2020 2:05 am

Re: Batch convert output 'sort order'

Post by rnmerchant »

I see "presets" in the convert window. Is this something that this function does? I don't seem to have any presets.

Richard
cday
XnThusiast
Posts: 3696
Joined: Sun Apr 29, 2012 9:45 am
Location: Cheltenham, U.K.

Re: Batch convert output 'sort order'

Post by cday »

I think you are looking at the Actions tab, if you switch to the Input tab where you loaded your files all should hopefully be clear... :D
rnmerchant
Posts: 26
Joined: Wed Nov 04, 2020 2:05 am

Re: Batch convert output 'sort order'

Post by rnmerchant »

Nope, looking in the Input tab as you suggested.

But the 'presets' option is not in tabs, but part of the dialogue and visible where-ever, if this is what you are referring to in particular.
cday
XnThusiast
Posts: 3696
Joined: Sun Apr 29, 2012 9:45 am
Location: Cheltenham, U.K.

Re: Batch convert output 'sort order'

Post by cday »

I'm afraid I missed your longer post immediately before the post in which you mentioned Presets, which is as you say a button on the Input tab.

I agree, at a quick look, with your comments on expected sort order, and I have raised the issue under the XnConvert forum heading.

In a test I made (not sure now whether it was in 'MP Batch convert or in XnConvert) I reproduced the output filename inversion that you originally reported.

And on the Input tab, clicking on Name to reverse the displayed sort order corrected the output filename inversion. :D

Edit:

The cause of this issue has been confirmed and will be corrected in the next XnView MP version; meanwhile the simple workaround above may be used.