gbravetti

In max4live, there is some way to make data stored in a Coll object persistent so each time I'll open that live set, previously stored data collection will be available.

I guess that I can save it to a file then load it each time the live set opens, but I'm looking for something more "embedded".

coll-data-persistent-on-max4live

You could check 'save data with patcher' in the coll inspector. Then data will be persistent with the device, BUT only if stored/changed while the device is in EDIT mode.

Got it!, I think I'll use a file instead.

Another way to do this sort of thing might be to rewrite your code to use dictionaries in parameter mode

Andrew, I'm not familiarised with the use of dictionaries in parameter mode.

Andrew, I'm not familiarised with the use of dictionaries in parameter mode.
Do you have any example to look at?


that will solve my umenu editing and persistence issues nicely (once I get home and work up the umenu dump to dictionary to umenu..note bidirectional). I had code to do this umenu stuff with colls in Max4, but lack of persistence in Live had me drop the effort...dictionaries being parameter mode compliant: that rocks. I should read the docs more often, or closer, eh, ;-)....

Thanks Andrew,
that will solve my umenu editing and persistence issues nicely  (once I get home and work up the umenu dump to  dictionary to umenu..note bidirectional). I had code to do this umenu stuff with colls in Max4, but lack of persistence in Live had me drop the effort...dictionaries being parameter mode compliant: that rocks. I should read the docs more often, or closer, eh, ;-)....


Coll data persistent on max4live