Writing presets of two pattrstorage contents into one file?
Hello and please,
does anybody know of some way, how to save union of two [pattrstorage] objects into one file + to be able to refresh them both from the one file?
Why i need this: in my patch, there are two pattrstorage objects on the same level (using the subscriptionmode 1). One pattrstorage is full of presets (i use store 1-16 there) and another one is for things like SOLO/MUTE, which you want to save with the file, but you don’t want these influenced when you switch (recall) patterns.
I was hoping, that doing it this way would work, If i’ll put another pattrstorage in a parent and set it to GREEDY. I tried that, but it doesn’t work (shown in attached compressed patch). The greedy pattrstorage can see the other two pattrstorage objects and all the pattr objects, but as I’m sending the "store " messages only to the two non-greedy pattrstorages, it seems to be saved only in them and the greedy pattrstorage does write only "empty" XML files (the file has xml structure, but no data in it).
Or even other ways of saving some preset-independent data with pattr-presets together in a single file are welcome…
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 1347.3oc4ZszbihCD9LSUy+AJN6MER7vN6oYOr+ClCaUYlxk.TrUBHn.4LN6 T6+8UO3gDFhIdhMNSNXSYIQqVe8mZ0sb+yO+IKmn783JG6+z9NaKqexawR1l nEqlFrbxP6iSQUxA5DmmkgoLmE0cxv6YxN9QIggqr+lCNqf872br2mk1NJ5t r7crTLSJD2lluOmxpH+KVzH.dSa6EHV7VBcy5RbLSoeP2U79sgAxG.HP9K2a bs+ttznnLozb9qRBxX9IzloGzzJIQNz7nG9ikNx19uO+IwS9iESFQxvUUnM3 QPjwQAvwPA0XYOWfUPfiS2ZcHDxSgPKkOB7k3zpSAffC.P9mN.Qw+fKg1o5I TYqRjfiHoD1yGBdE1U6hjqx2PRjGLThJdAhGg2d5bH2AfHniwTiKqAkFTgKc RJ9IbYEImpy.rbPEEZsao+RBv7gborBWz0FgpZysqsR7SjFQDT2pvP0LIc3v JeW4RGHIIgpe4uRGI3V0Mo4wOhSLlEm7BLkPKJwUbu.HV8z00eB9dztT15Qr JlC3dTLd7WeX6fkylRRRNUnHluqn8lo7NafzFK9VaMIGBEULzqWwWN6phPkB TLJEquSfSLyySM6qy5w4+HJICwvLhRkgtcxkjUTRnLyICSQbwrsJtLOM0TZp tdZntR3V3X7OHIrsRwY.q7WfTzXPb5fqDxFbEqWiLzlpdMYbXfACTeGtYG81 oGsiw3y+Bs9G1m2v92hPzMc93FaSLvK7l.wIAM6d6sGdbG9GrgE5z1Qsisl8 LmLDX5ryzmVZNJQtFmH.M1dneAvaoB0T9+FA6dg8dSGZce6g1dGzZhs7kHJM 0FdVv1iiqA0taTGv3e6AG99pQV3HHKHXdPVv7hr25c1A1vKLvVwxKwyFiEFD pgqKOi3p+rfqyEeErZ4EBW8tz35tHQLFQX6GejQnn4h454C5PXfq2YDhAyLD OWj3vvKEBeFhSfOwQ7juzmQ8bNUceG36u.1BOYrUDo+hoFMlG+rMdnr9tR2D AiDOVApjq6Lb4ZUpAlo88FEv1pYxNL+FAwcIckXDBuH4inaDFxSd2cvfXrxI 3r26z8Dsn9ywCWQcrpmuPj1KCOeot3a7JkXY3D0TEef47UgdBmrl+Vb8bs.s H7TfUYQacnkYDVT2.zL5WVB.33D.vLS.TGFcAr+dia+88+cy7mrqL+Er8h0N OXEawvr+RazIY4IyW.10g+AquCS2aOi2hgwqzt7qU0FGi+ZbhZHV+NZBC4GG 4KtMAnfx6BMlgieVjkSbJASYZxzWIQufUbwtjKvYk0khhmBqSLrqEVmJh3VR 2xyGoybEh1Ib+z5CRBc2n8mJ8BLSvuuLSsqzOkPG8Zqk1Qw.FgyVkuqLtAzp 88a26H9DN3yAylKV+tlH0VX2y1ukjjz6+TPc86UBjHwzW+Q2n8pUc+op5qt5 TcdZ1GnRCq6vqOc2cp5N35S289Hn6WgbF+2w3t+6XbO3ifteExYB+Hn6WebF 3zOax88rxe8wZfv2yHOblPdsn5SvEXJWNwOuNFEuEOR.9FYT1KsHdtp4L9he qYctHx1rNwOmu92+yW06fjUjRhIxLS.FJl5GcUS0wRlpqjuNZYNcXuiV6TaR yiPo0UWV6Z+0WpOSoJqlPgbMVEGMfXawuyQUDte+9AJfP8aRfOB6uroDiSdt 6FDN60io5Fqq+WzTEt5aWEq1sL5eEA27PUWQXMYh5qKa+WNS+Imk+gDB0TXl UeMAouirFZxfoBqgxSITiAbaMfKqCTyd0soTi5Wul8qUyCpSSoT4e8+PWjBx e -----------end_max5_patcher-----------
One solution I can think of is moving the preset-dependent pattr objects into a separate subpatch and use loads of [send]/[receive] or [inlet]/[outlet] objects to get the data there and back. Then store/recall only that subpatch when working with presets. Seems do-able, but maybe I’m just missing some facts about the greedy pattrstorage and this can be done simply. hmmm
(and perhaps it’s worth mentioning that the patch is already quite huge, (>800 entries in the pattrstorages together) so the more elegant and tidy solution, the better… (for example, storing/recalling each pattr separately would work, but would be crazy thing to do))
Is there perhaps a way, how to have pattr objects in pattrstorage NOT organizes by patcher/subpatcher hierarchies, but organizes manually into some subgroups which I could then store and recall manually?
(if not, then i’ll probably have to destroy my hierarchy + turn my patch into a mess (putting pattr objects far away from the UI it controls) to be able to recall some UI elements but not others on the same patcher level)
Forums > MaxMSP