[Bug 305655] New: Detect which pictures are actually new in the camera

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] New: Detect which pictures are actually new in the camera

Tomáš Pártl
https://bugs.kde.org/show_bug.cgi?id=305655

            Bug ID: 305655
          Severity: wishlist
           Version: 2.5.0
          Priority: NOR
          Assignee: [hidden email]
           Summary: Detect which pictures are actually new in the camera
    Classification: Unclassified
                OS: Linux
          Reporter: [hidden email]
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: Import
           Product: digikam

This is the problem:
I installed digiKam, showed it where I keep my pictures and it recognized the
subdirectories as albums (nice). Then I connected my camera (actually a mobile
phone) to the computer and wanted to import new photos from it. BUT DigiKam
insisted that all photos in the camera are new, even though a lot of them were
in the albums already.
I tried to find a way to make digiKam compare the photos in the camera to the
ones in the albums (at least by file name) and mark as new only those that
weren't in the albums already, but I found no way to do it and ended up writing
a shell script to copy the photos in the computer instead.

So: It would be great if digiKam could check if the photos in a connected
camera are actually in the albums already and only mark as new those that
aren't. It could compare the photos using file names only or it could consider
also files size and maybe even a file checksum.

Thank you for considering this request!

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] Detect which pictures are actually new in the camera

Gilles Caulier-4
https://bugs.kde.org/show_bug.cgi?id=305655

Gilles Caulier <[hidden email]> changed:

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

--- Comment #1 from Gilles Caulier <[hidden email]> ---
This is already implemented and work fine with USB Mass Storage camera.

With GPhoto2 device, a problem have been reported here...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] Detect which pictures are actually new in the camera

Gilles Caulier-4
In reply to this post by Tomáš Pártl
https://bugs.kde.org/show_bug.cgi?id=305655

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Gilles Caulier <[hidden email]> ---
See these entries :

#285683
#281758

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] Detect which pictures are actually new in the camera

Tomáš Pártl
In reply to this post by Tomáš Pártl
https://bugs.kde.org/show_bug.cgi?id=305655

--- Comment #3 from Tomáš Pártl <[hidden email]> ---
Hello!
Thank you for the fast reply!
I compiled digiKam 2.8 and the problem persists: all pictures on the phone
camera
are always marked as new.

I read the two bug entries you refer to but to no avail.
I am using a Samsung Android phone connected as a mass storage device.
I can import from it either via Import->Cameras or via Import->USB Storage
Devices
but the result is always the same: all images erroneously marked as new.

Any suggestions, please?

Thank you!

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] Detect which pictures are actually new in the camera

Andrew Goodbody
In reply to this post by Tomáš Pártl
https://bugs.kde.org/show_bug.cgi?id=305655

Andrew Goodbody <[hidden email]> changed:

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

--- Comment #4 from Andrew Goodbody <[hidden email]> ---
I think there is a misunderstanding here. Digikam will record which photos it
has already downloaded from a camera. Digikam will not recognise photos as
already downloaded if that was done not using digikam, as in your case. So
digikam is working as expected here but not as you would like it to. So if you
allow digikam to download all photos, you can delete the duplicates that were
already downloaded. From then on digikam will recognise your new photos.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 305655] Detect which pictures are actually new in the camera

Tomáš Pártl
In reply to this post by Tomáš Pártl
https://bugs.kde.org/show_bug.cgi?id=305655

--- Comment #5 from Tomáš Pártl <[hidden email]> ---
Yes, you nailed it down. Still, it would be useful to me if digikam could
recognize even photos downloaded into its album directory in a different way
than using digikam as not new.
So this is not a bug report, but a feature request :)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel