Terry, That response time issue between the 2 versions may be the case for me too. However after upgrading I can't compare anymore, since I deleted all my 3.0.2 edits (I am a newbie and consider all I did as learning material). One possibility is that on a zoomed-out image the math is done in the cpu rather than in the gpu. I suspect this because of the much faster reponse of the export versus the response on the zoomed-out image. Not sure how I can monitor this, but I will try in the coming days. Met vriendelijke groet, Marc.
> Op 19 aug. 2020 om 01:46 heeft Thierry Rakotoarivelo <tr.d...@gmail.com> het > volgende geschreven: > > Thanks Marc and others that sent direct inputs. > > Your comment @Marc made me test a few scenarios, and indeed it seems like the > issue comes with v 3.2.1 when I re-edit an already edited (zoomed-out) image > with a history stack comprising +40 items (similar to you including multiple > instances of the same module). I note that I did not get such a slow response > on the same image with the same history stack with v 3.0.* though. > > I found that compressing the history stack greatly mitigate the issue, e.g. > on an image with +60 history items (a poorly exposed green-ish underwater > photo with lots of backscatter), hitting Compress History reduces the stack > to 25-ish items, and the module sliders become much more responsive upon > re-editing. It is still not as smooth on the same image (with compressed > stack) as with v 3.0.*. However, it's smooth enough to be usable and I > decided to re-upgrade to and use v 3.2.1. > > (the puzzling thing is that during the 1st original edit session of such an > image with +60 items in the history stack, the sliders of all used modules > and new instances are very responsive... so maybe there are some processing > strategies used at that time that are not later used on re-edit? I might post > this note on the devs on their github project) > > Thanks again for your inputs! > Cheers, > T. > > >> On Wed, Aug 19, 2020 at 12:45 AM <marc.ca...@gmail.com> wrote: >> Thierry, >> >> >> >> I am a newbie since July. >> >> >> >> FYI my current dt 3.2.1 response time appreciation is as follows. >> >> >> >> I upgraded from dt 3.0.2 to dt 3.2.1 under Windows 10. I only see degrading >> response time, also on the module sliders, when zooming out on an already >> edited image with a large module stack with a few masks and denoise >> (profiled) activated (sometimes more than 1 instance). On the contrary, >> exporting such an image happens in only a bit more time than a fit-to-screen >> image change on the GUI after a module slider change. I consider this as >> ‘normal’ behaviour. My laptop is an high-end (kind of) gaming laptop with a >> discrete GPU and a (color accurate) 4K display. >> >> >> >> Marc. >> >> >> >> Van: Thierry Rakotoarivelo <tr.d...@gmail.com> >> Verzonden: dinsdag 18 augustus 2020 10:05 >> Aan: darktable-user@lists.darktable.org >> Onderwerp: [darktable-user] v.3.2.1 slow when re-editing a photo (Win10) >> >> >> >> Hi all, >> >> >> >> I have been running Darktable on Windows10 for a couple of years now, and >> very happy with it, thanks a lot to the DT team for all the work in >> developing and maintaining this software! >> >> I upgraded to v 3.2.1 (from v. 3.0) last week. I had no issue with loading >> new photos and making adjustments to them in the Darkroom mode. However I >> ran into an issue when I close the software once I am done with my editing >> and then re-start it to re-edit the same photo. >> >> >> >> So when I start such a new session of DT and try to re-edit a photo that I >> edited earlier, every interactions with any modules is really really slow, >> e.g. moving the sliders take many seconds to update on the UI control (>10 >> s) and then many more seconds to actually refresh the preview (>> 10 s). >> This is independent of the image having a history stack of a couple of steps >> or +10 steps. Also in the same session, if I open and edit a freshly new >> photo that I have not yet edited before, this problem does not happen, i.e. >> for the new photo the UI and Preview are responding at a "normal" speed. >> Thus this seems to happen only on photos that were edited in a previous >> session. >> >> >> >> Not sure if it is relevant here, but please note that I also have "Write in >> XMP sidecar" option enabled. >> >> >> >> Any help on solving that slowness issue with v 3.2.1 when re-opening a >> previously edited photo would be great! Right now I downgraded to the >> previous v 3.0. Thanks! >> >> >> >> Cheers, >> >> Terry. >> >> >> ____________________________________________________________________________ >> darktable user mailing list to unsubscribe send a mail to >> darktable-user+unsubscr...@lists.darktable.org >> = ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
