dynamic range problem

[mfi]

Hello,

I am new to digicam so maybe solution for this is simple, but I couldn't
find it in mailing list archives. When I edit PEF files (Pentax k20d)
highlights are very clipped compared to other tools. Areas that have
very visible details in other programs, and are far away from being
overexposed in digiKam are white. What is strange, when I click on a
thumbnail to get image preview in main digiKam window (as opposite to
edit window) everything is fine, and bright areas have all details. This
can't be corrected by decreasing brightness/lowering exposition - image
gets darker but there's no more details in bright areas.

Example of this can be found here:

http://www.fotopolska.info/example/example.jpg


thanks for any suggestions.
Michael
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Dnia Sunday 05 of October 2008, mfi napisał:

> Hello,
>
> I am new to digicam so maybe solution for this is simple, but I couldn't
> find it in mailing list archives. When I edit PEF files (Pentax k20d)
> highlights are very clipped compared to other tools. Areas that have
> very visible details in other programs, and are far away from being
> overexposed in digiKam are white. What is strange, when I click on a
> thumbnail to get image preview in main digiKam window (as opposite to
> edit window) everything is fine, and bright areas have all details. This
> can't be corrected by decreasing brightness/lowering exposition - image
> gets darker but there's no more details in bright areas.
>
> Example of this can be found here:
>
> http://www.fotopolska.info/example/example.jpg

Can you post somewhere RAW file?

m.

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

Dnia Sunday 05 of October 2008, mfi napisał:

> Hello,
>
> I am new to digicam so maybe solution for this is simple, but I couldn't
> find it in mailing list archives. When I edit PEF files (Pentax k20d)
> highlights are very clipped compared to other tools. Areas that have
> very visible details in other programs, and are far away from being
> overexposed in digiKam are white. What is strange, when I click on a
> thumbnail to get image preview in main digiKam window (as opposite to
> edit window) everything is fine, and bright areas have all details. This
> can't be corrected by decreasing brightness/lowering exposition - image
> gets darker but there's no more details in bright areas.
>
> Example of this can be found here:
>
> http://www.fotopolska.info/example/example.jpg

Apart from making PEF file available try to change Highlights to Unclip
in Raw Decoding. To restore luminosity add exposure or play with
luminosity curve.

m.

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

[Gilles Caulier-4]

2008/10/5 Mikolaj Machowski <[hidden email]>

Dnia Sunday 05 of October 2008, mfi napisał:

> Hello,
>
> I am new to digicam so maybe solution for this is simple, but I couldn't
> find it in mailing list archives. When I edit PEF files (Pentax k20d)
> highlights are very clipped compared to other tools. Areas that have
> very visible details in other programs, and are far away from being
> overexposed in digiKam are white. What is strange, when I click on a
> thumbnail to get image preview in main digiKam window (as opposite to
> edit window) everything is fine, and bright areas have all details. This
> can't be corrected by decreasing brightness/lowering exposition - image
> gets darker but there's no more details in bright areas.
>
> Example of this can be found here:
>
> http://www.fotopolska.info/example/example.jpg

Can you post somewhere RAW file?

Agree, whitout a good sample to test, we cannot guide you...

Gilles Caulier

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

[mfi]

Mikolaj Machowski pisze:

> Dnia Sunday 05 of October 2008, mfi napisał:
>  
>> Hello,
>>
>> I am new to digicam so maybe solution for this is simple, but I couldn't
>> find it in mailing list archives. When I edit PEF files (Pentax k20d)
>> highlights are very clipped compared to other tools. Areas that have
>> very visible details in other programs, and are far away from being
>> overexposed in digiKam are white. What is strange, when I click on a
>> thumbnail to get image preview in main digiKam window (as opposite to
>> edit window) everything is fine, and bright areas have all details. This
>> can't be corrected by decreasing brightness/lowering exposition - image
>> gets darker but there's no more details in bright areas.
>>
>> Example of this can be found here:
>>
>> http://www.fotopolska.info/example/example.jpg
>>    
>
> Apart from making PEF file available try to change Highlights to Unclip
> in Raw Decoding. To restore luminosity add exposure or play with
> luminosity curve.
>
> m.
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>  

Hello,

I changed Highlights to Unclip in Raw Decoding (I even restart digiKam to check if new setting was saved, and it was) - and there is no effect at all. Edited image looks exactly the same as before.

