Keep Exifmetadata inconsistent w.r.t. Samsung Trailer / BLOB Data

Ask for help and post your question on how to use XnView MP.

Moderators: XnTriq, helmut, xnview

sx090
Posts: 25
Joined: Thu Jan 11, 2024 8:49 am

Keep Exifmetadata inconsistent w.r.t. Samsung Trailer / BLOB Data

Post by sx090 »

Hey there,

this is a pretty special and complex topic it seems.

Both in XnView as well as XnConvert, when converting/compressing a JPG (overwriting the original one to compress a bit), when using the Option "Keep EXIF Metadata", not al EXIF Metadata is retained.

Most of the "Samsung Trailer" (Idk, what this exactly is) as well as the Embedded Images and Depth Maps (DepthMapData, DepthMapTiff) are removed.

Interestingly, not ALL Blobs are removed. There is specifically an entry called "OtherImage" which is causing even problems with Exiftool when trying to write changes to the EXIF of this file, also see this thread: https://exiftool.org/forum/index.php?topic=15823.0 - Funnily, specifically this problematic entry is kept by XnView/Convert. This tag "OtherImage" is inserted as soon as one "edits" the image within the Samsung Gallery app.

Now my question is:
1) Would it be possible to also remove the "OtherImage" entry as it blocks Exiftool from making any changes to the Image later on in case wanted. As per thread above, this is anyhow not needed data or an corrupt binary file.

2) Would it be possible to be able to configure somehow (maybe only in XnView ini expert settings or so) which BLOBs to keep while compressing/converting JPGs? I'd like to remove the embedded Original image for sure (as it is) BUT keep the Depth Maps (DepthMapData) - because this can be used by image editing SW to know the depth of objects in the picture.

Thank you for your consideration!
User avatar
xnview
Author of XnView
Posts: 44759
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: Keep Exifmetadata inconsistent w.r.t. Samsung Trailer / BLOB Data

Post by xnview »

could you post a sample file?
Pierre.
sx090
Posts: 25
Joined: Thu Jan 11, 2024 8:49 am

Re: Keep Exifmetadata inconsistent w.r.t. Samsung Trailer / BLOB Data

Post by sx090 »

yes sure, here you are, a few sample files, all recorded with my Samsung S23 default camera app.
https://www.dropbox.com/scl/fo/jkvhee51 ... yt0h1&dl=0

I uploaded 4 pictures:

1) Captured in portrait mode (-> includes a few binary files, including BLOB DepthMap). I uploaded this one to Dropbox before actually editing it in the Gallery App, and yet it already contains the original image as full copy inside the metadata (EXIF "Embedded Image").

2) Than I edited that portrait shot from 1) -> Keeps all metadata, the original image can even be still extracted from the EXIF "Embedded Image", and funnily, changes the Byte Order from Little-Endian to Big-endian Motorola!?

3) This one is a "regular / normal" snapshot without portrait - Does not contain neither DepthMap nor the original Image as Binary inside EXIF

4) I edited the regular one from 3) but still, the "Original Image" is not embedded. BUT: funnily I can still "Reset to original" within the Samsung Gallery App. I don't get this at all.

So my key takeaways:
* DepthMap Binary BLOB is only embedded in case of Portrait mode - this might really be useful for image editing on the computer - so it would be nice to at least be able to keep this data somehow using XnConvert / XnView MP Convert.
* The original Image as Copy in EXIF "Embedded Image" is embedded in portrait mode, irrespectively if you edit the image or not - I think this should be removed / deleted from EXIF in most cases (which it already is when converting using XnConvert / XnView MP Convert)

Thanks for your consideration!