yurki

When I use pattrstorage in parameter mode to save some live.dial's, I noticed the following:

- when I change presets using a preset object as a gui, all changes occur fast and

- when I use another a live.numbox to change the active preset and I change the preset

with an envelope in Live. Then all live.dial's go one by one to the new value,

each taking it's own undo. This is also much slower and, with many parameters

controlled by a pattrstorage, give me audio glitches in Ableton as well.

Does anybody know why this is or how to solve this?

- when I change presets using a preset object as a gui, all  changes occur fast and
only take one Live undo.
- when I use another a live.numbox to change the active preset and I change the preset
with an envelope in Live. Then all live.dial's go one by one to the new value,
each taking it's own undo. This is also much slower and, with many parameters
controlled by a pattrstorage, give me audio glitches in Ableton as well.

controlling-pattrstorage-with-a-parameter

To answer my own question after some research. (maybe it's useful for someone in the future)

This behaviour occurs in max6, in max7 recalling pattr presets within the gui also puts every parameter change separatly in the undo.

To have both the power of automation and pattr presets, I found the following solution:

I connect all parameter objects to a separete max numberbox and these I control with pattr.

I connect the numberboxes back to the parameter object with a [set $1] message.

Every change I make in the gui with the max numberboxes are saved to a secret preset on a -mouse up- and pattr presets are stored within the Live set because pattr is in parameter mode.

The limitation is that as soon as you recall a preset, the max numberboxes in your gui are not in sync with the parameters in Live.

I also noticed that the old classic GRM plugins wanted the same thing: presets and automation. And guess what: they solved it the same way with the same limitation and I used it as an inspiration.

1. pattr interpolation still flooded the Live Undo. I have no idea why and it seems like a max bug to me. I solved it with a deferlow.

2. mapping parameters to a midi controller will not save the changes you made with the midi controller in the Live set because it's the secret pattr preset that's loaded and not the parameter data it self.

I think I can solve this by checking A a change in the parameters B midi cc coming in. if both are true, I save to the secret preset with a speedlim,

I connect all parameter objects to a separete max numberbox and these I control with pattr.
I connect the numberboxes back to the parameter object with a [set $1] message.
Every change I make in the gui with the max numberboxes are saved to a secret preset on a -mouse up- and pattr presets are stored within the Live set because pattr is in parameter mode.

The limitation is that as soon as you recall a preset, the max numberboxes in your gui are not in sync with the parameters in Live.
I's a limitation I can live with.
I also noticed that the old classic GRM plugins wanted the same thing: presets and automation. And guess what: they solved it the same way with the same limitation and I used it as an inspiration.

Two problems occured still:
1. pattr interpolation still flooded the Live Undo. I have no idea why and it seems like a max bug to me. I solved it with a deferlow.

2. mapping parameters to a midi controller will not save the changes you made with the midi controller in the Live set because it's the secret pattr preset that's loaded and not the parameter data it self.
I think I can solve this by checking A a change in the parameters B midi cc coming in. if both are true, I save to the secret preset with a speedlim,
maybe at 1000ms.
But I have to test this still.


I know we can't turn off the Live undo system and I know this feature is not gonna happen any time

soon. But a way to make the Live set dirty and have the possibility to save some stuff in your device at the moment the user did a save in Live, just before the rest of the set is saved would be great. Just an idea :).

A feature request came up to me:
I know we can't turn off the Live undo system and I know this feature is not gonna happen any time
soon. But a way to make the Live set dirty and have the possibility to save some stuff in your device at the moment the user did a save in Live, just before the rest of the set is saved would be great. Just an idea :).


controlling pattrstorage with a parameter