Problem With Macro Modulations, Causing Conflict On Messages [SOLVED]

[Natan]

I just installed Vocal rider, And Can confirm this Happens With Waves Too.

Ableton?
-NOT MY BUSINESS!

[DabDab]

@Natan Don't get me wrong. I was just having fun. It was a Joke.
I can understand what you are facing right now. Hope you don't mind. :)
Cheers !!

[Natan]

@DabDab All good Bro.

[DanH]

@Natan oh cheers man, that's good to know! Nice work finding out :)

[Natan]

@DanH Cheers Mate, This was Somewhere on my Mind, To Check, and Yeah
This is Happens Commonly On All SelfAutomating Plugins,

Is This A Bug?
Well, Christoph Can Bring Some Light On This Situation.

And here is my Try With vocal Rider

Pay Attention To Big rider Knob, and Ableton's Automation On Down left-hand side.

It moves, and On edit > Undo History, always It shows The Rider.
I made a dummy midi clip, and Deleted It, and tried to Undo, And Ctrl + Z Like Ten Time, does Nothing ( Look at Edit On Top, when it Blinks )

[Natan]

On Vocal Rider, If You Select Off, The Knob Still Moves, But It won't Send Automation Messages,
I Think It is Exactly what Should be Available on Macro Modulation,

So Once you selecting A Destination, On FrontEnd Macro Panel, The new Paramers shows Up, with A Default Value Of OFF, So no need To go and Setting it To OFF, and Things Stay Fine On the Ableton side.

[Natan]

Something like This:
Just A Button, A Gate, Between The Destination and Automation

Not sure, but it may Help to reduce Messages Thread aswell.

[DanH]

Coming back to this as Logic, like Ableton (and others most likely), now records all knob movement in it's undo history and using a macro modulator to control a knob on your UI will send continuous messages and populate the entire undo history in DAWs rendering Undo pretty useless!

Is there any way to make macro modulation not broadcast it's outgoing info?

[Natan]

@Christoph-Hart Hey Legend, Is this fixed?
How is it supposed to work?!
any Lines?

- fix plugin parameter modulation messing up DAW undo history

[Christoph Hart]

@Natan yes that is fixed. You don't have to do anything on your end - if a macro modulation source changes a parameter that is automated during its render callback, it will skip the DAW notification call that gets written in the undo history.