Batch convert -- Saving output to a relative folder

[winnylinny]

A tooltip or explanation needs to more clearly offer a hint when selecting an output folder under Batch Convert.

relative-folder.png

I didn't even know this was possible, until I found out by mistake!

I kept using the "source folder" option, because I did not want to save my converted files to the same folder on my drive every time. Images exist in different albums and folders, so I was hoping there was a way to save the converted files into a relative output folder.

Guess what? It's possible! I just never knew because it was not explained!

---

This works on Linux, and I assume it is the same with Windows? New users might not know that XnViewMP's batch convert even supports "relative output folder" since no hints are provided.

[cday]

An interesting discovery, possibly not an intended option...?

Regarding syntax, mightn't a 'slash' be more intuitive, accept either '/' or '\', for example /converted ?

Out of interest, if the named folder does not already exist, is it possibly created automatically when needed?

Regarding documentation, for a developer testing is boring, documentation is even more boring, so volunteers are always welcome...

[winnylinny]

Out of interest, if the named folder does not already exist, is it possibly created automatically when needed?

Yes. If the folder does not exist, it is automatically created.

In fact, you can even specify a further nested relative output folder, such as:

• converted/webp
• converted/jpg
• converted/png

It works as you expect: It will save the newly converted files two folders down relative from the source folder.

This has beautifully improved my workflow. I wish I knew about this feature much earlier!

I believe more users will benefit if they knew about this feature in Batch Convert.

Regarding syntax, mightn't a 'slash' be more intuitive, accept either '/' or '\', for example /converted ?

Leading slashes denote an absolute path. This will attempt to save it to the root of the filesystem. This is why if you use the "browse" button to select the output folder, it will use the complete absolute path, which leads with a slash. (In Windows, this is the equivalent of typing C:\converted )

[cday]

This has beautifully improved my workflow. I wish I knew about this feature much earlier!

Maybe Pierre does too?

Regarding syntax, mightn't a 'slash' be more intuitive, accept either '/' or '\', for example /converted ?

Leading slashes denote an absolute path. This will attempt to save it to the root of the filesystem. This is why if you use the "browse" button to select the output folder, it will use the complete absolute path, which leads with a slash. (In Windows, this is the equivalent of typing C:\converted )

Either slash would be incorrect? A slash is normally used in the path to a subfolder?

[winnylinny]

Maybe Pierre does too?

It's a great feature, and should remain! Accident or not.

Either slash would be incorrect? A slash is normally used in the path to a subfolder?

Any slash put in the beginning of a path is considered "start from the root of the filesystem". Whereas, if you begin with the folder name (without a leading slash), it is interpreted as "start from the current directory".

Any slashes that come later are considered part of the absolute or relative path.



Some examples, if the source folder is /home/cday/Pictures/batch


Typing in /converted will save the converted files into:

• /converted

Typing in converted will save the converted files into:

• /home/cday/Pictures/batch/converted

Typing in /home/cday/Pictures/batch/converted will save the converted files into:

• /home/cday/Pictures/batch/converted

Typing in converted/webp will save the converted files into:

• /home/cday/Pictures/batch/converted/webp

[cday]

Thanks for the paths explanation, I think that my reasoning was that the Source folder part of the path was implied, so that /converted/some_folder with the slash would be logical. Never mind though, you have now documented a previously undocumented feature that might be useful to others.

[winnylinny]

Never mind though, you have now documented a previously undocumented feature that might be useful to others.

That's why I think a clear explanation or tooltip or "hint" should be printed on this page. It can help more people.


(FYI: I made some REALLY BAD TYPOS in my previous post. I've correct them!)