XnView Software

Hello,

a few days ago, I tried to migrate from Adobe Lightroom Classic to XnView MP (Windows 11).

During importing of my pictures I realized, that XnView MP imported the (hierachical) keywords from JPG and DNG files only. It didn't import the (hierarchical) keywords from the XMP sidecars from all other RAW files (like RW2, RAF, ...). So if I search search/filter by keywords, only JPG and DNG files are shown. Selecting a picture with a camera specific RAW ending (e.g. RAF) does not show any keywords in XnView MP. Checking the appropriate XMP sidecar with a text editor, I am able to see the (hierarchical) keywords.

Any hints how to solve this behaviour? Did I make any errors during import?

Thanks in advance.

Bye,
OdysseusL

what do you have in Settings>Metadata-Sidecar?

Here is a screenshot (german).

I've tested it with both options: <filename>.xmp and <filename>.<extension>.xmp. The same result. From my point of view it seems as XnView MP does not read the XMP files written by Adobe Lightroom Classic.

could you send me an example?

Hello,

here is a link to Dropbox directory with a RAW photo and the associate XMP file:
https://www.dropbox.com/sh/85ll36gjbk4j ... 709ya?dl=0

I hope the link works for you.

I have the problem with all kind of RAW photos, except for DNG. I think, that keywords reading from DNG, JPG, and TIF works fine, is the fact, that metadata are stored in the photo files?

Thanks in advance.

ok, i found the problem. In .xmp, you have xmpMM:PreservedFileName with '_DSF0982.RAF', but the file name is 'Img_068138.RAF', so i don't load the .xmp. Perhaps it will be good to add an option to force loading??

I see.

I added two additional files in my Dropbox folder where the value of "xmpMM:PreservedFileName" is the same as the current filename, but XnView MP does not read the keywords (XMP file). Even if I re-import the appropriate directory in XnView MP.

So I'm not sure, if "xmpMM:PreservedFileName" the single source of the "problem" :-/

Nevertheless, an option to force loading would be ok, at least for me.

ok there is an issue with "PreservedFileName", See issue for current status and some details.

Hello "xnview",

thank you for your quick response. One question only: As described in an earlier response, I have the same problem, even if "PreservedFileName" is the same as the real current filename. Is this solved too?

OdysseusL wrote: Mon Apr 10, 2023 8:24 am thank you for your quick response. One question only: As described in an earlier response, I have the same problem, even if "PreservedFileName" is the same as the real current filename. Is this solved too?

this one is solved. When "PreservedFileName" is not the same, an option to force is useful?

Yes, at least for my current situation. Does there exist a release date for 1.44?

See issue for current status and some details.

OdysseusL wrote: Mon Apr 10, 2023 12:32 pm Does there exist a release date for 1.44?

next week...

These are good news. Thanks for your fantastic support!

This problem is supposed to be fixed in XnView MP 1.4.4. Please check and confirm the bug fix here.

Hello Pierre,

yes, it is fixed in 1.4.4. Thank you very much. One question only: Where may I find the new option regarding ""PreservedFileName"? I haven't find it until now (in Germany we say "maybe I have tomatoes on my eyes").