tone equilizer drawn mask - bug?

If I use a drawn mask in the tone equalizer, e.g., an ellipse, and then hide (deselect) the mask, the mouse selection (the circle that displays the tone value) remains black and can no longer be changed with the mouse wheel.

DT: 5.3.0+901~gbaff9166fd
CachyOS x86_64
Linux 6.17.8-2-cachyos


I cant replicate this problem on windows DT 5.3 +887. All working fine for me.

1 Like

I can reproduce on Fedora 42, DT built from latest sources.

5 Likes

I can also reproduce on 5.4.0 (on Arch Linux).

Update: I think I found a workaround. Go to Tone Equalizer, click on Drawn Mask, draw the mask and then display it. The Mask Opacity will be set to 0%, so adjust that.

Next, click on the pencil to disable the mask, then click again to enable it. Now all adjustments will work properly and affect only the masked area.

Is this worth a bug report? Can anyone else reproduce the issue on 5.4?

I see this also happening with DT 5.4.0 on KUbuntu.

Looking at your screenshot it appeared to me that you were hiding the mask by clicking on the arrow and dotted line icon. If that is the case the mask remains and it is only the masks editing elements that get hidden. Therefore I don’t see a bug here but intended behaviour. Apologies if I have interpreted your screen shot wrong.

I still think there is a minor UI issue here. Try this:

  • Activate tone equalizer, advanced tab.
  • Add a drawn mask to the image.
  • Click on the arrow with the dotted line icon to disable mask editing.
  • Hover over the image. You’ll see the usual mouse exposure tool, but with label “?EV”. Turning the mouse wheel has no effect.
  • On the tone equalizer graph, move one of the curve nodes.
  • Now go back to the image. You’ll see that the EV label now is correct and the mouse wheel is active again.

It looks to me like, after adding and hiding a mask, mouse control is not fully returned to the TE module. Certain actions, like moving a curve node, fix this problem.

4 Likes

Yes I can confirm this behaviour. This last post by you makes the issue clear to understand. Hopefully one of the developers can comment on this issue, but at least you have a work around in place.