kparagraphic

I've been using max for a number of years now and have switched to max4live. (I'm on max 6 as my ableton is still a little old.) So my first instinct is to go through my patches and turn them into devices. I don't want to replace all my dials and sliders with the live ones, but I cannot get the values of the normal knobs and sliders to save with the ableton session. I've gone into inspector and set everything up, named parameters, put the right values in etc. Live has no problem finding each param for automation but forgets all data whenever a new session is loaded (even the preset object forgets anything you save). So, I understand you need to use pattr, pattrstorage and a manner of similar items. I understand you need to set them up as parameters. I have followed everything on this page with no luck.

https://cycling74.com/tutorials/max-for-live-tutorial-adding-pattr-presets-to-your-live-session

The only time I got something to work was to have a metronome saving a preset to pattrstorage every 5 seconds or so but this is just a cheap workaround until I find the proper way of doing things.

So, I'm positive there is something obvious I am missing. With that in mind, can someone please simplify and clarify exactly what one needs to do to get the value of sliders, numboxes and dials to save with the session? What are the fundamental processed behind this idea? I've had a lot of difficulty finding clear answers on this. And my second question, why is it not enough to just tick param mode enable and then be done with it? Is this to do with the way max is coded or something?

Apologies if this is a painfully obvious issue that has been asked previously but I just decided to give up and make a thread about it after a few days of trying to figure it out. Thanks for your help!

Hello there,
I've been using max for a number of years now and have switched to max4live. (I'm on max 6 as my ableton is still a little old.) So my first instinct is to go through my patches and turn them into devices. I don't want to replace all my dials and sliders with the live ones, but I cannot get the values of the normal knobs and sliders to save with the ableton session. I've gone into inspector and set everything up, named parameters, put the right values in etc. Live has no problem finding each param for automation but forgets all data whenever a new session is loaded (even the preset object forgets anything you save). So, I understand you need to use pattr, pattrstorage and a manner of similar items. I understand you need to set them up as parameters. I have followed everything on this page with no luck.
https://cycling74.com/tutorials/max-for-live-tutorial-adding-pattr-presets-to-your-live-session

So, I'm positive there is something obvious I am missing. With that in mind, can someone please simplify and clarify exactly what one needs to do to get the value of sliders, numboxes and dials to save with the session? What are the fundamental processed behind this idea? I've had a lot of difficulty finding clear answers on this. And my second question, why is it not enough to just tick param mode enable and then be done with it? Is this to do with the way max is coded or something? 

Apologies if this is a painfully obvious issue that has been asked previously but I just decided to give up and make a thread about it after a few days of trying to figure it out. Thanks for your help!


not-using-live-dial-and-live-slider

There's only one way to use Live's mechanism of storage, recalling and automating parameters: the live dot objects.

Of course you're free to use your own system (or the classic Max pattrstorage way) but you won't be able to use that in combination

with Live's preset browser, automation, Undo, etc. etc.

There's only one way to use Live's mechanism of  storage, recalling and automating parameters: the live dot objects.
Of course you're free to use your own system (or the classic Max pattrstorage way) but you won't be able to use that in combination
with Live's preset browser, automation, Undo, etc. etc. 

thanks Christian, if anyone else is confused about this in the future, I've made this clipping that you can paste in and it should automatically find and save all the params for you.

If you're never modifying the autorestore or the outputmode attributes, your patch would be even more compact and reliable if you set the attributes as arguments to the pattrstorage/autopattr externals (e.g. "autopattr mypatch @autorestore 1")....

NOT using live.dial and live.slider