[digikam] [Bug 374004] New: Different Images recognised as identical images

[bugzilla_noreply]

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

            Bug ID: 374004
           Summary: Different Images recognised as identical images
           Product: digikam
           Version: 5.3.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Metadata
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

Created attachment 102923
  --> https://bugs.kde.org/attachment.cgi?id=102923&action=edit
Zip with the 3 images of the camera.

Different images are treated as identical images by digikam.

I've copied 3 images from my smartphone camera with a file browser into an
album.
I start digikam and browser to this album and wait until these pictures are
detected.
In the side-pane in Versions/Versions with the display option "Show available
versions and the applied filters in a combined list." for each picture only the
current image is shown below "Image History". Everything fine so far.
Now I select each picture (individual or together doesn't matter) a give these
one star.
When I now select one picture the other two images are shown in the section
"Identical Images" in the right side-pane. But the content of the pictures is
different.
I wouldn't expect that different images are shown as identical.

Besides that the pictures are shown as identical (I wouldn't bother too much),
within my album some as wrongly identical detected images are NOT shown in the
album view anymore (although they can be seen in the file browser).
Unfortunately I can't reproduce how this happened but this is very annoying.

The pictures are taken by a Samsung Galaxy S4.
The Exif-Information contains for each picture the same
Exif.Photo.ImageUniqueID of S13F0LAHA01.
In the database all 3 pictures have the same uuid S13F0LAHA01 in the table
ImageHistory.

Is the same ImageUniqueID given by the camera the root cause?
Do I have to manipulate the ImageUniqueID by my self before using digikam or
can digikam take care of this maybe not ideal behaviour of the smartphone?

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

[bugzilla_noreply]

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

[hidden email] changed:

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

--- Comment #1 from [hidden email] ---
yes, exactly. Exif.Photo.ImageUniqueID is used to register image to database.

Code relevant :

metadata parser :
https://cgit.kde.org/digikam.git/tree/libs/dmetadata/dmetadata.cpp#n981

used to register image in DB while scanning :
https://cgit.kde.org/digikam.git/tree/libs/database/item/imagescanner.cpp#n984

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=374004

--- Comment #2 from Blomi <[hidden email]> ---
So somehow like the detection of the click counter in
https://cgit.kde.org/digikam.git/tree/libs/dmetadata/dmetadata.cpp#n989
via exifUid.startsWith(QLatin1String("00000000000000000000"))
a detection of not unique IDs is necessary.

But this will be difficult: How to determinate if the IDs are the same because
of a stupid camera implementation or the IDs are intentionally the same because
it's an modified version of the same picture.

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

[bugzilla_noreply]

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

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.5.0
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
      Latest Commit|                            |https://commits.kde.org/dig
                   |                            |ikam/c142f6b5c2a491db75253f
                   |                            |75c331bdc2c4d48c0f
         Resolution|---                         |FIXED

--- Comment #3 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.

[bugzilla_noreply]

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

--- Comment #4 from Maik Qualmann <[hidden email]> ---
Note: this only fixed for new added images. See Bug 375483

Maik

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