Bug 195538

Summary: use more than one thread for batch conversion of RAW images
Product: [Applications] digikam Reporter: S. Burmeister <sven.burmeister>
Component: BatchQueueManager-RAWProcessingAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: caulier.gilles
Priority: NOR    
Version First Reported In: 1.0.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.3.0
Sentry Crash Report:

Description S. Burmeister 2009-06-07 11:07:35 UTC 
Version:           0.10 (using KDE 4.2.4)
OS:                Linux
Installed from:    SuSE RPMs

If I use Batch > Batch Raw converter to e.g. convert 50 images on a dual core, digikam only uses one core and processes one picture after the other instead of working on two or more at a time. The conversion of the batch would be a lot faster if it would use all available cores.

If there are concernes that this would slow down everything else, it could be used with "nice" or at least made optional, i.e. offer a checkbox in the batch conversion dialogue to enable/disable it.
Comment 1 caulier.gilles 2009-06-07 11:22:03 UTC 
sven,

I will not touch Raw converter kipi-plugins in this way...

But digiKam has now Batch Queue Manager where RAW can be converted and more of course :

http://www.digikam.org/node/427

In this tool, build into digiKam core (it's not a plugin), i plan to use OpenMp library (or another technic) to parallelize queue execution. 

Gilles Caulier
Comment 2 S. Burmeister 2009-12-29 11:44:56 UTC 
Same for the BQM, only one picture is processed at a time.
Comment 3 caulier.gilles 2010-10-13 09:15:26 UTC 

*** This bug has been marked as a duplicate of bug 254033 ***
Comment 4 caulier.gilles 2019-08-09 11:05:52 UTC 
Fixed with bug #254033