dt-l...@stefan-klinger.de (2019-Jun-04, excerpt):
> and not enough good searchable concise test.
"text", not "test".
Case in point: Text is easier to edit/bugfix/adapt later on.
--
http://stefan-klinger.deo/X
I prefer receiving plain text messages, not
Aurélien Pierre (2019-May-29, excerpt):
> I guess I will have to record video tutorials in English then…
No, please, just write it down. I hate watching videos until the
presenter finally gets to the point. There's already too many videos
and not enough good searchable concise test.
--
On Fri, May 31, 2019, at 13:15, Heiko Bauke wrote:
> Hi,
>
> Am 29.05.19 um 22:14 schrieb jys:
> > Since the basecurve module must be retained, I'm wondering if, now
> > that its default position has been moved to after colorin, is there
> > anything preventing it from being moved even further
Hi,
Am 29.05.19 um 22:14 schrieb jys:
Since the basecurve module must be retained, I'm wondering if, now
that its default position has been moved to after colorin, is there
anything preventing it from being moved even further along the pipe,
to the most harmless possible location (whatever that
t;
> https://support.google.com/youtube/answer/6373554
>
>
>
> Tim
>
>
>
> *From:* Matthias Andree
> *Sent:* Thursday, May 30, 2019 8:09 AM
> *To:* darktable-dev@lists.darktable.org
> *Subject:* Re: [darktable-dev] DT bad on skin tones?
>
>
>
> Am 29.
it.
https://support.google.com/youtube/answer/6373554
Tim
From: Matthias Andree
Sent: Thursday, May 30, 2019 8:09 AM
To: darktable-dev@lists.darktable.org
Subject: Re: [darktable-dev] DT bad on skin tones?
Am 29.05.19 um 12:28 schrieb Aurélien Pierre:
I guess I will have to record
Am 29.05.19 um 12:28 schrieb Aurélien Pierre:
>
> I guess I will have to record video tutorials in English then…
>
Or find someone to translate French to English.
Subtitles/captions have been proposed by Florian, too.
___
On Tue, May 28, 2019, at 03:25, Aurélien Pierre wrote:
> I personally think darktable should default to a neutral look (dark and
> ugly), but not all the dev team agrees. I guess having a very neutral
> picture (only demosaiced) as a default starting point in the darkroom
> would freak out
If there's some interest maybe i can dedicate some time to create English
subs for existing good videos on Darktable from you, rawfiner, carafife...
But not before July, I have a competition for a PhD grant at the end of
June.
Even though I prefer coding improvements :-P I already have a list of
Florian - thanks I will check these out. My French not so good and I
have never used lightroom.
I have watched quite a few videos - the ones I have seen don't
necessarily go into the relative merits of different modules (eg base vs
tone curve).
On 5/28/19 10:48 PM, Florian W wrote:
> @Paul
>
>
"I personally think darktable should default to a neutral look (dark and
ugly), but not all the dev team agrees."
It all depends what target you have for Darktable. There are probably and
surely not only pro photographers using it, and I'm not sure if all the
passionate amateurs are doing enough
@Paul
Appart from the manual, there's several people on youtube either presenting
what you can do module per module and what effect on an image can be
expected for each slider (technical approach), or doing screen recording of
photographs edit (retouch/artistic approach) for a full processing or
On Wednesday, May 29, 2019 5:48:30 AM CEST paul sorenson wrote:
> This thread is fascinating to me. Are there resources out there for
> those who want to learn a more technical approach to editing with
> Darktable. As has been mentioned elsewhere, the manual kind of presents
> modules in isolation
This thread is fascinating to me. Are there resources out there for
those who want to learn a more technical approach to editing with
Darktable. As has been mentioned elsewhere, the manual kind of presents
modules in isolation eg the base curve docs don't come with a warning -
well maybe a hint in
A raw "picture" is just a text file filled with RGB code values. These
code values are not data and need to be decoded, by the software but
also by the user, to be turned into data (meaning : colors). The
software can do some of the low-level decoding, but at the end, only the
user knows if the 80
"
Sure, there are people who want to fight the theory of signal processing to
complain about the consequences, and people who do the right thing at the
right time in the pixelpipe. Surprisingly, the latter get better results
faster.
Thanks for trying to make my point a different one than what I
I couldn't have said it better than Aurélien. I have a default setting for
basecurve that matches any input and is always linear. This essentially
makes the the module do nothing. And I have this since I started using DT.
Caveat: I'm a VFX professional. I know a bit about this topic. ;)
.mm
While I really like the idea behind filmic module, still it's not
always easy to get the colors I want with it. I guess, depending on the
camera, base curve might give better colors by default, but will make
much trouble in other departments. Obvious point that it's not that
easy as just using
Hi !
That falls back to the difference between Lightroom and Capture One
colors… If the in-camera software has been tweaked for warmer skins, you
won't get the same result with an all-purpose matrice alone.
In color balance, push the highlights slider towards magenta (opposite
of green) with a
But since apparently the people in charge of Darktable know about this :
"which was a design mistake in the first place because you are applying a
matrice profile expecting scene-linear input on perceptually-encoded data"
are there plans to fix the design mistake ?
I know that you are offering
Sure, there are people who want to fight the theory of signal processing
to complain about the consequences, and people who do the right thing at
the right time in the pixelpipe. Surprisingly, the latter get better
results faster.
Filmic is simple to use if you understand what exposure means in
On 5/28/19, François Tissandier wrote:
>
>
> Indeed the first thing I'm doing is applying a style either switching to
> the base curve, or disabling the module to use filmic. I love what I can
> get out of filmic often, but to be honest Aurélien, filmic is also a bit
> complex to use. I'm
It is not a matter of digital development choices here, nor of one's own
tastes or choices, it is a matter of trying to know whether the input color
profiles are well applied in darktable.
We can't compare colors if we use modules that are messing the colors (and
we know base curve does that).
So
The base curve can be still used with the standard one instead of the
camera one, colours are quite fine then. I was doing that before the
arrival of filmic. So the base curve can be kept. And indeed it's good to
have the choice.
Le mar. 28 mai 2019 à 10:00, Florian W a écrit :
> Not everyone
Not everyone has the same approach of digital development (eg. Film like
response vs more creative curve editing, with its disadvantages) and one of
the strong advantage of Darktable is allowing all these use cases. Starting
a war about this won't get us anywhere in the issue at hand here.
Le
Indeed the first thing I'm doing is applying a style either switching to
the base curve, or disabling the module to use filmic. I love what I can
get out of filmic often, but to be honest Aurélien, filmic is also a bit
complex to use. I'm trying the presets, but often I have to change the
For the last time :
*BASE CURVES ARE EVIL, CRAP, GARBAGE, NO-GO, DON'T TOUCH, BIO
HAZARD, KEEP AWAY, HUN HUN, SURVIVORS WILL BE SHOT AGAIN.*
I wouldn't have taken 2 months of my life to develop filmic if base
curves had worked as expected. Base curves are a broken design and will
always
On Mon, May 27, 2019, at 13:08, François Tissandier wrote:
>
> I think I'm maybe seeing the same kind of pb with the Sony A7RII and
> A7RIII matrix. I always had problems with dark blues on the Sony
> cameras, and I'm often changing the base curve to "neutral" to avoid
> having big issues.
Am 27.05.2019 um 01:09 schrieb Šarūnas:
Hi, I re-did the test with the Fuji X-E2 version of the test-chart
shoot and the skin colors are much better.
This interest me to, however it is not obvious, what you [re-]did to get
better colors. Care to elaborate? Thanks!
Same settings. Just some
On 27.5.19 01:09, Šarūnas wrote:
On 5/25/19 3:11 PM, Christian wrote:
Hi, I re-did the test with the Fuji X-E2 version of the test-chart
shoot and the skin colors are much better.
This interest me to, however it is not obvious, what you [re-]did to get
better colors. Care to elaborate?
On 5/25/19 3:11 PM, Christian wrote:
> Hi, I re-did the test with the Fuji X-E2 version of the test-chart
> shoot and the skin colors are much better.
This interest me to, however it is not obvious, what you [re-]did to get
better colors. Care to elaborate? Thanks!
Šarūnas
darktable handles the matrices all the same way. It's simple linear
algebra, if it works for some matrices, it will work for all matrices.
But if the coefficients of the matrice are wrong, nothing magical will
happen.
Le 25/05/2019 à 21:11, Christian a écrit :
> Hi,
> I re-did the test with the
Hi,
I re-did the test with the Fuji X-E2 version of the test-chart shoot
and the skin colors are much better.
Maybe this helps in identifying the problem.
Link to RAW file:
https://www.dpreview.com/reviews/image-comparison/download-image?s3Key=6641b9cbeec04777b85655fad61e4b4d.raf
Chris
Am
Hi Florian,
thanks for pointing out a possible workaround (dcraw), but in general
I prefer as few steps as possible in my workflow. :-)
Concerning input profiles: If dcraw/RawTherapee's profiles are good,
maybe they could be used in DT too...
Chris
Am 24.05.2019 um 22:21 schrieb Florian Hühn:
> So the input color profile (camera RGB -> XYZ transformation matrice) is
wrong in darktable.
Maybe it is not the the color matrix itself that is wrong (source code says
it was extracted from Adobe DNG Converter and those matrices are usually
very good), but handling the color matrix in DT is
So the input color profile (camera RGB -> XYZ transformation matrice) is
wrong in darktable. Can you export an ICC input profile from whatever
software the good picture comes from ?
Aurélien.
Le 24/05/2019 à 20:40, William Ferguson a écrit :
> Perhaps a better check for color accuracy is
Perhaps a better check for color accuracy is checking the color checker
included in the raw?
Regards,
Bill
On Fri, May 24, 2019 at 2:01 PM Moritz Moeller
wrote:
> On 24.5.19 19:26, David Vincent-Jones wrote:
> > Raw is RAW without processing. It is up to you to manipulate the
> > raw
On 24.5.19 19:26, David Vincent-Jones wrote:
Raw is RAW without processing. It is up to you to manipulate the
raw data to achieve the look that you want. [...]
OP clearly said they had no modules that shift color turned on.
The DT processed image clearly has green tint in the shadows.
Raw is RAW without processing. It is up to you to manipulate the
raw data to achieve the look that you want. There are 'styles' in dt
that will allow you to simulate provia if that is the look that you want.
On 2019-05-24 9:20 a.m., Christian wrote:
Hi,
Attached is a comparison between
39 matches
Mail list logo
