| Summary: | Import from MTP or PTP based cameras is very slow | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Philippe ROUBACH <philippe.roubach> |
| Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.4.0 | |
|
Description
Philippe ROUBACH
2014-01-17 10:17:17 UTC
Huge improvements have been done in import tool with-beta release few days ago. Please take a look Gilles Caulier digikam 4.0.0 beta 4 kde 4.12.4 pb still there . i discover this with kde 4.12.4 : in dolphin we access to the smartphone via "mtp:<name of the smartphone>" mtp displays 2 devices : "card" and "phone" mtp lets the user running very fast across the 2 trees there is 2 difficulties : - the user must know where are the photos and videos taken with smartphone camera . in case of android he must know photos and videos are in "DCIM" folder in the "phone" or in "card" if user chooses in "photo" app to store them in "card" . - there is no preview . i think it is an interesting alternative way to procede if the 2 difficulties are solved opensuse x86_64 13.1 kde 4.13.1 digikam 4.0.0 no progress for mtp and ptp it is very slow my solution today (no more cable) : android 4.2.2 + primitiveftpd (ftp server to share internal and external storage) my smartphone and my pc connected with wifi to the same network the sole pb with this solution is that "import from a remote computer" is less feature rich that "import from a camera" Philippe, This file still valid using last digiKam 4.2.0 ? Gilles Caulier Philippe, This file still valid using last digiKam 4.9.0 ? Gilles Caulier New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier Philippe, digiKam 5.0.0 is released. Problem still valid with this release ? Gilles Caulier We need feedback with last digiKam AppImage Linux Bundle: https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release ? It available at this url : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier with 5.4 it is no more slow but it remains a problem: why listing all folders instead of the one whom digikam is aware : DCIM/camera or better the tree DCIM because under DCIM many different folders are created by camera apps as "100ANDRO", "Camera", "OpenCamera" etc. because DCIM is the standard root dir. Sub directories can be different for some device. Starting to scan from DCIM will work on all cases. Of course a future work to customize this patch for each camera set in digiKam can be a solution. See bug #168253. This is another point to talk in #168253 Gilles Caulier i didn't well explain about MTP 1. digikam display many many folders apart Camera folder. read again description of the report i know it's not digikam but the MTP protocol. only Camera folder is useful for digikam. it would be better if digikam filters result of MTP and retains only Camera Camera is drowned among many folders. 2. digikam(?) displays "Camera" folder it would be better to display "DCIM" because "Camera" is a not a standard folder to store photos by camera apps there is no standard folder in android to store photos by camera apps with android some app store by default photos in DCIM/100ANDRO/ some app store by default photos in DCIM/Camera/ some app store by default photos in DCIM/OpenCamera/ etc. |