Bug 494640

Summary: DNG conversion from CR2
Product: [Applications] digikam Reporter: Bertil Rolf <b.g.rolf>
Component: Plugin-Bqm-DngConverterAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.5.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: attachment-3917122-0.html

Description Bertil Rolf 2024-10-13 08:06:04 UTC
Hello!
I shoot many photos with Canon Powershot G9X mk II. They come out as CR2. I need to convert them into DNG before I import them into Lightroom.

I tried DigiKam for this, using Batch Queue. But DK bends straight lines when converting from CR2 to DNG. See the zipfile at:

https://drive.google.com/file/d/1EpCwwq_h9cpzRnOIufeE3zD1L5ydHyu8/view?usp=drive_link
...
Best regards
Bertil Rolf
Baden bei Wien
Comment 1 caulier.gilles 2024-10-13 08:08:04 UTC
Which digiKam version did you use ?
Comment 2 Bertil Rolf 2024-10-13 08:11:37 UTC
Created attachment 174763 [details]
attachment-3917122-0.html

8.5.0


Build date: 2024-08-29 16:21 (target: RelWithDebInfo)
Revision: 7141aca20964a7f17ef5e678c785c83056e51c57 
<https://invent.kde.org/graphics/digikam/commit/7141aca20964a7f17ef5e678c785c83056e51c57>


BR


On 2024-10-13 10:08, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> caulier.gilles@gmail.com changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |caulier.gilles@gmail.com
>            Component|BatchQueueManager-Core      |Plugin-Bqm-DngConverter
>
> --- Comment #1 fromcaulier.gilles@gmail.com ---
> Which digiKam version did you use ?
>
Comment 3 caulier.gilles 2024-10-13 08:17:26 UTC
can you share in the cloud a CR2 file sample to test ?
Comment 4 Bertil Rolf 2024-10-13 08:20:10 UTC
In the description of the bug, you'll find the link to a zipfile on my 
account on Google Drive.


On 2024-10-13 10:17, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> --- Comment #3 from caulier.gilles@gmail.com ---
> can you share in the cloud a CR2 file sample to test ?
>
Comment 5 Maik Qualmann 2024-10-13 08:22:54 UTC
So digiKam doesn't bend lines. Your RAW image from the camera is actually bent like that.

digiKam just doesn't apply any lens correction to create the preview image for the DNG.

Maik
Comment 6 Maik Qualmann 2024-10-13 08:36:21 UTC
The image is automatically recognized by our lens correction. But it is not corrected correctly at the determined focal length of 10.2 mm. Only at around 1.0 mm do we have a roughly corrected image. Either there is an error in the lensfun database or we are overlooking something with fixed lenses when transferring the focal length.

The question is whether we want to use lens correction at all when converting to DNG and do other (commercial) converters do it?

Maik
Comment 7 Maik Qualmann 2024-10-13 09:01:52 UTC
Git commit 43fb998e4dc9ed29829943f900191e195d6a77bf by Maik Qualmann.
Committed on 13/10/2024 at 09:00.
Pushed by mqualmann into branch 'master'.

fixed focal length only for a specific Sony camera model

M  +5    -2    core/libs/dimg/filters/lens/lensfunfilter.cpp

https://invent.kde.org/graphics/digikam/-/commit/43fb998e4dc9ed29829943f900191e195d6a77bf
Comment 8 caulier.gilles 2025-04-11 18:13:59 UTC
Hi,

The 8.7.0 pre-release Windows installer from today have been rebuilt from
scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5, ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif, heif, aom, etc.).

Please try with this version to see if your problem still reproducible...

https://files.kde.org/digikam/

Thanks in advance
Best regards

Gilles Caulier
Comment 9 Bertil Rolf 2025-04-12 08:57:42 UTC
Hello,

Will try out this in a couple of days.

Btw, like 8.6.0. a lot!

Best

Bertil Rolf

On 2025-04-11 20:13, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> --- Comment #8 from caulier.gilles@gmail.com ---
> Hi,
>
> The 8.7.0 pre-release Windows installer from today have been rebuilt from
> scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5,
> ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif,
> heif, aom, etc.).
>
> Please try with this version to see if your problem still reproducible...
>
> https://files.kde.org/digikam/
>
> Thanks in advance
> Best regards
>
> Gilles Caulier
>
Comment 10 caulier.gilles 2025-04-12 13:47:46 UTC
Thanks you. For info the Libraw processor used in parallel than DNG SDK is always updated between digiKam versions (libraw code is included in digiKam as well)...

https://www.libraw.org/

This is why i ask regularly in digiKam Bugzilla if the dysfunctions are reproducible...

Best

Gilles Caulier
Comment 11 Bertil Rolf 2025-05-02 10:08:26 UTC
Hello!

I now have tried out DNG-conversion from CR2 to DNG, using DigiKam 
8.7.0. on Windows 11 and using Adobe DNG Converter for comparison.

Photos and comments enclosed here:

