Version: (using KDE KDE 3.5.8) OS: Linux This profile: http://ufraw.sourceforge.net/Colors/Nkx_D80_5_1691_06_000_434.icm can be used in ufraw, biblepro and other raw converters with no problem. Showfoto refuses to let me select it as my input profile, ergo I can't even try showfoto as rawconverter. From a similar bug, it appears that digikam has an option to override this, but I can't find the equivalent in showfoto.
It works fine for me using digikam-0.9.3-beta2 and the latest libkdcraw based on dcraw 8.80 (I think the libkdcraw will make a difference) What versions are you using? Gerhard
Hi Gerhard, i'm also using 0.9.3 beta2; I'm using libkdcraw-0.1.2.tar.bz2; browsing the source I see it is using dcraw 8.77. I'll try building libkdcraw cvs trunk and see what happens. So in your case, in showfoto, if you go to showfoto preferences > colormanagement you see the d80's profile as one of the available input options?
I could checkout libkdcraw, however I can't find the way to build it, there is no configure nor autogen.sh. The INSTALL file mentions configure but there is no such thing. I tried autoconf configure.in.in with no luck. This is what I got: ari@nahuatl:~/Desktop/Builds/libkdcraw/libkdcraw$ ls AUTHORS configure.in.in INSTALL libkdcraw.pc.in autom4te.cache COPYING libkdcraw Makefile.am ChangeLog dcraw libkdcraw.kdevelop NEWS configure.in.bot icons libkdcraw.lsm README Can someone give me a hint on how to build this thing so I can check if the issue is gone?
Try make -f Makefile.cvs before. Still, I suggest to follow the instructions at http://www.digikam.org/?q=download/svn (under "Install digiKam in your Home Directory"), because there also all relevant paths are defined.
Ar, What's new about this report ? it still valid using digiKam 0.9.4 ? Gilles Caulier
Hi Gilles, this is still a problem in 0.9.4 & showfoto 0.8. If I put the profile in a folder, and then select the folder as the "Color Profiles Directory", digikam/showfoto still do not list the d80 profile as an input profile (in the dropdown list).
Just to report that the problem still persists in digikam 0.10 SVN as of today - the .icc profile still works fine with UFRAW and bible.
The device class is indeed unknown: it is "nkbf", 0x6e6b7066, which is not specified in the ICC specification. I found this: http://newsgroups.derkeiler.com/Archive/Comp/comp.periphs.scanners/2006-05/msg00222.html which suggest to treat it just like an input device profile. Should we do this? Does anyone know more?
SVN commit 925638 by mwiesweg: Recognize special proprietary device class in Nikon profiles CCBUG: 152528 M +1 -0 setupicc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=925638
Ar, the device will in current 0.10 SVN now be recognized as input profile. Can you test if it will also be used properly? (I dont know if there are any other checks for device class in other code paths or lcms)
Marcel, thanks a lot, it works now. I can import my NEFs directly into digikam for the first time. The converted raws in digikam look similar to same raws converted in UFRAW, but for some reason not exactly equal. This is with both apps controls in their default values. UFRAW has a "Exposure Compensation in EV" control set to zero, which I guess has something to do with Digikam's "Contrast". I guess the difference comes from two UFRAW's controls associated with the Input Profile called Gamma and Linearity. For Nikon, there is a recommendation to set this to 0.45 and 0.10 respectively. For some reason digikam's raw converter doesn't have these settings. This bug has been fixed so changing status.