You can use the 'o' key to show over and under exposed areas in darktable.
On 24 Mar 2015 07:45, Matthias Bodenbinder wrote:
>
> For those of you who do not speak german: You can start watching the video at
> 1:14 min. This is the point where the screen goes black and he starts moving
> the slid
284d0ad43b6ecc96284005fe5ad449c9175f39cf should be considered for stable
--
Edouard Gomez
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with
iew the bugfix.
--
Edouard Gomez
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software dev
implementation (we only replaced the mipmap cache).-joOn Sat, Jan 3, 2015 at 1:29 PM, Edouard Gomez <ed.gomez@free.fr> wrote:On 01/02/2015 09:22 PM, johannes hanika wrote:
> this is now merged to master. let us know how it goes and if you have
> any questions.
I get crashes when generating
0x21b44)
#14 0x40420b (/home/ed/opt/darktable/bin/darktable-cli+0x40420b)
--
Edouard Gomez
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnershi
cation sites some 3 years ago that
have been driven you crazy these last two days.
My intention was to clean the cache code to avoid exactly this kind of
troubles, i failed so hard :-D
--
Edouard Gomez
--
Want excitement
may be me missing those allocation
sites or code added later on, i don't remember
As for the commnt about 4*sizeof(float), iirc, it is about the structure
being at least a SSE register, but i don't remember why... it's like a
2011 c
(in
my D7000 usacase, all reds/oranges were simply oversaturated). This
approach is way too simplistic, to be correct color wise
--
Edouard Gomez
--
Want fast and easy access to all the code in your enterprise? Index and
The use case I'd to use one or the other but not both at the same time.
Also note that without manual tuning of the a* and b* channels of the
tonecurve, you might find the result a little bit too flat colorwise. I'm still
wondering how to improve their fitting. So outputting them is disabled by
determine
the curves.
As for the 350D bad curves, blurring the input pictures, resizing down
the images could help.
I may be able to spend a bit more time for solving out my
These curves aren't good at all.
You may have messed something in the process or I may have left an enormous bug.
Do you have the save state available for me to download ?
On 10 Mar 2014 18:25, Ger Siemerink wrote:
>
> retry, will this be visible?
>
>
> 2014-03-10 14:02 GMT+01:00 Robert William
Hello the list,
Just to let you know that I commited fixes to the tiff output module.
These commits are good candidates for next 1.4 stable release (if
scheduled):
8add5fbf30461ad474f23b89e29ffd37c96c3d3a
573ef4134a6e7bfc25b31f76063c210e0df77f2f
--
Edouard Gomez
eprofiling, i'll push in a minute.
you're welcome
> i can't believe you used this download site :)
it can host legit files too :-D
--
Edouard Gomez
--
Symantec Endpoint Protection 12 positioned as A
co.nz/#!EUcH2Qab!RJZ50T0l36yXkhsEEsMMHHhLbe9auYYFinvFSCOwaBM
I used graph2 to compare against D5100 (same sensor), seems to at least
not be off completly :-D
Cheers
--
Edouard Gomez
--
Symantec Endpoint Protection 12 positioned
cams.
If the denoise profile experts give a go, i'll commit the profile asap
for D7000 so git users can report back.
--
Edouard Gomez
gaussian.pdf
Description: Adobe PDF document
poissonian.pdf
Description: Adobe PD
15 matches
Mail list logo
