SUMMARY *** Hello! As explained in detail in this new tutorial: https://userbase.kde.org/Digikam/Tutorials/Tagging_and_Face_Tags#Rotating_face_tags there is a well known issue that Windows Photo Gallery sometimes produces wrong face tags that need to be rotated relative to the image. With a fairly trivial new function digiKam could have an excellent fix for this common problem: *** Suggestion for a new "Rotate Face Tags Left" function: 1. Execute the code from the standard image rotation function which rotates Face Tags (to the Left), but do NOT perform actual image data rotation. 2. Make sure that “Exif orientation tag” is set to “Normal” (in case it was not correct previously). Result - correctly oriented Face Tags both in digiKam and in any Microsoft program that caused the issue. For the the user interface: 1. adding a possibility to map a Keyboard shortcut is important. 2. the function can be under menu "Item" ==> "Rotate Face Tags" ==> "Left" / "Right". Thank you!
We can certainly add this feature. But that would still mean having to manually sift through a lot of images and rotate the faces. I would be more interested in an automatic solution. We just need to find a way to recognize that the faces have been edited with Windows Photo Editor. Maybe there is something in common in the metadata. Maybe a few samples from Windows Photo Editor would help us. Maik
Thanks for the suggestion Maik, I thought about it and experimented some more until I arrived to conclusion that a fully automatic solution is not worth it - basically using digiKam's advanced search together with the simple "Rotate Face Tags" function would be fast enough that I would not bother testing and risking potential damage any fully automatic script can cause. I described the desired workflow in detail here: https://userbase.kde.org/Digikam/Tutorials/Switch_from_Microsoft_OneDrive_or_WLPG_to_digiKam#Semi-automated_approach The main point is - simple "Rotate Face Tags" function would be my preferred tool both for single file corrections and for fixing whole collection at once. PS, I would be happy if some digiKam experts look through the tutorials I wrote over the holidays (2 new and 1 revised). If you see any mistakes or can suggest a better approach. I keep on polishing them as I find mistakes and new tricks, but I am sure there is more to be done. I would like to eventually make them into video tutorials, but only when I am more confident that the tutorials are good. Thank you for all your work!
Happy New Year :) Would be great if this "Rotate tags, but not picture" button could be added for all the ex-Windows Photo Gallery users :)
Git commit 862032217ac8af283db5cae4e0f7f7c2b0a1adbf by Maik Qualmann. Committed on 10/09/2023 at 17:54. Pushed by mqualmann into branch 'master'. add Microsoft Photo Editor detection for face region rotation Related: bug 474357 FIXED-IN: 8.2.0 M +1 -1 NEWS M +19 -2 core/libs/database/item/scanner/itemscanner_photo.cpp https://invent.kde.org/graphics/digikam/-/commit/862032217ac8af283db5cae4e0f7f7c2b0a1adbf
After using Windows Photo Gallery for so many years I had to deal with this issue by rotating and correcting all the problematic images. What will this this code change do? Automatically correct/transpose the XMP? Also, the creator tool xmp entry with the problems may read: "Microsoft Windows Live Photo Gallery xxxx" (pre-2012), "Microsoft Photo Gallery xxxx" where xxxx is the version number, not just "Microsoft Photos" There may be applications which may have already adjusted the MS Photo Gallery XMP Region Tags, so it would be best to provide a manual option just in case and not just "assume" the MS Photo Gallery XMP Region Tags are incorrect to begin with.
Git commit 3937123d76f2c1cc1b5aea0f3ab477a77355266e by Maik Qualmann. Committed on 11/09/2023 at 07:43. Pushed by mqualmann into branch 'master'. revert Microsoft Photo Editor detection for face region rotation Related: bug 474357 M +2 -3 NEWS M +2 -19 core/libs/database/item/scanner/itemscanner_photo.cpp https://invent.kde.org/graphics/digikam/-/commit/3937123d76f2c1cc1b5aea0f3ab477a77355266e