Bug(s) in MDynamicsEQ undo and improvement suggestion for undo

[MacGyver]

Hi there,

there is a bug in MDynamicsEQ undo: If you change the slope of the Band-Shelf A or B filter, this change won't be saved in the undo history. If you then undo, the previous change will be undo-ed instead. So it can mess up the history.

I also would like to suggest to improve the undo steps handling:

1. If you actually would filter away each next step of the same control, the undo would be much more reliable, in my opinion. For example: If you start to edit the gain of band 2, doing multiple changes, currently the undo history is filled without various steps. Instead the undo could simply jump to the first value the gain of band 2 had when you started to change it. Same filtering when you then change another control: The steps of the previous changed control then to be filtered. Have a look into Renoise's undo. It is pretty smart here.

2. A status message and/or a highlight blinking of the control you are undoing. For example something tiny will be undo-ed after 5 undos, and you can't really see what was undo-ed now, and you don't even know how many changes in the undo are saved for each change (currently this feels kind of random).

I think these changes could highly improve the undo UX.


Btw. I also find kind of strange how the opening of a band detail page works: If you still have a band selected from the last edit, and then open the plugin again and right click the already selected band to open the detail page, nothing will happen. Then you have to select another band first and reselect the wanted band, or first left click/disable and reenable it first. Maybe a bug, too?

Have a good day!

[MeldaProduction]

Hi, actually things like that cannot be undone - only automatable/modulatable parameters are noted. In the rather supercomplex ecosystem of thousands of parameters in each plugin this is just a needed compromise I'm afraid. Most parameters are automatable/modulatable though.

As for the other thing - I'll check, but please tell me exactly your OS and DAW.

[Tearing Riots]

The undo is not working well across your plugins. MSF is very tempting but I'm not up for using such a complex software while figuring out what the undo can't do.
Main point of concern is that imo undo should never destroy any data entered.

[MacGyver]

Hi, actually things like that cannot be undone - only automatable/modulatable parameters are noted. In the rather supercomplex ecosystem of thousands of parameters in each plugin this is just a needed compromise I'm afraid. Most parameters are automatable/modulatable though.

As for the other thing - I'll check, but please tell me exactly your OS and DAW.

I use macos 10.13.6 and Bitwig 2.5. I meant the undo system within the melda plugins, and not the daw's undo.

If you move a band in the melda eq, it will fill up the melda undo history with kind of random snapshots. If it was only one single undo to the point you started to change that band (only updating last step as long as you did not switch the band/control), I think it would be much more easy to understand. Also then, not much would be lost.

IMO the slope change should be refected in the melda undo in any case.

[MeldaProduction]

Sorry, but the slope and some other parameters just cannot be undone and won't be, long technical story. You know it's easy for most plugins out there, which just a few parameters and that's it... Here, not so much.

Anyways it works like this - whenever you touch something, it stores the undo state, then you keep moving it, and once you stop moving it for some time, it resets the state thinking that "time for next undo when he starts moving something again".