[digikam] [Bug 375483] New: Wrong history on images taken with Samsung S3

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

            Bug ID: 375483
           Summary: Wrong history on images taken with Samsung S3
           Product: digikam
           Version: 5.5.0
          Platform: Appimage
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Versioning
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

Created attachment 103611
  --> https://bugs.kde.org/attachment.cgi?id=103611&action=edit
Wrong history of Samsung images

It seems an old problem is back (see
https://bugs.kde.org/show_bug.cgi?id=323210 ), at least very similar.
I noticed that a lot of images I downloaded from a Samsung S3 smartphone have a
history showing "Derived Images And Identical Images That Are Neither Derived
Nor Identical". See attachment!
It seems that all these images in the history are edited by digiKam, at least
the metadata. If I go to one of these images it also shows this screwed up
history. All the false derived or identical images are from the same Samsung S3
as far as I could find out up to now.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Maik Qualmann <[hidden email]> ---
Probably like my Samsung S4 the S3 has an always same Exif.Photo.ImageUniqueID
for all images. That's really bad. Can you check whether the S3 images has the
same ImageUniqueID in the EXIF?

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #2 from Maik Qualmann <[hidden email]> ---
The Exif.Photo.ImageUniqueID only changes here if a new firmware version
installed.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from [hidden email] ---
A solution : while importing, recompute UUID and patch Exif/XMP tags. Like this
database and versioning properties will not be a mess.

This will not solve the problem of collection of image not processed by import
tool. At least it's better than nothing.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #4 from Maik Qualmann <[hidden email]> ---
We could also put Samsung on a blacklist and ignore Exif.Photo.ImageUniqueID.
Xmp.digiKam.ImageUniqueID is read first and would not be affected.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #5 from Maik Qualmann <[hidden email]> ---
Created attachment 103626
  --> https://bugs.kde.org/attachment.cgi?id=103626&action=edit
uniqueID.patch

Wolfgang can you test this patch? Re-reading the metadata should solve the
problem.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Wrong history on images     |Wrong history on images
                   |taken with Samsung S3       |taken with Samsung S3
                   |                            |[patch]

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #6 from [hidden email] ---
Maik to comment #4 :

yes, so far, a better solution at all. Why i don't think about it before
(:=)))...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #7 from Wolfgang Scheffner <[hidden email]> ---
(In reply to Maik Qualmann from comment #5)
> Created attachment 103626 [details]
> uniqueID.patch
>
> Wolfgang can you test this patch? Re-reading the metadata should solve the
> problem.
>
> Maik

Maik, Reread Metdata from Image in the Item menu on pics that are already
imported does  n o t  solve the problem. Only if I import the pics again the
wrong history is gone, but only with "Use file metadata" un-checked.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=375483

--- Comment #8 from Maik Qualmann <[hidden email]> ---
Git commit c142f6b5c2a491db75253f75c331bdc2c4d48c0f by Maik Qualmann.
Committed on 26/01/2017 at 11:37.
Pushed by mqualmann into branch 'master'.

blacklist Samsung cameras for Exif.Photo.ImageUniqueID

M  +2    -1    libs/dmetadata/dmetadata.cpp

https://commits.kde.org/digikam/c142f6b5c2a491db75253f75c331bdc2c4d48c0f

--
You are receiving this mail because:
You are the assignee for the bug.