Max 4 Live and Coll - Can be populated and saved as a live preset?
Hello,
I have been trying to implement the patch below into the max for live environment. The problem I have is that I can populate a coll in the max edit view but not through the Max 4 Live Ableton view. I know there are a couple of threads about this, but no one seems to get to the bottom of it? I want to drag files to the GUI and have them auto saved like in the patch, save an Ableton preset and have the info there when I open the instrument again.
Any help very much appreciated.
Hi . Coll wont be stored with pattr/preset type of scenario . you could embed Coll to the patcher but it will be stored within a file only , not the live project .
Uve got two options . Look at Dict object . Coll communicates with Dict back and forth . Then u can pattrize your Dict within the instance .
Im encouraging u to use plain Dict solution , so u stay consistent and there is no unnecessary dataflow involved .
Yes! The dict option works. However for some reason the preset object retain its stored values, when I save a new iteration in Ableton and re-open it, the dict has saved the data but the preset object is blank?
yeah . look at the preset help file -> pattrstorage tab !!!
I did and it still didn't work, it's more complicated than that in M4L. I found an online tutorial that explains step by step... https://cycling74.com/tutorials/max-for-live-tutorial-adding-pattr-presets-to-your-live-session/ and even then I had to return to the pattrstorage helpfile to look at the M4L tab.
really ? i havent dealt with preset in m4l yet . it was my guess . i will keep your link for the reference though . thanks !
In m4l an embedded coll does seem to get saved with the set, since projects are frozen into one file rather than the.. linking? that happens in full max. I'll try to get your auto populate to work here in a little bit and post back. Are colls really unpattrable though? I would intuit that its just an array, when a dict has some sort of mark up? huh. - In the meantime try this and see if the added pattrstorage fixes it. You could probably use the pattrstorage msgs to replace the counter too since I think there is a storenext.
No worries, DO...WHILE it's just another example of the tiny annoying differences between Max and M4L. Your patch is great but actually when I imported it into M4L I can't search the dictionary using (get $1), you have to search using (get "$1") so I had to figure out how to formulate that message with no spaces between the quatation marks and $1...faff!!!
Its true for max lower than 7 . In 7th we dont need to worry about index as symbols anymore . sorry i didnt ask u . And your mentioned differences worries me a bit now :/
hi,
I'll be looking to something like this soon. If I want to store some values - eg for a lookup table, in M4L, should I be looking at coll, or dict or something else?
Hi Venetian, This is the M4L patch that is the culmination of the dialogue from this thread, - hopefully it's of some use to you?