Bug 261871

Summary: Digikam import of Nikon D7000 images very slow
Product: [Applications] digikam Reporter: Bernie <meensb>
Component: Import-Gphoto2Assignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version: 1.7.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 2.1.0

Description Bernie 2011-01-02 15:41:47 UTC 
Version:           1.7.0 (using KDE 4.5.4) 
OS:                Linux

Using digikam for Nikon D200 and new D7000, both jpg and NEF. Importing D200 images (both via card reader as well as direct connect) works fine. Importing D7000 images (both via card reader as well as direct connect) goes painfully slow. It takes a lot of time for the import module to show the thumbnails and even more time to actually import (much slower than USB 1.0 speeds). Workaround, copying the images via the dolphin file manager from the sd card directly into the desired folder, works fine, so no USB transfer speed issue here. Also, importing images from a panasonic lumix SD card works fine.

Reproducible: Always

Steps to Reproduce:
Connect D7000 or insert SD card in card reader, choose " download images with digikam" when notification shows up in task bar device manager. Digikam starts with import module and behaviour shows up.

Actual Results:  
Very slow transfer

Expected Results:  
Swift transfer according to USB speed

I'll upload some images to test yourself. Put them on a SD card and try..
Comment 1 Bernie 2011-01-02 15:58:12 UTC 
Cannot attach images due to size too large. Please use:

http://www.xs4all.nl/~meensb/BMS_0848.JPG
http://www.xs4all.nl/~meensb/BMS_1104.JPG
Comment 2 caulier.gilles 2011-08-04 14:35:01 UTC 
The camera connection time is depending of thumbs generation with older versions.

With next digiKam 2.1.0, thumbs are generated on the fly. Problem must be fixed...

Can you test with code from git master and report ?

Gilles Caulier
Comment 3 caulier.gilles 2011-08-09 09:24:36 UTC 
For me this file is fixed now (future digiKam 2.1.0). Please re-open if
necessary...

Gilles Caulier