reduced size raw import

[Johannes Wienke-3]

Hey,

after some time I updated to current stable trunk and wonder what
happened to the raw import feature that the preview was generated on a
smaller version of the raw file. Right now all processing is done on the
full image size. Was it planned to remove this?

Regards,
Johannes


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> after some time I updated to current stable trunk and wonder what
> happened to the raw import feature that the preview was generated on a
> smaller version of the raw file. Right now all processing is done on the
> full image size. Was it planned to remove this?

As I understood it, the main point was to have an option list of demosaicing
methods: If only the half-size preview is loaded, which is not demosaiced, no
difference between demosaicing choices methods can be seen in the RAW import
tool.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Right. processing half size raw do not take a care about all
demosaiced options, which is weird to take the right settings.

The advantage to process full image in raw import is that when you
press Import the image is imediatly loaded in editor.

I recommend to compile libkdcraw with OpenMP (libgomp) and to remove
all debug info (typically using KDE FINAL)

RAW demosaicing time will be reduced drastically

Gilles Caulier

2011/2/19 Marcel Wiesweg <[hidden email]>:

>
>> after some time I updated to current stable trunk and wonder what
>> happened to the raw import feature that the preview was generated on a
>> smaller version of the raw file. Right now all processing is done on the
>> full image size. Was it planned to remove this?
>
> As I understood it, the main point was to have an option list of demosaicing
> methods: If only the half-size preview is loaded, which is not demosaiced, no
> difference between demosaicing choices methods can be seen in the RAW import
> tool.
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> I recommend to compile libkdcraw with OpenMP (libgomp) and to remove
> all debug info (typically using KDE FINAL)
>
> RAW demosaicing time will be reduced drastically

By about 50% on a dual core processor? ;-)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

ARW file, A500 camera, full debug, no OpenMP : 16s

final, OpenMP : 4s

Demosaicing : AMaZE

Not all demosaicing methods use OPenMP yet...

Gilles

2011/2/19 Marcel Wiesweg <[hidden email]>:

>
>> I recommend to compile libkdcraw with OpenMP (libgomp) and to remove
>> all debug info (typically using KDE FINAL)
>>
>> RAW demosaicing time will be reduced drastically
>
> By about 50% on a dual core processor? ;-)
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel