I have just upgraded to 1.91.6, but I can't get the new companion files feature working, and the default companion file handling (which was fine in 1.914) seems to be disabled.
Firstly, I want to move/copy .JPG files when I move/copy the RAW file (.CR2). This was default behaviour before, but seems to have stopped working.
Secondly, I'd ideally like to move, at the same time, the Bibble Pro sidecar file (which will have an extension of .CR2.bib). Can this be done?
andrewj wrote:I have just upgraded to 1.91.6, but I can't get the new companion files feature working, and the default companion file handling (which was fine in 1.914) seems to be disabled.
Firstly, I want to move/copy .JPG files when I move/copy the RAW file (.CR2). This was default behaviour before, but seems to have stopped working.
Secondly, I'd ideally like to move, at the same time, the Bibble Pro sidecar file (which will have an extension of .CR2.bib). Can this be done?
Do you have tried to change the CompanionFile in xnview.ini?
Dear Pierre,
I'm trying to use the latest test version, and I've come across a problem. If I pick up and drag the .CR2 file, I want it to take the .JPG and the .CR2.BIB with it. This works fine.
However, if I pick up the .JPG I don't want to move the other files. This allows me to move this to a different output directory from the originals if I want to.
I've currently got the following two entries in the ini file:
Companion_00=cr2:jpg
Companion_01=cr2:cr2.bib
I've got rid of the line mapping jpg to cr2.
Logically this should give me the behaviour I want. Can we fix this?
Thanks
andrewj wrote:Dear Pierre,
I'm trying to use the latest test version, and I've come across a problem. If I pick up and drag the .CR2 file, I want it to take the .JPG and the .CR2.BIB with it. This works fine.
However, if I pick up the .JPG I don't want to move the other files. This allows me to move this to a different output directory from the originals if I want to.
I've currently got the following two entries in the ini file:
Companion_00=cr2:jpg
Companion_01=cr2:cr2.bib
I've got rid of the line mapping jpg to cr2.
Logically this should give me the behaviour I want. Can we fix this?
Thanks
Andrew
Ok right. Currently i check cr2=>jpg AND jpg=>cr2!
Pierre - thanks for fixing this. It works like a dream now.
I suggest we need a couple of lines of instruction added to the "companion files" page in the help file. If it helps, I've drafted the following as a starter:
XnView allows you full control over how companion files are managed. You turn companion file handling on and off in the "File Operations" tab under Tools/Options.../"General". The detail behaviour then depends on lines in the [File] section of XnView.ini
For each pair of file types, you need a line like:
This means that file operations such as move, copy and delete on a Canon RAW file with extension .CR2 will also affect the companion file with extension .JPG
You can have up to 100 associations, but each line must have a different number before the "=" sign.
The system can also accomodate files where a new extension is appended to the original one. E.g. Bibble adds .bib to the RAW filename, so you need a line like the following:
The associations only work one way. E.g. the above only work if you act on the .CR2 file. This makes it easy to manage output files separately from the other associated files. If you want the associations to work both ways you will need lines mapping the other way, e.g.:
Apparantly the reason for the inflationary application of "Companion_xx" is that "JPEG"/"JPG" and "TIFF"/"TIF" are separate extensions. Also the declaration is only one-way. Suggestions:
use "::" instead of ":" to indicate bidirectional binding
Another problem is that XnViewMP 0.39 seems not so supprt "Companion_xx".
This might by natural, however, since its ini-file not even has a "[File]" section.