Hi,
On 28.10.18 15:51, Jason Polak wrote:
> Make a new preset where the base curve has no nodes (i.e. is a line).
> When you are making the preset check 'auto apply this preset to matching
> images'. Then click OK. It will still be on from now on but do nothing.
This is what I did. Then I created
Hi Aurélien
I like the idea of supporting a kind of workflow. That would help a lot of
people to get things right faster.
Looking at :
>> The branch is here :
>> https://github.com/aurelienpierre/darktable/tree/UI-refactor.
I'm wondering why color look up table is not placed in the basic group
erated than you want, I think
you can do a lot better than just a straight line :-)
-Original Message-
From: Jason Polak [mailto:jpo...@jpolak.org]
Sent: 28 October 2018 14:51
To: darktable-dev@lists.darktable.org
Subject: Re: [darktable-dev] Darkroom UI refactoring
> How can we
Note to Rob and Phillipe: I would very much appreciate just addressing
emails to the list, not to me (in most programs this is accomplished via
'Reply to List' function), as otherwise I get two copies of the same mail
Rob: Yes, it is possible to use other basecurves. Some people were
asking how to
15:51:03
Objet: Re: [darktable-dev] Darkroom UI refactoring
> How can we turn it off, "base curve" presets are protected in preset settings
> ?
Make a new preset where the base curve has no nodes (i.e. is a line).
When you are making the preset check 'auto apply this prese
> How can we turn it off, "base curve" presets are protected in preset settings
> ?
Make a new preset where the base curve has no nodes (i.e. is a line).
When you are making the preset check 'auto apply this preset to matching
images'. Then click OK. It will still be on from now on but do nothi
Hi Andreas,
> It shouldn't be turned of by default in darktable but you can turn it off in
> the preset settings for your installation.
How can we turn it off, "base curve" presets are protected in preset settings ?
Philippe
__
Hi Andreas,
Thanks for the write-up. After vacation I will try it out. Thanks in
advance!
Andreas Schneider schrieb am So., 28. Okt. 2018, 04:09:
> On Saturday, 27 October 2018 08:17:44 CEST Coding Dave wrote:
> > I wonder 2 things:
>
> Hi Dave,
>
> > 1) Is this whole color topic written down s
On Saturday, 27 October 2018 08:17:44 CEST Coding Dave wrote:
> I wonder 2 things:
Hi Dave,
> 1) Is this whole color topic written down somewhere with like a tutorial
> how to tune darktable for your camera to have nice colors (A video would be
> ok for me too)?
take a look at:
https://blog.pi
Seems like I never have understood the basecurve and LUT correctly. Since
basecurve is one of the default modules applies on every image upon opening
I never was questioning that it is required. I always wanted to tune it to
get good results with my Nikon D750 (I also have tried to create my own
pr
Thanks for the explanation about the base curve, Aurelien. Makes sense.
The base curve seemed to be too extreme in some cases and caused
unnatural colour gradients to appear in skin tones. I have since
reprocessed about 100 shots with the base curve disabled and the
improvement is quite noticeable
Le 26/10/2018 à 00:49, Jason Polak a écrit :
> Dear Aurelien,
>
> It's clear that you put a lot of thought into this and I am eager to try
> it. It is very helpful to see the GUI screenshots, and based on those I
> do have a few comments/questions:
>
> 1) Don't you think that the equalizer/local c
Dear Aurelien,
It's clear that you put a lot of thought into this and I am eager to try
it. It is very helpful to see the GUI screenshots, and based on those I
do have a few comments/questions:
1) Don't you think that the equalizer/local contrast module are more
similar to the sharpening module r
Hi everyone !
To follow up on that matter, I have done a pull request doing what I
discussed here : https://github.com/darktable-org/darktable/pull/1745
You will find screenshots showing the changes, a sum-up of the benefits
and a poll to vote for/against the change and give your feedback. After
On 2018-10-12 06:26 AM, Aurélien Pierre wrote:
> Moreover, base curves and tone curves are redundant as long as we don't
> explain clearly that base curves come before the color profile and work
> in RGB, whereas tone curves come after and work in Lab.
I do think that this is a very interesting po
I would be willing to help on the manual. Not lead, but assist.
Get Outlook for Android<https://aka.ms/ghei36>
From: William Ferguson
Sent: Friday, October 12, 2018 11:51:39 AM
To: darktable
Subject: Re: [darktable-dev] Darkroom UI refactoring
I s
I started darktable, added all the modules to the interface, then opened an
image and turned them all on. Then I looked at the pixelpipe order and
this is what I found. The order is top to bottom.
raw black/white point
invert
white balance
highlight reconstruction
chromatic aberrations
hot pixel
> A profile is generated by computing the error on a signal, that is the
> difference between the actual measure and the expected value. The
> correction (of lenses, of colors, etc.) will then aim at reverting this
> error,* assuming* the actual input signal is in the same state than the
> signal u
That's especially because most users are not interested by the insides
of darktable that we need to draw a foolproof path for them. I don't
want to pull a Steve Jobs here, but if users don't know, engineers have
to decide for them (Apple style), or, at very least, give clear
guidance, so they can m
+1 to Maurizio.
As a user, I'm not really interested in the technically correct order in which
the modules need to be applied. I would much rather have the ability to reorder
the modules to my liking inside the favourites tab. Or to be able to create
multiple user defined tabs and/or rename t
Hi all,
if I can leave my very little opinion.
I think we have to divide this matter in two separate flows: the
'technical' and the 'usability'
a) Technicians (developer) can understand and design very well the best
workflow for the image manipulation.
b) Users (normal users) are not very interest
+1
Am Fr., 12. Okt. 2018 um 09:00 Uhr schrieb rawfiner :
> Hi
>
> I strongly agree that the order of modules should be more clear in the UI,
> and that the UI should guide the user more. I like the suggestion Aurélien
> made for this.
>
> Trying to follow the module order in the pipeline gives th
Hi
I strongly agree that the order of modules should be more clear in the UI,
and that the UI should guide the user more. I like the suggestion Aurélien
made for this.
Trying to follow the module order in the pipeline gives the best
performance, as computations are done once.
In addition, not fol
I have given a lot of thought about your idea, which is obviously very
well thought out. Thanks for having this discussion; at the very least,
it is making me examine editing carefully. Of course I am not a dev so I
don't make any decisions for darktable, so feel free to ignore this but
I have some
On Wed, Oct 10, 2018 at 12:53 AM Aurélien Pierre
wrote:
> Le 10/10/2018 à 00:14, William Ferguson a écrit :
>
> On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre
> wrote:
>
>> What I call "signal-processing" here are all the module intended to clean
>> the data and turn an (always) damaged picture
Le 10/10/2018 à 00:14, William Ferguson a écrit :
> On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre
> mailto:rese...@aurelienpierre.com>> wrote:
>
> What I call "signal-processing" here are all the module intended
> to clean the data and turn an (always) damaged picture into what
> it is
On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre
wrote:
> What I call "signal-processing" here are all the module intended to clean
> the data and turn an (always) damaged picture into what it is supposed to
> look like in theory. That is :
>
>1. reconstructing missing parts (clipped highlights
What I call "signal-processing" here are all the module intended to
clean the data and turn an (always) damaged picture into what it is
supposed to look like in theory. That is :
1. reconstructing missing parts (clipped highlights)
2. recovering the dynamic range (tonemapping)
3. reconstructing
>
> * in/out color profiles are stored in the color tabs, whereas they are
> "basic" in the sense they are needed from technical requirements and
> always on,
Yes they are needed, but I wouldn't want them cluttering up the 'basic'
group. If they have to be modified, it's likely to be no
On 10/9/18 3:02 AM, Aurélien Pierre wrote:
But even if we keep the actual disposition, don't you think it's weird
that :
* in/out color profiles are stored in the color tabs, whereas they
are "basic" in the sense they are needed from technical
requirements and always on,
I don't th
rface organized in the order they effects
are processed. In learning dt, I have found I rework modules constantly and
never paid attention to why.
Get Outlook for Android<https://aka.ms/ghei36>
From: Aurélien Pierre
Sent: Tuesday, October 9, 3:03 AM
Subject: Re: [darktable-dev] Darkroom UI ref
But even if we keep the actual disposition, don't you think it's weird
that :
* in/out color profiles are stored in the color tabs, whereas they are
"basic" in the sense they are needed from technical requirements and
always on,
* signal-processing modules are mixed with creative ones
+1
On Mon, Oct 8, 2018 at 10:08 PM Jason Polak wrote:
> I've been thinking a little more about this idea, and while some modules
> might be better moved to other tabs (or a new set of tabs) like perhaps
> 'color reconstruction', the current setup still seems to make more sense
> in some ways too
I've been thinking a little more about this idea, and while some modules
might be better moved to other tabs (or a new set of tabs) like perhaps
'color reconstruction', the current setup still seems to make more sense
in some ways too. For example:
1. I prefer the idea of the 'effects' tab (like w
Hi community,
I like the idea to improve the UI and I appreciate the enthusiasm Aurelien
has put into it!
Darktable is a very nice piece of software feature-wise. Their developers
have created some great, feature-rich, wonderful tool in their spare time
and we are all very thankful for that. We l
Hi all
I don't think that reordering the modules would change much. The problem
remains the same: Either there are way to many parameters at once on the
screen to keep track of or there is a lot of clicking involved to dive
in and out of the individual modules.
I know that the advanced parameters
point in fixing blown areas if they are
not included in the inage.
Get Outlook for Android<https://aka.ms/ghei36>
From: Andreas Schneider
Sent: Monday, October 8, 2018 6:24:35 AM
To: darktable-dev@lists.darktable.org
Subject: Re: [darktable-dev] Darkr
On Monday, 8 October 2018 10:06:45 CEST Jørn Villesen Christensen wrote:
> Hi,
>
>
> An alternative suggestion (as I have also found the module list a bit...
> difficult to work with sometimes :-D ). I have often wished for a search
> box, so here is an idea; not thought through, but meant as ins
I'm with Jørn!
Great ideas, all.
Certainly feeling the pain of modules changing size and having to
constantly scroll up and down.
Cheers,
Bruce Williams
--
Mobile: +61 41 250 6349
audio2u.com
brucewilliamsphotography.com
shuttersincpodcast.com
sinelanguagepodcast.com
Hi,
An alternative suggestion (as I have also found the module list a bit...
difficult to work with sometimes :-D ). I have often wished for a search
box, so here is an idea; not thought through, but meant as inspiration:
How about one big list of modules, but with collapsible sections (and
Thanks Andreas !
So I tried the modifications I have suggested and I agree that the base
tab would be too crowded.
What I did was to split the technical modules in 2 tabs :
* the I/O and dynamic range ones in the base tab (color profile,
tonemap, exposure, crop etc.)
* the de-* (denoisin
On Monday, 8 October 2018 03:06:34 CEST Aurélien Pierre wrote:
> Hi everyone !
Hi Aurélien,
> I would like to propose a lifting for the UI in the darkroom.
I like the idea. However the crop and rotate module should be in the 'optics
handling' subcategory.
Also the corrections group is too big
First a message for everyone on this thread: please use just
reply-to-list. Else I get 2 copies of the message. No need to cc to me
or anyone else.
I see your point about your editing, if you have an injury. I use
darktable nearly daily and I regularly have to spend many hours in
darktable and edi
Le 08/10/2018 à 00:42, Jochen Keil a écrit :
> Hi,
>
> On Mon, Oct 8, 2018 at 5:39 AM Aurélien Pierre
> wrote:
>> The real question here is : could you get past the change and benefit from
>> it ?
>>
>> I'm biased here, since I developed repetitive strain injury in the wrist at
>> the early age
Hi,
I've also my workflow, but it's a bit different then yours (crop is one of
basic corrections for me, I almost never do noise removal as a one of first
steps). I'm not a big fan of arbitrary change here. Agree with Jochen that
custom tabs could be quite nice.
To achieve something similar I just
Hi,
On Mon, Oct 8, 2018 at 5:39 AM Aurélien Pierre
wrote:
>
> The real question here is : could you get past the change and benefit from it
> ?
>
> I'm biased here, since I developed repetitive strain injury in the wrist at
> the early age of 23. So I'm basically trying to improve the efficienc
The real question here is : could you get past the change and benefit
from it ?
I'm biased here, since I developed repetitive strain injury in the wrist
at the early age of 23. So I'm basically trying to improve the
efficiency of the workflow by decreasing as much as possible the number
of user in
Hi!
I can certainly see the logic of your idea. I definitely prefer the
current setup, if only because that's what I started with. I think the
only way to see if this is a good idea is to poll users because I am
sure there are some that would like your way and some that prefer the
current way.
I
Hi everyone !
I would like to propose a lifting for the UI in the darkroom.
*Problem**
*
Currently, the modules are separated in 5 tabs :
* base
* tones
* colors
* enhancements
* effects
But :
* some modules in the color group affect the tones as well (colo
49 matches
Mail list logo
