Error in section retouch module in darktable's manual (3.0 & draft 3.4)

Software darktable
1

There is an error in darktable manual about retouch module, both in version 3.0 and in draft 3.4.

From manual 3.0

The top slider adjusts the merge scale feature. This setting allows to apply a common edit on multiple consecutive scales within a group starting from the highest scale (not including the residual image) down to the one selected by this slider. If the slider is set to 3 and the maximum scale is 5 then all edits that are added to scale 5 will be applied to scales 3 to 5. Edits added to scale 4 will be applied to scales 3 and 4, and edits added to scale 3 will be applied only to scale 3.

From draft for 3.4 manual

merge from
[ā€¦] edit to be applied to multiple consecutive scales [ā€¦] starting from the coarsest scale [ā€¦] down to the scale selected. [the example is the same of 3.0]

Now, in 3.2 (sorry for the very bad English):

For scale more fine that ā€œmerge fromā€ value, the edit is applied only to edited scale.
For scale equal or more coarse that ā€œmerge fromā€ value the edit is applied from edited scale up to the coarsest scale.
For example, if ā€œmerge fromā€ is set to 3 and the maximum scale is 5 then all edits that are added to scale 5 will be applied only to scale to 5. Edits added to scale 4 will be applied to scales 4 and 5, and edits added to scale 3 will be applied from scale 3 to scale 5.
(see screenshots below: cloned the eye on level 4, it is visible on level 4 and 5, not in 3).

level3

level4

level5

1 Like
2

Iā€™m not sure the wavelet visualisation tool is the best way to see this effect properly (I donā€™t know if itā€™s supposed to include the merging or not). What happens if you compare snapshots of the actual image with the various settings (i.e with the visualisation tool switched off)?

For me it looks like it works the way the manual says it does but I might be missing something in what youā€™re trying to show.

Edit: In fact, moving the ā€˜merge fromā€™ slider seems to change the wavelet visualisation even if there are no changes to any detail layer, so I wouldnā€™t use it for any more than what itā€™s designed for - visualising the detail on adjustments to a single layer.