On Tue, Jun 4, 2013 at 6:23 PM, Alexander Wagner <[email protected]>wrote:
> On 06/03/2013 10:58 PM, Daniel Karch wrote:
>
> Hi!
>
> > I just switched to Darktable from Aftershot Pro, and
> > although I am getting to grips with it, I found it to be
> > less responsive then ASP, for example when adjusting
> > exposure with the histogram: I would click on the
> > histogram, move the mouse to the right to increase the
> > exposure, and nothing would happen for more than a second.
> > Then, there would be a "jump" in the histogram. It was
> > difficult to fine-tune the exposure that way.
>
> Did you have a look at the "Levels" module? I think it could
> accomplish what you want, especially as it displays it's own
> histogram as well. (Same for tone curve.)
>
> I found that dragging the histogram is a nice idea but
> usually doesn't work that well for me either due to the time
> lags you experience as well.
>
i'll try to put a request_focus(self) in the proxy exposure callback of the
exposure module (the histogram goes down that route), that should enable
the caching mechanisms which usually process only from the input to the
currently focused module to the end of the pipe (which would exclude
denoising in this case).
>
> > After some investigation, I found that this process would
> > be much smoother when the denoise plugins were disabled (I
> > used profiled denoise).
>
> Well, those are very heavy. However, they scale quite well if
> you have the possiblity to use OpenCL (thus moving them to
> your graphics cards gpus). Probably you have this option?
> Some nVidia-card with a bunch of RAM?
>
> > It seems that the denoise plugin is
> > applied constantly while I changed the exposure,
>
> Well, it sort of has to. It's in the pixel pipe and you want
> to see the effects of it, right?
>
> > thereby slowing down the process. An obvious workaround
> > would be to just disable denoise and only apply it after I
> > am happy with the exposure.
>
> Yepp. Unfortunately, especially as the mentioned profiled
> version of denoise has quite sensible presets one is
> inclinde to apply automagically...
>
> > But in my opinion it would be even better if such heavy
> > plugins could be temporarily disabled, i.e.:
> >
> > - User clicks on histogram: Disable CPU-heavy plugins
> > - User moves mouse around: Immediately update exposure
> > - User releases mouse button: Re-apply CPU-heavy plugins
>
> I'm not technician, but this could be tricky.
>
easily possible, but messy and a special case that seems unnecessary here.
j.
>
> --
>
> Kind regards, / War is Peace.
> | Freedom is Slavery.
> Alexander Wagner | Ignorance is Strength.
> |
> | Theory : G. Orwell, "1984"
> / In practice: USA, since 2001
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
