Ping does not read XMP profile of DNG image

[mustafaoral]

Similar to #1953 but for DNG files.

Package: Magick.NET-Q8-x64
Version: 14.15.0
OS: Windows 11

Using Ping() to load metadata of a DNG image doesn't seem to process the XMP profile, returning null when .GetXmpProfile() is called. I'm not sure if this is by design or a bug.

The only workaround seems to be a full read, which is orders of magnitude slower.

For my use case, I'm interested in crs:RawFileName and/or xapMM:PreservedFileName keys.

Here's a link to an example file: dng

[dlemstra]

Good news! It turns out the xmp profile is read before the image data is read. This means that we can read this data when pinging the image. This change will become available in the next release.

[dlemstra]

I am thinking about adding a unit test for this but I cannot find a small sample file that contains an xmp profile. Could you help me with that?

[mustafaoral]

Hey Dirk. Thank you for investigating so quickly.

Here's a DNG that is ~365 KB in size: link. I have produced it using the lossy compression option in Adove DNG converter. That is not my normal workflow, so this one is not like-for-like to the original file I provided.

This does not have values for the crs:RawFileName or xapMM:PreservedFileName keys I'm interested in, but it does have an XMP profile, i.e. .GetXmpProfile() will return a non-null value.

[dlemstra]

Thanks for your help. I have added a unit tests that makes sure that the XmpProfile is read that with that image you provided is being pinged.

[dlemstra]

A new release has been published and you should be able to read the information when you ping the image.