Every compression attempt results in the error ‘Unable to compute the base path for the files’

[Proximanova-Metropolis]

I want to compress multiple images in a folder (including subfolders) while preserving the date attributes. I also want existing images to be overwritten without creating a new output folder. Every single time I try to use CaseiumCLT, despite cross-checking that the syntax is correct (i.e., caesiumclt --lossless -RS --same-folder-as-input Downloads or caesiumclt --lossless -RS --same-folder-as-input *.jpg), I always get the same result: Unable to compute the base path for the files. No matter what arguments I change, whether I specify the parent folder name or *.jpg, the result is always the same.

The progam works only when I specify the name of an individual file in the arguments, NOT when I specify the name of a folder — but that would defeat its purpose for me, since I have thousands of photos in subfolders that I need to compress.

There is no help online for this error. For the record, I run Version 1.2.0 on Windows 11.

[Lymphatus]

Where is the caesiumclt executable located?
You can know the path by running in the CMD

where caesiumclt

I see you give Downloads as the input path, but if the executable it's not in the same folder as the Downloads one, it won't work.
Try giving the full absolute path, for example

C:\Users\{YOUR_USERNAME_HERE}\Downloads

Same applies if you run with *.jpg as parameter: if the executable is located in a folder without any jpg image inside, it gives you the error.

[JeckPeppinger]

nope, cannot confirm, the files were found in previous versions and now the same command line creates this error that its unable to compute the base path. This indicates a clear error in caesiumclt 1.3.0.

Only full absolute path work! Everything else creates the error. why the tool has an error to calcuate a base path is unclear, but thats a simple function call in bash (basename).

[JeckPeppinger]

"funny" what AI just wrote:

[Lymphatus]

I made some changes on how the file structure is calculated in this version, so this might be a new bug. It would be very helpful if you could tell me how to replicate it, so I can solve it.

For example, if you could provide me:

• caesiumclt version
• caesiumclt command executed (and in which directory is it called)
• caesiumclt executable location (where or which command depending on the OS)
• Operating System

AI is very good at making useful bug reports, by the way.

[JeckPeppinger]

Any command with an input file will do.

caesiumclt 1.3.0

Ubuntu 25.10

The location of the caesium binary to the image files is entirely irrelevant as long as the binary is in the path.

Only absolute fully qualified path work.

[Lymphatus]

I'm sorry, but I cannot reproduce the issue with the info you gave me.
If I'm asking for detailed information, it's because it's necessary to me to be able to properly debug the issue.

Any command with an input file will do.

This is not helpful at all. Please provide me a full command that gives error. If another command, with different parameters, result in the same error, giving me also that command really helps me tackle possible problems.

The location of the caesium binary to the image files is entirely irrelevant as long as the binary is in the path.

I had some issues in the past, especially on Windows, relative to the executable location. That's why I'm asking. It might be irrelevant for your case, but an extra info is better than no info at all.

Only absolute fully qualified path work.

A command that does not work and a command that does work are key for me to understand. Please provide both.

What I am trying to understand is if you are pointing to a folder by relative path, but that folder is non existent and the error is misleading. The folder in which you are trying to launch caesiumclt (pwd command) is also a very useful information.

So please, provide me:

• pwd output before launching caesiumclt
• ls -la output before launching caesiumclt
• the full command you execute that results in a error
• the full command that does not give the error, with the fully qualified absolute path