Here is PEF file:
http://www.fotopolska.info/example/

regards,
Michael


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

[Gilles Caulier-4]

Michael,

I cannot reproduce the problem here.

I have tested to import your RAW file using digiKam for KDE4 (0.10.0-beta4) or digiKam for KDE3 (0.9.5-svn) using new RAWImport tool for image editor, and all work fine with highlight recovery settings.

For RAW file decoding, i use libkdcraw based on LibRaw (http://www.libraw.org). LibRaw currently use the last dcraw code for demosaicing. Now look my screenshots:

* This the preview of raw import tool with RAW demosaicing settings. Postprocessing use default settings (no gamma/curve/exposure adjustment) . Of course like it's a preview with a divided by 4 image size, huge zooming give artifact. But it's enough to set demosaicing configuration. Also, working on a reduced raw decoded image speedup computation. Note that i use 16 bits color depth, not 8 (it's a non sence to use 8 bits color depth with RAW)

http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

And now, the best: the full raw image in editor. Look like the color (white balance) is better than RAW studio !

http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-editor.png

For me, it's a good example how to use properly RAW files in digiKam.

Note : the preview from digiKam  icon view is rendered using JPEG preview image from RAW file. It's not RAW image data decoded. In fact the preview  JPEG  is adjusted using camera  firmware. It's still JPEG : only 8 bits color depth ! this is why highlight are broken, and it's a good example to explain why RAW is always better than JPEG.

Unforget : jpeg is fine to take shot and publish as well the image on the web (fats workflow). Never use JPEG if you want to retouch photo, especially color settings ! This file format is not adapted and use lossy compression algorithm.

Best

Gilles Caulier

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

Dnia Monday 06 of October 2008, Gilles Caulier napisał:
> Michael,
>
> I cannot reproduce the problem here.

Uh, uh. Situation isn't so good. You didn't use default settings. And
with few weeks older digiKam 0.9.5svn (kdcraw still as separate binary)
with defaults I got only slightly better results than Michael.

Looking into screenshots I *was* able to reproduce your outcome but this
requires good knowledge of RAW processing and digiKam itself.

m.

ps. couldn't test 0.10 because it crashes when trying to open RAW file
    in rawimport.

ps2. I got best results with rawtherapee 2.4 M1 (almost defaults),
    second is digiKam but requires much fiddling with sliders.

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

Dnia Monday 06 of October 2008, Mikolaj Machowski napisał:
> ps2. I got best results with rawtherapee 2.4 M1 (almost defaults),
>     second is digiKam but requires much fiddling with sliders.

Forgot:

http://www.witkacy.hg.pl/var/andrt.png

m.

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

Dnia Monday 06 of October 2008, Mikolaj Machowski napisał:
>
> ps. couldn't test 0.10 because it crashes when trying to open RAW file
>     in rawimport.


Application: digiKam (digikam), signal SIGSEGV
[?1034hUsing host libthread_db library "/lib/i686/libthread_db.so.1".
[New Thread -1260693808 (LWP 10732)]
[New Thread -1387365488 (LWP 10959)]
[New Thread -1378960496 (LWP 10958)]
[New Thread -1370567792 (LWP 10957)]
[New Thread -1345479792 (LWP 10781)]
[New Thread -1336607856 (LWP 10770)]
[New Thread -1294353520 (LWP 10769)]
[New Thread -1302746224 (LWP 10768)]
[New Thread -1283015792 (LWP 10734)]
[Current thread is 0 (LWP 10732)]

Thread 9 (Thread -1283015792 (LWP 10734)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0x082865f6 in Digikam::ScanController::run ()
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x083dafc0 in ?? ()
#6  0x00000000 in ?? ()

Thread 8 (Thread -1302746224 (LWP 10768)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x083fcc78 in ?? ()
#6  0x00000000 in ?? ()

Thread 7 (Thread -1294353520 (LWP 10769)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x08440f28 in ?? ()
#6  0x00000000 in ?? ()

Thread 6 (Thread -1336607856 (LWP 10770)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x0a1e5060 in ?? ()
#6  0x00000000 in ?? ()

Thread 5 (Thread -1345479792 (LWP 10781)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x0bbae520 in ?? ()
#6  0x00000000 in ?? ()

Thread 4 (Thread -1370567792 (LWP 10957)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x086b71d8 in ?? ()
#6  0x00000000 in ?? ()

Thread 3 (Thread -1378960496 (LWP 10958)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x0bbdb430 in ?? ()
#6  0x00000000 in ?? ()

Thread 2 (Thread -1387365488 (LWP 10959)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6ebe206 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/i686/libpthread.so.0
#2  0xb6f1a276 in QWaitCondition::wait ()
from /usr/lib/qt4/lib/libQtCore.so.4
#3  0xb630406e in Digikam::LoadSaveThread::run ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#4  0xb6f19bd7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#5  0x0d73bda0 in ?? ()
#6  0x00000000 in ?? ()

Thread 1 (Thread -1260693808 (LWP 10732)):
[KCrash Handler]
#6  0xb63f634f in Digikam::EditorTool::readSettings ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#7  0xb64140de in Digikam::RawImport::slotInit ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#8  0xb63f6cfa in Digikam::EditorTool::qt_metacall ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#9  0xb63f6daa in Digikam::EditorToolThreaded::qt_metacall ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#10 0xb64142aa in Digikam::RawImport::qt_metacall ()
from /home/mikolaj/kde/lib/libdigikam.so.1
#11 0xb6fff05a in QMetaObject::activate ()
from /usr/lib/qt4/lib/libQtCore.so.4
#12 0xb6fff4a2 in QMetaObject::activate ()
from /usr/lib/qt4/lib/libQtCore.so.4
#13 0xb7006da7 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#14 0x0d6dba00 in ?? ()
#15 0xb708acc8 in QAbstractItemModel::sort ()
from /usr/lib/qt4/lib/libQtCore.so.4
#16 0x00000000 in ?? ()


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

[mfi]

Hello,



Gilles Caulier pisze:

> Michael,
>
> I cannot reproduce the problem here.
>
> I have tested to import your RAW file using digiKam for KDE4
> (0.10.0-beta4) or digiKam for KDE3 (0.9.5-svn) using new RAWImport
> tool for image editor, and all work fine with highlight recovery settings.
>
> For RAW file decoding, i use libkdcraw based on LibRaw
> (http://www.libraw.org). LibRaw currently use the last dcraw code for
> demosaicing. Now look my screenshots:
>
> * This the preview of raw import tool with RAW demosaicing settings.
> Postprocessing use default settings (no gamma/curve/exposure
> adjustment) . Of course like it's a preview with a divided by 4 image
> size, huge zooming give artifact. But it's enough to set demosaicing
> configuration. Also, working on a reduced raw decoded image speedup
> computation. Note that i use 16 bits color depth, not 8 (it's a non
> sence to use 8 bits color depth with RAW)
>
> http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

Is that possible in version 9.4 ? I am not familiar with svn and there's
no KDE 4 for gentoo at this moment. I can't see Raw Import Tab in my
digikam and I don't have options that You have below histogram. If this
is just version related problem I can wait a bit for a more current
release for my distro. I tried sharpening tool for digikam and now I
just don't want to use other program ;)

>
> And now, the best: the full raw image in editor. Look like the color
> (white balance) is better than RAW studio !
>
> http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-editor.png
>
> For me, it's a good example how to use properly RAW files in digiKam.
The white balance in RawStudio is messed up, but it's my fault - I set
it up manually,  just to show the problem with highlights.

>
> Note : the preview from digiKam  icon view is rendered using JPEG
> preview image from RAW file. It's not RAW image data decoded. In fact
> the preview  JPEG  is adjusted using camera  firmware. It's still JPEG
> : only 8 bits color depth ! this is why highlight are broken, and it's
> a good example to explain why RAW is always better than JPEG.

But highlights are broken after RAW decoding as far as I understand...
Preview (didn't know RAW contains jpg previevs, thanks) is rendered
correctly and highlights aren't broken there... Did I miss something ?
>
> Unforget : jpeg is fine to take shot and publish as well the image on
> the web (fats workflow). Never use JPEG if you want to retouch photo,
> especially color settings ! This file format is not adapted and use
> lossy compression algorithm.

Thanks - that's why I use RAW instead of JPG ;)
>
> Best
>
> Gilles Caulier


Best Regards
Michael Fidler

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

[Gilles Caulier-4]

2008/10/7 mfi <[hidden email]>

Hello,



Gilles Caulier pisze:

> Michael,
>
> I cannot reproduce the problem here.
>
> I have tested to import your RAW file using digiKam for KDE4
> (0.10.0-beta4) or digiKam for KDE3 (0.9.5-svn) using new RAWImport
> tool for image editor, and all work fine with highlight recovery settings.
>
> For RAW file decoding, i use libkdcraw based on LibRaw
> (http://www.libraw.org). LibRaw currently use the last dcraw code for
> demosaicing. Now look my screenshots:
>
> * This the preview of raw import tool with RAW demosaicing settings.
> Postprocessing use default settings (no gamma/curve/exposure
> adjustment) . Of course like it's a preview with a divided by 4 image
> size, huge zooming give artifact. But it's enough to set demosaicing
> configuration. Also, working on a reduced raw decoded image speedup
> computation. Note that i use 16 bits color depth, not 8 (it's a non
> sence to use 8 bits color depth with RAW)
>
> http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

Is that possible in version 9.4 ? I am not familiar with svn and there's
no KDE 4 for gentoo at this moment. I can't see Raw Import Tab in my
digikam and I don't have options that You have below histogram. If this
is just version related problem I can wait a bit for a more current
release for my distro. I tried sharpening tool for digikam and now I
just don't want to use other program ;)

Raw Import  tool do not exist with 0.9.4. Only current code from svn (coming with next 0.9.5 release) has this code.

You can customize highlight recovery level in Raw decoding settings panel, but this config is common for all RAW files to load in editor. You cannot customize it like with RAW Import.

Also, 0.9.4 use old dcraw based libkdcraw. 0.9.5 use new version with LibRaw: it's more powerfull.

>
> And now, the best: the full raw image in editor. Look like the color
> (white balance) is better than RAW studio !
>
> http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-editor.png
>
> For me, it's a good example how to use properly RAW files in digiKam.

The white balance in RawStudio is messed up, but it's my fault - I set
it up manually,  just to show the problem with highlights.

>
> Note : the preview from digiKam  icon view is rendered using JPEG
> preview image from RAW file. It's not RAW image data decoded. In fact
> the preview  JPEG  is adjusted using camera  firmware. It's still JPEG
> : only 8 bits color depth ! this is why highlight are broken, and it's
> a good example to explain why RAW is always better than JPEG.

But highlights are broken after RAW decoding as far as I understand...

Not here.
 

Preview (didn't know RAW contains jpg previevs, thanks)

RAW is a container : JPEG, RAW image, ICC profile, metadata data (Exif + makernotes), Gamma curves, etc...
 

is rendered
correctly and highlights aren't broken there... Did I miss something ?

>

I think no, but it's not easy to investiguate whithout more info.

Can you take a screencast of you digikam session, including RAW setting and RAW loading in editor ? Best tool for that is recordmydesktop...

Gilles

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

[mfi]

Gilles Caulier pisze:

> Raw Import  tool do not exist with 0.9.4. <http://0.9.4.> Only current
> code from svn (coming with next 0.9.5 release) has this code.
>
> You can customize highlight recovery level in Raw decoding settings
> panel, but this config is common for all RAW files to load in editor.
> You cannot customize it like with RAW Import.
>
> Also, 0.9.4 use old dcraw based libkdcraw. 0.9.5 use new version with
> LibRaw: it's more powerfull.
>

I could accept common setting for all RAW files - at least for
highlights recovery level - (most programs even don't have settings for
this I guess, they import RAW automatically), but I only would like it
to work as it does in other programs.


>
> Can you take a screencast of you digikam session, including RAW
> setting and RAW loading in editor ? Best tool for that is
> recordmydesktop...
>
> Gilles
here it is:

http://www.fotopolska.info/example/digiKam.ogv (6,4 MB) - every possible
highlights setting tried.


regards
Michael

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

[Gilles Caulier-4]

2008/10/7 mfi <[hidden email]>

Gilles Caulier pisze:
> Raw Import  tool do not exist with 0.9.4. <http://0.9.4.> Only current

> code from svn (coming with next 0.9.5 release) has this code.
>
> You can customize highlight recovery level in Raw decoding settings
> panel, but this config is common for all RAW files to load in editor.
> You cannot customize it like with RAW Import.
>
> Also, 0.9.4 use old dcraw based libkdcraw. 0.9.5 use new version with
> LibRaw: it's more powerfull.
>

I could accept common setting for all RAW files - at least for
highlights recovery level - (most programs even don't have settings for
this I guess, they import RAW automatically), but I only would like it
to work as it does in other programs.

>
> Can you take a screencast of you digikam session, including RAW
> setting and RAW loading in editor ? Best tool for that is
> recordmydesktop...
>
> Gilles

here it is:

http://www.fotopolska.info/example/digiKam.ogv (6,4 MB) - every possible
highlights setting tried.

Witch version of libkdcraw you use exactly ? Go to About dialog and look version ID of library.

It sound like  bug fixed in current version, but i'm not sure.

I will release a new libkdcraw based on LibRaw. Code is stable now. I think this will fix your problem definitivly. It will support also new RAW cameras, especially devices show to Photokina during september.

Gilles Caulier

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

[mfi]

Hello Gilles, the version was 0.1.4.
Recently I moved to KDE 4 hoping it will help me to get digikam working.
Things gone even worse, now digikam isn't working at all - I guess I
could repair this but I just can wait until new version of digikam will
show in portage. If You want to check if the problem was bug You
mentioned - let me know - I can try to get digikam working and check new
library, in other case I will just use other program for some time.
Thank You very much.

Michael Fidler


Gilles Caulier pisze:

>
>
> 2008/10/7 mfi <[hidden email]>
>
>     Gilles Caulier pisze:
>     > Raw Import  tool do not exist with 0.9.4. <http://0.9.4.>
>     <http://0.9.4.> Only current
>     > code from svn (coming with next 0.9.5 release) has this code.
>     >
>     > You can customize highlight recovery level in Raw decoding settings
>     > panel, but this config is common for all RAW files to load in
>     editor.
>     > You cannot customize it like with RAW Import.
>     >
>     > Also, 0.9.4 use old dcraw based libkdcraw. 0.9.5 use new version
>     with
>     > LibRaw: it's more powerfull.
>     >
>     I could accept common setting for all RAW files - at least for
>     highlights recovery level - (most programs even don't have
>     settings for
>     this I guess, they import RAW automatically), but I only would like it
>     to work as it does in other programs.
>
>
>     >
>     > Can you take a screencast of you digikam session, including RAW
>     > setting and RAW loading in editor ? Best tool for that is
>     > recordmydesktop...
>     >
>     > Gilles
>     here it is:
>
>     http://www.fotopolska.info/example/digiKam.ogv (6,4 MB) - every
>     possible
>     highlights setting tried.
>
>
> Witch version of libkdcraw you use exactly ? Go to About dialog and
> look version ID of library.
>
> It sound like  bug fixed in current version, but i'm not sure.
>
> I will release a new libkdcraw based on LibRaw. Code is stable now. I
> think this will fix your problem definitivly. It will support also new
> RAW cameras, especially devices show to Photokina during september.
>
> Gilles Caulier
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>  

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

[mfi]

I have KDE 4, I have digikam 0.10.0_beta2 now and the same problem.
Clipped highlights - and I don't have additional options for Raw import
below histogram, that Gilles showed  here:
 http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

Maybe the reason is that I don't have libraw listed in digikam
components as it can be seen here:

http://www.fotopolska.info/example/shot.jpg ? I couldn't find libraw in
gentoo packages either.

Highlights seem to be clipped a  VERY little bit less. Same as before -
different highlight import options doesn't seem to affect result.

Thanks for Your effort very much Gilles, but I just wouldn't like to
install new library without using portage - I am a bit affraid of
messing my system. Hope there's other way to fix this.

Michael.


Gilles Caulier pisze:

>
>
> 2008/10/7 mfi <[hidden email]>
>
>     Gilles Caulier pisze:
>     > Raw Import  tool do not exist with 0.9.4. <http://0.9.4.>
>     <http://0.9.4.> Only current
>     > code from svn (coming with next 0.9.5 release) has this code.
>     >
>     > You can customize highlight recovery level in Raw decoding settings
>     > panel, but this config is common for all RAW files to load in
>     editor.
>     > You cannot customize it like with RAW Import.
>     >
>     > Also, 0.9.4 use old dcraw based libkdcraw. 0.9.5 use new version
>     with
>     > LibRaw: it's more powerfull.
>     >
>     I could accept common setting for all RAW files - at least for
>     highlights recovery level - (most programs even don't have
>     settings for
>     this I guess, they import RAW automatically), but I only would like it
>     to work as it does in other programs.
>
>
>     >
>     > Can you take a screencast of you digikam session, including RAW
>     > setting and RAW loading in editor ? Best tool for that is
>     > recordmydesktop...
>     >
>     > Gilles
>     here it is:
>
>     http://www.fotopolska.info/example/digiKam.ogv (6,4 MB) - every
>     possible
>     highlights setting tried.
>
>
> Witch version of libkdcraw you use exactly ? Go to About dialog and
> look version ID of library.
>
> It sound like  bug fixed in current version, but i'm not sure.
>
> I will release a new libkdcraw based on LibRaw. Code is stable now. I
> think this will fix your problem definitivly. It will support also new
> RAW cameras, especially devices show to Photokina during september.
>
> Gilles Caulier
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>  

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

[Gilles Caulier-4]

2008/10/10 mfi <[hidden email]>

I have KDE 4, I have digikam 0.10.0_beta2 now and the same problem.
Clipped highlights - and I don't have additional options for Raw import
below histogram, that Gilles showed  here:

 http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

Maybe the reason is that I don't have libraw listed in digikam
components as it can be seen here:

No.

Go to setup panel, in image editor section, and set on "Raw Import" option

Gilles Caulier

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

[Gilles Caulier-4]

For KDE3, libkdcraw 0.1.6 is just released. i recommend to use it...

http://www.digikam.org/drupal/node/379

Gilles Caulier

2008/10/10 Gilles Caulier <[hidden email]>

2008/10/10 mfi <[hidden email]>

I have KDE 4, I have digikam 0.10.0_beta2 now and the same problem.
Clipped highlights - and I don't have additional options for Raw import
below histogram, that Gilles showed  here:

 http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png

Maybe the reason is that I don't have libraw listed in digikam
components as it can be seen here:

No.

Go to setup panel, in image editor section, and set on "Raw Import" option

Gilles Caulier

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

[mfi]

Gilles Caulier pisze:

>
>
> 2008/10/10 mfi <[hidden email]>
>
>     I have KDE 4, I have digikam 0.10.0_beta2 now and the same problem.
>     Clipped highlights - and I don't have additional options for Raw
>     import
>     below histogram, that Gilles showed  here:
>      http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png
>
>     Maybe the reason is that I don't have libraw listed in digikam
>     components as it can be seen here:
>
>
> No.
>
> Go to setup panel, in image editor section, and set on "Raw Import" option
>
> Gilles Caulier
>
>  

Sorry, I am beginning to feel really stupid about that, but I cannot
find that... I guess I tried every tab and It doesn't show.

Michael


P.S. I consider going back to KDE3 when current version of libkdcraw
will be released, but if this should work on KDE4 and digikam 0.10.0
maybe I'll give a try to KDE4 ?

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

[Gilles Caulier-4]

2008/10/11 mfi <[hidden email]>

Gilles Caulier pisze:

>
>
> 2008/10/10 mfi <[hidden email]>
>
>     I have KDE 4, I have digikam 0.10.0_beta2 now and the same problem.
>     Clipped highlights - and I don't have additional options for Raw
>     import
>     below histogram, that Gilles showed  here:
>      http://digikam3rdparty.free.fr/Screenshots/temp/rawimport/pef-rawimport-preview.png
>
>     Maybe the reason is that I don't have libraw listed in digikam
>     components as it can be seen here:
>
>
> No.
>
> Go to setup panel, in image editor section, and set on "Raw Import" option
>
> Gilles Caulier
>
>

Sorry, I am beginning to feel really stupid about that, but I cannot
find that... I guess I tried every tab and It doesn't show.

with 0.9.5-svn or 0.10.0-beta4 (not 0.9.4) go in this panel:

http://digikam3rdparty.free.fr/Screenshots/setup/setuprawimport.png

Gilles Caulier

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

Dnia Saturday 11 of October 2008, Gilles Caulier napisał:
> For KDE3, libkdcraw 0.1.6 is just released. i recommend to use it...
>
> http://www.digikam.org/drupal/node/379
>
> Gilles Caulier

OK, with latest svn code (KDE3 branch) I was able to get nice results.
Still:

a) not on defaults (had to use Highlights Rebuild, Level 6, plus some
   curve work)
b) RawTherapee has better sharpness, it is very easy to "oversharp"
   images in digiKam - ugly artefacts are becoming visible

m.

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