Thanks Ulrich for this explanation.
This clarifies and I see now two clearer issues:
* 1 this message is unclear and conveys a more alarming message than needed.
* 2 the user does not know that changing anything triggers a re-render
without any bad consequence
* 3 changing anything feels like a workaround. The user should have an
option to just re-render.
I see two ways to fix these issues :
* I guess the developers have considered fixing the issue (increasing
the timeout ? Retrying the computation ?) and not done it for good reasons.
* A simpler way:changing the wording. Perhaps something like: "Rendering
timed out. You can continue adjusting parameters or [Retry]." with
[Retry] being a clickable button that just requests another render
without actually changing any parameter. This way, the user is not
needlessly alarmed (fixing issue 1) and know they can just continue
adjusting
I might be stating the obvious, or not, since choosing good words
(towards a user that is not a developer) is not that obvious and
sometimes overlooked.
In case it's useful I'm happy to add my two cents.
Cheers !
-- Stéphane
Le 09/12/2018 à 19.46, Ulrich Pegelow a écrit :
Am 09.12.18 um 08:59 schrieb Stéphane Gourichon:
My guess is a memory corruption error in some part of darktable. Of
course it would be nice if somehow could trace this. (I'm willing to,
but currently not using darktable much, and quite busy with other
projects.)
Well, no. The error message appears when darktable is not able to
synchronize the two pixelpipes in darkroom mode: the preview one for
the navigation window and the "full" one for the center view. Both
pixelpipes normally run asynchronously as separate processes. Some of
darktable's modules require a synchronization: the full pixelpipe
needs to wait at certain points until the preview pixelpipe produces
the needed data. Without that missing data the module in the full
pixelpipe would produce wrong results, the output of the two
pixelpipes would no longer be consistent.
In some cases synchronization fails, e.g. when the full pixelpipes
needs to wait too long and a pre-defined timeout value is exceeded
(config variable pixelpipe_synchronization_timeout). If that happens
the above warning message is displayed. However, this is of no big
concern. Typically with the next processing step all is good again.
Any zooming in or out, panning, (de-)activating of modules or any
value change is sufficient.
Ulrich
--
Stéphane Gourichon
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
