Issue? Ableton LFO modulating Max Devices triggers automation lane and overflows Undo Cache

[auxxtone]

Hi everyone,

im facing two issues in Live 12 on a PC when using an Ableton LFO to modulate parameters of Max devices,, not M4L devices:

• 1.) Automation Lane Triggered: The parameters are written to the automation lane, especially with free-running, non-cyclic LFOs, making it static and ruining the effect.
  This doesn’t happen with Ableton-native parameters (e.g., Track Volume) or VSTs.
  
  2.) Undo Cache Overflow: The Max modulations flood the undo cache, even without record mode, making Ctrl+Z unusable.

Is there a way to configure this behavior of Max devices to avoid triggering the automation lane and affecting the undo cache? Ideally, Max parameters would behave like VST or Ableton-native parameters.

I see those things as independent: manually changed parameters that get recorded, controller-driven parameters that get recorded, drawn automation curves, and LFOs modulated parameters that should run freely and independently without being recorded. This could apply to all devices or parameters.

[auxxtone]

Nobody?

This might sound a bit silly, and I'm not sure if I explained the problem clearly enough, but I'm certain this is a real issue.

[S4racen]

"Is there a way to configure this behavior of Max devices to avoid triggering the automation lane and affecting the undo cache? Ideally, Max parameters would behave like VST or Ableton-native parameters."

Not really, they are either automatable or they aren't with automation comes the write to undo history.

Perhaps give some examples of the devices you mean, your post is a little vague in that regard.

Cheers
D

[chapelier fou]

To clarify, LFO is not the culprit here.
Pollution of automation and undo history is usually caused by how the device is coded.