Normally You use one exposure module and push it 3EV max. They
duplicated it and pusched it 1 stop more so maybe here something tricky
happens. I did a test witch 5EV underexposed image on 80D and I didn't
noticed any exposure difference when I pushed it 3EV plus 2EV in
darktable. It could be a dif
On 3/2/19 5:37 AM, Bruce Williams wrote:
Yeah, but the numb nuts said "darktable could only give +3 stops of
exposure".
Clearly, they did not know about the ability to instigate a second
instead of a module.
As cameras continue to see better in the dark, I wonder if it would be
worth conside
* Moritz Mœller [03-02-19 15:59]:
> And how are you representative as a user? What's the relevance of your
> experience in the context of what I said?
>
> I have no problem with DT's UI but I'm a professional VFX artist and
> software engineer. My DT UX is zero representative for this reason and
And how are you representative as a user? What's the relevance of your
experience in the context of what I said?
I have no problem with DT's UI but I'm a professional VFX artist and
software engineer. My DT UX is zero representative for this reason and for
the most obvious one: I'm just a sing
Patrick Shanahan wrote:
fwiw: all software has it's own ideal about what a user
expects one can seldom move from one application to another
similar w/o having to learn the new UI. NONE is standard.
I tend to agree with this.
However, precisely because all are different good documentation is
* Jason Polak [03-02-19 11:03]:
> Going to have to disagree with that, and I think at least some of it is
> what you used first. I actually tried darktable before Lightroom and
> just by clicking around I found darktable pretty intuitive. Trying to do
> the same in Lightroom was confusing after th
I've extended darktable.gui.libs.filter and added the sort, sort order,
rating, and rating comparator gui elements.
I've also extended darktable.gui.libs.lighttable_mode and added layout and
zoom level.
Each of these works in the following manner:
If you call them without an argument, i.e.
darkt
Hello
Is it intentionally made - there is no way now to apply custom camera
color martix at import stage? There is no more editable settings for a
color profile to apply it for particular camera. I use custom made
profiles for my cameras and now I have to apply the profile manually to
all imp
Going to have to disagree with that, and I think at least some of it is
what you used first. I actually tried darktable before Lightroom and
just by clicking around I found darktable pretty intuitive. Trying to do
the same in Lightroom was confusing after that.
Jason
On 2/3/19 9:19 am, Moritz Mœl
I'm not surprised by the comment. DT's UI isn't intuitive.
If you are a person that learns a software by using it/trial & error
instead of reading the manual, your experience will be pretty unfavorable.
I haven't watched the video but from the comments here it seens it's about
features, not UX
In the comments, they do mention using another instance of exposure.
However, since they gave darktable a total of 20 minutes (and did not
ask someone who has actually used it), they may have forgotten about
base curves, which also influence brightness.
---
https://www.youtube.com/watch?v=RAb85TukS
even more easy than that: right click and enter value manually ... :-)
--
regards
Bernhard
https://www.bilddateien.de
Bruce Williams schrieb am 02.03.19 um 11:37:
Yeah, but the numb nuts said "darktable could only give +3 stops of
exposure".
Clearly, they did not know about the ability to ins
Yeah, but the numb nuts said "darktable could only give +3 stops of
exposure".
Clearly, they did not know about the ability to instigate a second instead
of a module.
I wouldn't lose any sleep over it.
Cheers,
Bruce Williams.
-- Forwarded message -
From: Andreas Schneider
Date: S
Hi,
there a video where they did take and underexposed image and then pushed the
exposure 4 EVs. darktable produced a darker image than the other raw
developers.
https://www.youtube.com/watch?v=RAb85TukSuc
___
darktable d
14 matches
Mail list logo
