SUMMARY Apparently, editing an image using Digikam's Image editor (and saving it as a new version, at least), adds the XMP Video Date field, copying the date from the XMP Creation date. But it depends on the existing metadata, as it not happens in all cases. Check this screen capture: https://i.imgur.com/A2Zu7Wv.gifv I am pretty sure there are other cases where digikam adds the XMP Video Date, but this is the only one I've been able to identify. STEPS TO REPRODUCE 1. Check image in the metadata editor to make sure that the XMP Video date is empty. 2. Use the image editor, and save the image as a new version. 3. Check the metadata of that new image, and observe how the XMP Video date is no longer empty. OBSERVED RESULT Digikam has added a date in the XMP Video Date field. EXPECTED RESULT Metadata should be identical to that of the source picture. SOFTWARE/OS VERSIONS Ubuntu 18.04 with gnome and digikam-6.2.0-git-20190423T140539-qtwebkit-x86-64.appimage
*** This bug has been marked as a duplicate of bug 407034 ***
Hi, This problem still reproducible using last Linux AppImage bundle 6.2.0 pre release available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
Git commit 10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead by Gilles Caulier. Committed on 09/05/2021 at 03:55. Pushed by cgilles into branch 'master'. Do not add Xmp video date-time stamp tags on non video files Related: bug 407034 FIXED-IN: 7.3.0 M +12 -4 core/libs/metadataengine/engine/metaengine_item.cpp M +1 -0 core/libs/metadataengine/engine/metaengine_p.h https://invent.kde.org/graphics/digikam/commit/10cdfe4a5aedb3c38303fba8d3d8f1e72d6e2ead