New XmpProfile for PNG #1603
Replies: 3 comments 3 replies
-
It looks like you are creating an empty xmp profile? If you give me something to reproduce this error message I might be able to give you an answer why this is happening. |
Beta Was this translation helpful? Give feedback.
-
My hypothesis on the exiftool forums. There's a BOM (Byte Order Mark) at the beginning of the XMP block that I don't think should be there, though Phil will have to verify it. There has been trouble before with Directory Opus and BOMs in the metadata on the exiftool forums. There are several threads started by user mazeckenrode which have details. |
Beta Was this translation helpful? Give feedback.
-
I believe it is allowed by the spec, so they are not in the wrong. The reason exiftool flags it is because some programs do not read data in those locations. See this exiftool forums thread. |
Beta Was this translation helpful? Give feedback.
-
What is the best way to add XMP metadata to a PNG iimage?
Regardless of whether I add to an existing XmpProfile, or create a new one, I get these types of warnings from exiftool. If the image already had XMP metadata, exiftool could extract it fine... until I use Magick.NET to add XMP metadata.
Warning : [minor] Empty XMP
Warning : [minor] Text/EXIF chunk(s) found after PNG IDAT (may be ignored by some readers)
And it will no longer show the XMP metadata that it understood before this.
Beta Was this translation helpful? Give feedback.
All reactions