XnView Software

To ensure you do not break them in the future using XnViewMP, ensure the "Link companion files for the following actions" options are enabled on Settings:File list:Companion files.


Do you mean me to check the boxes "delete" and "copy/move/rename". That makes sense, though it won't fix the problem I'm having right now.
Correct on both counts. Necessary for future, not related to your current problem.


Beyond that, check that you have some settings correct:


I've had a look and the settings you mentioned are all correct.

It's a puzzle. The only reason for my initial speculation was a post I found when searching for a solution. Note that this only affects the files that I imported with a date added to the file name (the xmp files have the same name, added date and all). Other raw files imported previously are unaffected. I couldn't find an ini file to test the solution proposed there:
https://newsgroup.xnview.com/viewtopic.php?t=45638

Hmm, ok, and you've selected the images and done update catalog from files?

Yes you can have problems if you're trying to preserve the original name in the metadata. Trying the setting in that thread is a good idea.

Your ini file (xnview.ini) is in one of two places, depending on what you chose when you installed the application.
It is either in the directory where XnViewMP.exe is (check the location on your app shortcut) or it is in C:\Users\%USERNAME%\AppData\Roaming\XnViewMP


If you edit the xnview.ini file, make sure the app is closed before you do so. The app re-writes the file on exit.

One last thing to check (for future, not for the current issue) is in Settings:Formats:Write ensure that all the "Keep" options at the bottom are enabled. This will ensure when writing XMP files that all the data types are included.

Thank you very much for your detailed response. I've checked everything you mentioned, but have had no luck in figuring this out yet.


The name of the xmp file must have the same base name as the master file. So for a master file named A12345.cr3, there are only two acceptable names for the xmp:
A12345.xmp or A12345.cr3.xmp


The xmp files have the exact same base name as the master file in every case. (The xmp files were created after I imported the master files into lightroom so they were assigned the same name by lightroom.)


To ensure you do not break them in the future using XnViewMP, ensure the "Link companion files for the following actions" options are enabled on Settings:File list:Companion files.


Do you mean me to check the boxes "delete" and "copy/move/rename". That makes sense, though it won't fix the problem I'm having right now.


Beyond that, check that you have some settings correct:


I've had a look and the settings you mentioned are all correct.

It's a puzzle. The only reason for my initial speculation was a post I found when searching for a solution. Note that this only affects the files that I imported with a date added to the file name (the xmp files have the same name, added date and all). Other raw files imported previously are unaffected. I couldn't find an ini file to test the solution proposed there:
https://newsgroup.xnview.com/viewtopic.php?t=45638

Therefore, I'm wondering if the problem might be because I imported files into lightroom from the camera and, when doing so, I changed the name of the files to include the date as well as the name assigned by the camera, but that's speculation.

Regarding the above comment, if you only renamed the cr3 and not the xmp files, that was a mistake. If you now have files something like A12345-08-12-25.cr3 and A12345.cr3.xmp then you have indeed broken the xmp files.

The name of the xmp file must have the same base name as the master file. So for a master file named A12345.cr3, there are only two acceptable names for the xmp:
A12345.xmp or A12345.cr3.xmp

It is advisable to adhere to the .cr3.xmp standard.

You can rename files all you want, but the xmp files must be renamed to match. So if you have files named something like:
A12345-08-12-25.cr3 and A12345-08-12-25.cr3.xmp then you should be ok, since both the cr3 and xmp have the same base name.

The only solution for breaking your xmp files in that way is renaming things so they match again. To ensure you do not break them in the future using XnViewMP, ensure the "Link companion files for the following actions" options are enabled on Settings:File list:Companion files.

Beyond that, check that you have some settings correct:

-In Settings:File List:Companion files you should have:

Master Extension
*

Companion
{ext}.xmp;xmp

In Settings:Metadata, ensure all the Import options are selected (really, check all the options on that page)

