https://bugs.kde.org/show_bug.cgi?id=524434
--- Comment #18 from lovr377 <[email protected]> --- (In reply to Maik Qualmann from comment #17) > The "problematic" image definitely contains no motion video data. Although > the flag is set, the binary data is missing. There is nothing we can fix > here. I am closing this now. > > Maik Hi Maik, This image is captured by Xiaomi 14. The motion‑photo micro‑video data is definitely intact. It can play normally in the native Xiaomi Gallery, and also works fine in Google Photos. I downloaded this original file directly from cloud disk, no re‑encoding or modification was done. I think the root cause is that Xiaomi uses its private extended XMP metadata for micro‑video offset, different from Google Pixel standard motion‑photo tags. Digikam/Exiv2 cannot parse Xiaomi‑specific offset field, so it judges that binary video data is missing. But the actual embedded MP4 video still exists inside the file. Additionally I found another serious regression: For Xiaomi motion‑photo files that still work correctly, if I rotate the photo directly via Digikam thumbnail context menu, the embedded micro‑video will get lost after saving. After this rotation operation, even the original Xiaomi system gallery can no longer play the motion‑video. The rotation operation strips off the appended micro‑video binary segment inside JPG/HEIC file. Sample original test file for reproduction is available here: https://drive.google.com/file/d/1cSfxzmpdSFahM22uyb1f7H8jCUS7AP3-/view?usp=sharing Please reconsider this issue, this is not a corrupted file. -- You are receiving this mail because: You are watching all bug changes.
