Wrong/incomplete file metadata displayed

[AMack]

After the last update (5.0.0.2426, standalone, W10) file metadata isn't displayed completely and partly wrong. Camera and lens information (EXIF) are missing completely, Author/Copyright is displayed in non-Raw versions only. File size is displayed incorrectly for CR2 files.

[Hert]

This sounds like a metadata difference between Exif and XMP. Try to right click on the file and select Metadata-Convert metadata to XMP.
Does that bring in the metadata?

[AMack]

Thank you for your reply. I tried that but got an error message box (screenshot attached). Basically, I didn't have any problems so far, and I don't have a new camera oder different file types in use; so why would the application behave differently all of sudden? Just a thought: Could it be somme kind of file access (read/write) phenomenon? That could also be the case for my other problem posted in the forum (viewtopic.php?f=57&t=27785&p=123031#p123031).

[Hert]

That error means that psu found incorrect formatted XMP. Try to delete the XMP sidecar for that file (make a backup of the file if you think needed)

[AMack]

I tried that and did not get any further because there aren't any XMP files in the directory. It appears psu is not able to write them.

[Hert]

What about removing that image from the catalog and then import it again with “Import single files” from the hamburger menu. Does that help?

[AMack]

No, it doesn't help. No XMP is written when re-importing the image after removing it from the catalog. Ctrl+S won't change that either.

[Hert]

That’s useful info. And are you using embedded metadata for RAW files?
And do you still get that error?

[AMack]

Update

After unfortunately having been too busy with other things, I’ve now returned to my still existing PSU problem. I hope a couple of new observations might shed a different or at least slightly brighter light at things... As to your question, I think I don't use embedded metadata, but have attached my sync settings so that you can see for yourself. Suggestions for a useful setup always welcome !

Now for my current observations:

1. PSU is not able to export affected files using a batch process. I attach the resulting error message.

2. When I copied a „good“ file to a „bad“ directory using PSU’s copy/paste functions, syncing for this file still was doing. So one image was OK, the next one in this directory (even by the image number) not. -- I extracted the neighbouring files‘ EXIF information (with a different tool, IrfanView) and saved them to an Excel file which I can provide. I couldn’t find any hint about changed entries, though.

3. Copying a file directly from the camera, thereby avoiding Canon’s EOS Utility, didn’t lead to a different result.

4. On the other hand, newly shot CR2s with another, older, camera in a different directory are handled without problems. This shows newer images still can be managed and „understood“ by PSU, therefore indicating there’s no general problem with files after a specific point of time. (I didn’t import them with a Canon tool, but by transferring the files using Windows Explorer.)

5. Files from our latest camera, M50, in Canon‘s CR3 format aren’t synced and properly read either.

6. The incapability of reading EXIF information applies to TIFFs „developed“ from the raw files also.

7. I compared security settings for both the images and the directroies they’re in from before and after the behavioural change, bit couldn’t find any hint about different settings (caused maybe by Windows or Canon software updates).

8. My current (humble) idea ist that PSU rather doesn’t write XMP files because it cannot extract information from the images in the first place, instead of not having writing permission for the directoy.

There are no problems whatsoever opening and editing the images in DxO Photo Lab and Affinity Photo. Metadata is shown properly.

[Hert]

This error indicates that the XMP in your file is incorrectly formatted.
Psu can possibly fix that for you, try a right click -> Metadata -> Convert metadata to XMP.
Does that help?

[AMack]

No, unfortunately this also failed. (Error message attached.) I also tried "store metadata to file", but PSU doesn't succeed; the progress is not progressing at all, but remaining at 0,0%.

[Hert]

Can you upload your XMP file and share a link (here or by email). What software do you expect that wrote the XMP?

[AMack]

Thank you for your reply. Took me some time to get back to the problem.

PSU does not write XMP files in new folders from the point of time on the problems described above started.

The files still get registered with the database (file name and thumbnail), and I still can set rating, status colours, tags, and relate files to each other (versioning). Thumbnails is displayed.

It appears PSU is not capable of retrieving meta data out the files from a specific point of time (or directories created after a specific point of time) on. The problems' first occurrence corresponds with a new folder on my disk. I.e. no problems with 2019-08 (and until then), but with 2019-09 (and onward ever since). Same in different directory branch.

My impression ist PSU does not get a grip on metadata and therefore isn't able of writing an XMP file which requires values to be filled with and not NULL (so to say).

The problems encoutered are all describes above, but I will try and summarize them in a brief overview again.

[Hert]

The error message that you displayed *always* means that your XMP contains entries that do not comply with the XML/RDF (the format for XMP) rules. That’s why I asked for a sample file.

Please provide a sample first. You can share it here or send it to support@idimager.com

Thank you

[AMack]

Maybe I'm not getting it, sorry, but how can I provide an XMP if there is none? PSU does not write any XMPs into the directories as described.

Thanks for your help
Andreas