Bug 134164 - Be able to use the settings from inside the .NEF file itself
Summary: Be able to use the settings from inside the .NEF file itself
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-DImg-RAW (show other bugs)
Version: 0.9.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-16 13:45 UTC by Dennis Gnad
Modified: 2017-07-31 15:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Gnad 2006-09-16 13:45:17 UTC
Version:           0.9-svn 2006-09-15 (using KDE KDE 3.5.4)

There is something which would be very nice if it could be handled in digikam, but is probably very complicated...
Nikon's Software supports different settings for the raw file inside the raw file itself (so you have 1x raw data and 1,2,3 or even more different sets of other data which is then applied on the fly)
The data is part of the exif (or similiar data) - some guy (sorry can't remember who) showed me a webpage which contained all that data which he said could be used somehow. The data consists of white balance, unsharp mask settings, noise reduction settings, tonal curves, and many more. It would be very nice if the simpler of those settings could be used. The data can be stored in different sets inside the .nef file. As standard there is just the default set. It would be very very good if digiKam could store all the settings inside that file that you used for saving the last jpeg, so you can, if you want, still change the settings of the curves etc. - in fact it would be very nice if you could change the curves and they keep at their position, and the data is applied on the fly, so you dont lose image data - until the file is saved to jpeg, and/or the data is stored back to the raw files "last saved" set.
Comment 1 Médéric Boquien 2006-09-16 15:22:03 UTC
This would be nice, not only for Nikon raw files but also for Canon raw files which also contain profile information in the EXIF.
Comment 2 F.J. Cruz 2006-09-16 23:01:48 UTC
El S
Comment 3 Andreas Huggel 2006-09-17 05:29:23 UTC
I think ufraw does some of this, also using dcraw and exiv2

http://ufraw.sourceforge.net/

-ahu.
Comment 4 caulier.gilles 2008-03-18 13:37:40 UTC
Dennis,

Look my comment here :

http://bugs.kde.org/show_bug.cgi?id=124814#c10

And let's me here your viewpoint

Gilles
Comment 5 caulier.gilles 2011-12-18 17:29:47 UTC
Dennis,

Do you see my comment #4 ?

Gilles Caulier
Comment 6 caulier.gilles 2014-08-29 22:53:50 UTC
Dennis,

No response about my last comment ?

Gilles Caulier
Comment 7 Dennis Gnad 2014-08-31 21:44:21 UTC
Gilles,

sorry, for the long delay, I got a mail on your last comment but was busy at that time and forgot. I also started to use darktable for image processing some time ago, I guess that was before digikam got more advanced in raw processing like it seems now, I should re-check how that is now.

So I guess this is in stable digikam now?
When testing with 4:4.1.0-1 from debian, with a fresh initialized digikam, my NEFs all look mostly fine on import now :-)
Whereas my "old" digikam (updated config since something around version 0.9 probably), still shows too dark conversion, but probably a config issue on my side that happened over the time, I will just set it up fresh again.

OTOH, I am not sure what kind of basecurves you are applying. darktable started an effort to profile the cameras, so even if using different cameras (maybe shooting with a dslr and small compact at the same event) the same color rendition could be achieved, just as a hint here: http://www.darktable.org/2013/10/about-basecurves/

 - Dennis
Comment 8 caulier.gilles 2014-08-31 21:52:58 UTC
So we can considerate the original problem fixed with digiKam based on libraw decoder.

Gilles Caulier