https://drive.google.com/file/d/104Pwydzq4P6dPPyZypsMgltq629PnXZc/view?usp=drive_link

Best regards and Good luck!

Bertil Rolf

Baden bei Wien

On 2025-04-11 20:13, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> --- Comment #8 from caulier.gilles@gmail.com ---
> Hi,
>
> The 8.7.0 pre-release Windows installer from today have been rebuilt from
> scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5,
> ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif,
> heif, aom, etc.).
>
> Please try with this version to see if your problem still reproducible...
>
> https://files.kde.org/digikam/
>
> Thanks in advance
> Best regards
>
> Gilles Caulier
>
Comment 12 caulier.gilles 2025-05-12 06:13:17 UTC
I take a look to your comparison images generated from CR2 to Adobe and digiKam tool. results are not the same of course, but the result are near and not too bad after all.

Did you take a care to render the DNG preview with digiKam using the RAW data (or Embeded JPEG) for both to compare. Data to compare must be the same type.

Best

Gilles Caulier
Comment 13 Bertil Rolf 2025-05-16 11:20:07 UTC
Hello,

You are right, the image quality of Adobe Converter and DigiKam is 
roughly equivalent. I fed the same CR2 files into both apps without much 
thought.

Except for file size, there is a very significant different for the 
user, namely processing time.

The latest version of Adobe C is very fast while DigiKam 870 on my PC 
(HP Z240, 32 GB) was intolerably slow for my workflow.

Sure, it all comes down to which workflow you are comfortable with. In 
Adobe, I would convert all raw photos into DNG with AC and cull them 
afterwards in LR. I guess that in DK, I would need to cull them before 
feeding them to conversion. I have not tried this option, however.

Best regards

Bertil Rolf


On 2025-05-12 08:13, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> --- Comment #12 from caulier.gilles@gmail.com ---
> I take a look to your comparison images generated from CR2 to Adobe and digiKam
> tool. results are not the same of course, but the result are near and not too
> bad after all.
>
> Did you take a care to render the DNG preview with digiKam using the RAW data
> (or Embeded JPEG) for both to compare. Data to compare must be the same type.
>
> Best
>
> Gilles Caulier
>
Comment 14 caulier.gilles 2025-05-16 11:55:19 UTC
Well about the speed, i would expect a multicore/multithread options/functions in the Adobe DNG SDK that digiKa uses, but no chance, there is nothing like this. So the conversion processing done by digiKam will run on a single thread/single core.

Did you see a multi-core usage with Adobe RAW converter while converting CR2 to DNG ?

Tip: The DNG Convert in digiKam is also available in BQM. So, if you have enough RAM and Multicore, you can convert more than one file at the same time.

Gilles Caulier
Comment 15 Bertil Rolf 2025-05-20 14:14:09 UTC
About the speed of Adobe conversion, I can only say it is impressive, 
not how it is attained.

Thanks for the hint about BQM.

For an advanced amateur like me, the greatest advantage DigiKam has over 
Lightroom are the DAM features. I use them for selecting photos for 
slide shows on the fly and play them to my public. This is the main way 
we look at old photos and DigiKam runs from thin clients I have 
repurposed for media playing.

Although facetagging and geotagging in DigiKam are very fine, I have not 
found any way to make use of the results in the slide shows.

Best regards

Bertil Rolf

Baden bei Wien





On 2025-05-16 13:55, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=494640
>
> --- Comment #14 from caulier.gilles@gmail.com ---
> Well about the speed, i would expect a multicore/multithread options/functions
> in the Adobe DNG SDK that digiKa uses, but no chance, there is nothing like
> this. So the conversion processing done by digiKam will run on a single
> thread/single core.
>
> Did you see a multi-core usage with Adobe RAW converter while converting CR2 to
> DNG ?
>
> Tip: The DNG Convert in digiKam is also available in BQM. So, if you have
> enough RAM and Multicore, you can convert more than one file at the same time.
>
> Gilles Caulier
>
Comment 16 caulier.gilles 2025-06-07 10:42:26 UTC
Hi Rolf,

About the speed, it's clear. There is nothing to improve in digiKam as we are relevant to the open source DNG SDK which is not all the code of the Adobe DNG Converter, only the backend to process files.

We are also dependent on the libraw library used in digiKam to extract non demosaiced RAW data and pass it to the DNG converter. Here also, no improvements can be done about the speed as extraction is streamlined with the RAW file. No preprocessing is done in libraw where we can expect to parallelize something.

About the quality and the rendering of the DNG conversion, we apply the best metadata backport and adjustments that we know to pass to the DNG SDK. You must know that even if the DNG SDK is an open source component, there is no doc and examples available. It's difficult to use and tune. Also, at each DNG SDK version the API changes and the SDK calls must be adjusted, without any help from the Adobe team.

So for me, the best thing to do is already here in digiKam. Do not expect serious improvements in the future...

Best regards

Gilles Caulier