Prevent Plug-In broadcasting Undo info to DAW

[DanH]

Does anyone know how to prevent a Hise plugin from creating data in a DAW's undo history? Maybe something in the source code / Juce codebase...

If you change a knob's value, for example, it will create a string of Undo info.

Similarly if I use a macro to control a knob on the UI it creates continuous Undo info to the DAW.

This makes it really unnatural to use the DAW as often users will use the Undo function for arrangements etc - not really for undoing a UI setting o a specific plugin.

Thanks!

PS - also 'touch' automation mode not working in Logic... will test other DAWs. It creates an automation lane on the right automation channel but doesn't record any automation info...

[d.healey]

@DanH Which DAWs? Do you have a screenshot of the undo history?

PS - also 'touch' automation mode not working in Logic... will test other DAWs. It creates an automation lane on the right automation channel but doesn't record any automation info...

Did you enable the isPluginParameter property?

[DanH]

@d-healey yup - as you can see it's continuous and overwhelming.

All knobs I want for automation correctly set up and labelled etc.

[Christoph Hart]

When you have a plugin parameter it might be stored in the undo history of a DAW so if you don‘t want that, don‘t make it a plugin parameter, otherwise there‘s no option…

[DanH]

@Christoph-Hart really? Nothing that can be tweaked even in Juce?

[Lindon]

@DanH if you think about it - the DAW saves the state of the plugin - for next time you open it, so the DAW needs to know the state of params you want it to save, and when you change a param value it will need to save that value...

[Christoph Hart]

It has nothing to do with JUCE but it shouldn‘t be a problem. Why is it a problem?

[DanH]

@Christoph-Hart because if you're using macros with modulation it completely takes over the undo list in your daw.

So when you're editing your arrange or notes or whatever and you want to undo an action, you can't because there's hundreds of undo data points created by the macro controlling a ui knob, and it just carries on creating more and more until the macro connection is removed.

Even if you slowly move a knob you get a long list of undo points. I'm not sure how helpful even that is.

Would be great to be able to disable this somehow but sounds unlikely...

[lalalandsynth]

@d-healey I dont think touch automation works right in any DAW for me , the resulting automation is a jagged , jittery curve. Unless I am doing something wrong ?

[Dan Korneff]

@lalalandsynth same here. I always draw in my automation when mixing so it never bothered me, but a lot of my users like to use touch automation with poor results

[A Former User]

oh dear i have parameter/macro modulation as well

[clevername27]

@iamlamprey I'm wondering if a solution here is to do it manually, instead of through the Properties editor. In the widget callback, start a timer (i.e., when a user begins turning a a knob). In the time slice, check to see when the user stopped turning the knob. Then, manually report the start and end state for the undo history.

[Christoph Hart]

Yeah that‘s a valid point. I‘ll try to skip the Daw parameter notification for modulated parameters.

[DanH]

@Christoph-Hart

[DanH]

@Christoph-Hart Did you have a go at this yet? Couldn't see anything in the latest commit...

[DanH]

@Christoph-Hart Just checking if this is still on your radar or not? :)

[Christoph Hart]

@DanH Ah sorry, that slipped through the cracks. I've fixed it (it now deactivates the plugin parameter notification as soon as a knob is automated by either a macro modulation source or assigned to a MIDI controller).

As soon as Github is online again, I'll push it LOL

GitHub Status

Welcome to GitHub's home for real-time and historical data on system performance.

(www.githubstatus.com)

[DanH]

@Christoph-Hart oh dear!!

Thanks very much, hugely appreciated :)