Hi, how would I go about organising pattrstorage so that I could have some global setup data that is stored once in the patch and then have a number of presets for the variable part of the data?

is there someway to partition into levels or spaces so that I only get 1 copy of certain data, and x copies of other stuff?

pattrstorage-setup-question

If you need to have two independant sets of presets you need two [pattrstorage]. You can potentially have one calling the other.

Ya, what musinou suggested. In max itself, I would just use a pattrstorage for every group you would want to change individually, then link them all together with a pattrstorage @greedy 1. In max for live, if I wanted one patch to control storing/recalling the presets of every m4l device on every track, I would use a global receive object that feeds into a route then pattrstorage embedded in every device. (E.g. pattrstorage midi effect sending "all recall 1" or "specific_m4l_device recall 1"). Good luck

Ya, what musinou suggested.   In max itself, I would just use a pattrstorage for every group you would want to change individually, then link them all together with a pattrstorage @greedy 1.  In max for live, if I wanted one patch to control storing/recalling the presets of every m4l device on every track, I would use a global receive object that feeds into a route then pattrstorage embedded in every device.  (E.g.  pattrstorage midi effect sending "all recall 1" or "specific_m4l_device recall 1").  Good luck


pattrstorage setup question