Here are noise profiling files for three cameras I'm using: Olympus E-1,
Olympus E-3 and Olympus EP-2:
https://docs.google.com/file/d/0B6jPA_Ww7jjcTVM3eEFuS0h3S1E/edit?usp=sharing
https://docs.google.com/file/d/0B6jPA_Ww7jjcR0puOVBwbkc0ZWc/edit?usp=sharing
https://docs.google.com/file/d/0B6jPA_Ww7jjcS2pMNWRKX1dmRE0/edit?usp=sharing
As regarding the usability of these profiles you have to judge at the
moment as I'm not sure my Darktable uses them at all (see the question
below).The EP-2 pdfs for ISO 3200 and ISO 6400 are a bit strange, but these
are as best as I could produce with my camera (made 4 sets of profiling
images and results were very similar). As we all know the sensors Olympus
used in these cameras are not really shiny regarding the noise ...
I'm happy to do more profiling if you decide the results are not ok.
Now the usage question.
The profiles are all in my library (~/.config/darktable/library.db) as
sqlite query shows:
sqlite> select * from presets where operation='denoiseprofile';
E-P2 iso
100||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
200||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
400||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
800||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
1600||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
3200||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-P2 iso
6400||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-1 iso
100||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-1 iso
200||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-1 iso
400||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-1 iso
800||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
100||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
200||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
400||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
800||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
1600||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
E-3 iso
3200||denoiseprofile|3||1|||||0.0|0.0|0.0|0.0|0.0|0.0|0.0|0.0|0|0|0|0|0|4|0|
But when I run Darktable (version 1.2, compiled from tarball, Ubuntu
12.10), the only thing I see in "profile" dropdown in "denoise (profiled)"
module is generic poisonian choice. When I turn the module on, it does
something (without displaying the generic option in dropdown) and when I
choose generic option it also does something. Does this mean that just
turning the module on chooses the denoise profile from the library if it
exists? The results are pretty much the same both ways (I admit, I didn't
have time so far to compare results in depth).
So if module automatically chooses the profile from the library, it would
be very useful if the module could provide a sort of feedback on profile it
has chosen (displaying "Olympus E-3 ISO 800" for example).
Thank you for great work on Darktable,
kind regards,
--
Damjan Vrenčur
Overland - cruising blog <http://blog.overland-cruising.org/>
Google+ <https://plus.google.com/105115819786059600928/posts>
S-adventure <http://www.s-adventure.com/>
GPG key: C6A3146F
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
