On Sun, Aug 2, 2020, at 12:47, jot ess wrote:
> Wow! This comes already pretty close to out-of-camera jpegs[1]. I had
> tried to do it all with color balance. I obviously have to learn to
> properly use the filmic module.
It's just a quick attempt to match a non-ideal RAW grabbed from the web, b
Wow! This comes already pretty close to out-of-camera jpegs[1]. I had
tried to do it all with color balance. I obviously have to learn to
properly use the filmic module.
To me the Panasonic like base curve seems okay, Olympus-like alternate
seems too bright.
Now I just have to get oranges in so
On Sun, Aug 2, 2020, at 07:58, jot ess*g2 wrote:
> Now I have to figure out a default setting that compensates this.
> "auto-apply per camera basecurve presets" doesn't completely solve the
> problem because for my Panasonic TZ101 there seems to be only
> "Panasonic-like".
The "Panasonic-lik
* jot ess*g2 [08-02-20 11:00]:
> Hello Patrick,
> thank you, with that side note in the end of your last post you actually
> had the solution!
>
> Am 02.08.2020 um 15:50 schrieb Patrick Shanahan:
> > ...> remember that when importing an image, what is displayed is
> > determined by whether you c
Hello Patrick,
thank you, with that side note in the end of your last post you
actually had the solution!
Am 02.08.2020 um 15:50 schrieb Patrick Shanahan:
...> remember that when importing an image, what is displayed is
determined by whether you configured (lighttable) to use embedded
previe
* jot ess*g2 [08-02-20 09:33]:
> Hello Patrick,
> thank you for your advice. I'm trying to reproduce the steps on dt 3.0.2,
> Win 10 pro - sorry, I should have stated first what OS I'm on!
>
> I understand the procedure meant to temporarily hide the existing settings
> from the program to make it
Hello Patrick,
thank you for your advice. I'm trying to reproduce the steps on dt
3.0.2, Win 10 pro - sorry, I should have stated first what OS I'm on!
I understand the procedure meant to temporarily hide the existing
settings from the program to make it recreate the default settings.
And ~/.
Thank you very much for your feedback, I already fixed the typo.
I hope it will be useful. Let me know how it worked out for you. :)
Cheers!
On Sat, Aug 1, 2020 at 5:54 PM Jason Polak wrote:
> That is a fascinating program. I was thinking of doing a timelapse, so
> when I do I will try your so
* Patrick Shanahan [08-02-20 07:59]:
[...]
> you do not need to do a clean install to see if you have a configuration
> problem leading to the conditions you observe. Just
> (with darktable closed)
> mv ~/.config/darktable ~/.config/darktable.save
> and restart darktable
>
> see if importi
* jot ess*g2 [08-02-20 06:39]:
> Hello,
> I somehow managed to mess up some setting I am not aware of and I hope
> someone can help me find it.
> Effect: Any time I open a raw file in the darkroom, some change to
> saturation or vibrance seems to be applied, though both modules are not
> active. B
Hello,
I somehow managed to mess up some setting I am not aware of and I hope
someone can help me find it.
Effect: Any time I open a raw file in the darkroom, some change to
saturation or vibrance seems to be applied, though both modules are not
active. But obviously the saturation is strongly
11 matches
Mail list logo