In Settings:Metadata:Sidecar, ensure the Naming Convention matches the naming of your sidecar files. Since you will probably want to save metadata in sidecars as well, put a check by "Create or Update XMP Sidecar", and then also activate the export options on the Metadata page.

After all that is done, restart the app just to be safe, and then select the files in the browser from the Menu select Metadata->Update Catalog from FIles.

I haven't figured out how to display both formats in this directory.

check 'Show companion files'
in Settings>Filelist>Companion files

sorry but currently no way

Hi all,

Since MP has one of the best databases out there, i'm using XnView MP for previewing my 3d objects too.
By the way i must tag both the LWOs (3d object) and their thumbnails in order to see them correctly, since XnView cannot create a thumbnail for the LWO itself - see image below.

I would love to filter the list and see only the LWO files, but i would need to assign them the jpg (which has same name of the LWO) as a thumbnail. I tried the "companion" file thing, where i've set LWO as master and JPG as companion, but nothing happens. I also tried the opposite but again nothing happens.

Is there a real way to force XnView to replace the LWO thumbnails with the JPG that has same name ?

Thanks,
Paolo

Screenshot_1.png

Just by the by, I'd rather not use sidecar files for my routine photos. Too "messy" to deal with, doubling the number of files in use... Works fine if the only thing you use is the particular application using the files but if I use another - a file manager, for example, then I have all these 'random' (well, perhaps not random) files hanging around. ON1 does this - creates a file (*.on1) for every photo that it catalogues and I spend time deleting them...

Just my preferences.

Richard

Ideally, I want a set-up that mimics this :
- I shoot in RAW+JPG, so after importing I want files to be linked so that I do not see duplicated images.
- I want the actions I perform through the culling process to be applied to each photo (If I rate an image, the rating applies to the companion JPG file as well as the RAW that I've rated (or vice versa)


Configure companion files, then enable sidecar files and configure your ratings to be to be saved there.

The software can already do what you’re asking.

I second this request. :wink:

Ideally, I want a set-up that mimics this :
- I shoot in RAW+JPG, so after importing I want files to be linked so that I do not see duplicated images.
- I want the actions I perform through the culling process to be applied to each photo (If I rate an image, the rating applies to the companion JPG file as well as the RAW that I've rated (or vice versa)

- My personal desired methodology :
- Rating 5 stars: (Keeps RAW+JPG) photos I absolutely want to keep and will likely post
- Rating 4 stars: (Keeps RAW+JPG) photos that are great and backups to post
- Rating 3 stars: (Keeps RAW+JPG) May review later and are average at best. May have been shot more for the memory rather than the quality
- Rating 2 stars: (Keeps JPG only) Keeping the JPG only for the purpose of memory. no intention to potentially edit in the future
- Rating 1 star: Honestly, don't even plan to use this. I figure everything else that doesn't make the list above would be deleted.

Bonjour,
Merci pour la réponse.
J'utilise la version 1.9.3 64-bit pour Windows.
Dans les paramètres Métadonnées, j'ai trois lignes : Companion, Encodage et Libellés de couleur

Hi,

To show companion files, it must be activated in the parameters/file list/companion files

Settings>Companion files - show companion files

Currently when a file is loaded, XnView checks always if there is file.xm or file.ext.xmp

Should this be according to the activation of the 'Create or update XMP sidecar' setting?


No, "creating or updating" a sidecar file should be a separate option.

You said it "ALWAYS" checks.

When opening a file, It should only check (and then read the XMP) if the IMPORT options are checked on the Metadata page.

It should only write the file if "Create or update XMP sidecar" is checked.

As for the companion file settings, it only needs to check and process the XMP if the master file is deleted, moved, or renamed.

nope
I think it should stay like this:
read (Settings > Companion files)
* -- {ext}.xmp;xmp in Association list


write (Settings > Metadata > Sidecar)
'Create or update XMP sidecar' checkbox



On the other hand, I would probably merge these 2 settings tabs somehow as sidecar is a subset of companion files