The change that I see in v. 4.0 is that all of my images appear 1 stop
underexposed as compared to the previous version. Earlier I did not need
to adjust exposure at all, now I must boost the exposure on all images.
David
On 2020-06-09 11:46 a.m., Alexander Rabtchevich wrote:
Hm, as I underst
Hi Nicolas,
Do you update submodule (git submodule update ; a git submodule init
is sometimes good to do again) ?
Yes, I use both commands every time I build dt master. I observed the
warnings for the first time some weeks ago. I copied the output of
build.sh to a file using ./build.sh | tee
Hi Peter,
I just compile last master (so 3.1.0+2031 now) and I don't have any
error about libxcf on my side (nor I have on previous compile). But I am
on Ubuntu 20.04 so that could make some differences.
Do you update submodule (git submodule update ; a git submodule init is
sometimes good t
Hm, as I understand, if I enable filmic plugin v 4.0 manually, I need to
add +1.0EV manually too? That wasn't so with 3.0.
With respect,
Alexander Rabtchevich
Aurélien Pierre wrote:
Hi,
there is a +1 EV added by default in exposure if you enable the
scene-referred workflow. I don't unders
Hi,
there is a +1 EV added by default in exposure if you enable the
scene-referred workflow. I don't understand what you mean. The exposure
bias is read in image EXIF, if the bias is 0 EV, then the setting is 0
EV too.
Cheers,
Aurélien.
Le 09/06/2020 à 19:46, Alexander Rabtchevich a écrit :
> H
Hello
Exposure compensation bias for my Sony A99 is 0EV and images are too
dark. They require to add +1EV to match filmic v.3
Current git master
With respect,
Alexander Rabtchevich
___
darktable developer mailing list
to uns
Dear developers,
3.1.0+2016~g40a922d0e, Ubuntu 18.04
Running the build script build.sh a large number of warnings is thrown
on terminal. All warnings relate to xcf.c. They seem to have no impact
on the correct result of the build process, the binaries are working
fine. A reduced list of the w
