Multiple pattrstorage objects in a patcher
I am trying to save different groups of patcher states to different xml files using multiple instances of pattrstorage.
Eg, I want the settings of my midi routing in one xml, my tuning chart (when it is complete… argh) in one xml, and my synth settings (filters, levels, waveforms etc) in one xml.
Is there an easy way of doing this? For example pointing a certain pattr or autopattr to a certain pattrstorage, and to that pattrstorage only?
I seem to be getting problems when using "subscribe" or "active", the fundamental issue being that one pattrstorage seems to be the master and storing all of my pattrs values, while other instances of pattrstorage don’t store a thing, no matter how much I subscribe or activate.
Any help much appreciated.
you *could* have all of your different controls in differing subpatchers and expose them with pattrhub.
you could also have a separate pstore for each of those subpatchers.
if you want to go the subscribe/activate route you need to make sure that you’re writing to slots where it’s undesirable, and that you’re not recalling on the wrong state, so all in all that seems more clunky. doesn’t mean it’s not possible.
hope this helps,
Thanks for the reply!
> you *could* have all of your different controls in differing subpatchers and expose them with pattrhub.
I am not sure if I get the method described above: Would that enable me to route my controls via a certain pattrhub in a subpatch, to a certain pstore in the main patch? What kind of attribute do I use in pattrhub or pattrstorage to make this happen?
> you could also have a separate pstore for each of those subpatchers.
This is what I am leading towards, but still it seems like an awkward solution. I would much prefer to lay out my patch as practical as possible when it comes to signal flow, and not subpatching it just to get pattrstorage to work for me.
Still the question of master "pattrstorage" and "slave" pattrstorage puzzles me. How do I change this behaviour?
So I made a proof of concept in a separate patch that actually worked. It seems as if my working synth patch got some erratic behaviour with the pattrstorage objects, that needs to be taken care of.
Anyway, in the patch below (proof of concept) there is one thing that still bugs me. The pattrstorage furthest to the right is NOT set to subsrcribemode, which normally would let it see all the pattr objects, BUT it sees none! Why? It feels lika a slave – master relationship vs the other pattrstorage objects. How do I manipulate this behaviour? Is there a way to make it see all?
----------begin_max5_patcher---------- 1796.3ocyassbihCD8YxWAk2G1WxLE5B218gs1+hspYlJE1nDqYvfKPNYtTy +9JjDfvV3fu.hGhADBQyoa08Qcq7qGbVst36jpUt+k6mbcb90CNNhlpavQcs ypcIeeSVRknaq1TraGIms5Q48XjuyDs+Yd2pXjxOu5Q20GXtus8G+SSmnoht Tr9qe.hZZL+vNZdFgIFVPWiEGXMs5oZceIoh+NSXzh7mJIaXRANB3+QuGcgg n5Cdpeb+h5odtHmUQ+IQL9vO1NXIrMao4uL3.A7ECE73wJOYmXrV8ukzjrU0 232O7P8OONRraGopJ4ExIXW0g0UaJoqI6JRIt.SvFzHrAMBafyCa.uHwmavH fMuVXSN9rermHGkUqZeBCHZ+2QTn.WCle.0kiLqIk.0Qn53SnmvMOTFMmro3 PNSGP0fdP78C5iCipQhXvTh7wwcuC.FHsrsjsrmAaY.5J.z6C1.fgZyvmeyR VQIu82n4oEuY.Y7sHvfk97DPR3bCLaxn7YKChKA1FW.QPg2rnIBWxIuw+Na9 JeMorcHSxxNAs3BJqTYK4p0AMDCeAQYAmOd4k59Ap73HNDOpPop6Tk7JApdI +w+w4Qz4Lo9BcW2MWg5NUqUP2ov5S+6NQt9cj9DGh3R7S03HkSVQx.xoU43n LH0oHf.O5hwbsOHFw+MD1LjNMSq05MJvW0au.9yA8Cb+hnyB6h6o6DyzEP3a cFy0p+8AhILHnHvOV5HIZ1bj7VIkQLAHHaCH3.wgfYFPNjeLWHWTyIXS.km0 70hE9X88kQnwSjq1gV+BaKmwlKaaIg3p.yJW2cIeieHuvMk97yjRR9FhKM2s mG30jsIuRKNT9na01hCYo4+IiOPjt0+zihIx.693qXQQie4M.jjQnz1KTbA1 llf09vGk0HLxdVih3WgBLCBPydf+SWnRW7eCqhQGzBMBZd2Iqo.IjDHLihht f36hAiTdbr1moYjWIkU7kJooFcVooLfxvIHOwg.rmzDV60xA5WxJ17MRp1Wk ypTxyW3vTrmj28Hd5KTq2p0j8jlquRuie0IGxXOYFY6e+mS1PF7gMBlNqdoj lVjWKD8dx5ladc7OYk2Tc4Vzi7j8FdXVQQ15jxWoUz0YjdZCtcbRNcWBivnR 4A509bzc6KoR2asssivRRSXIRAQSOomwIM6fdyU5094lybx7lCQgddd.rGVu GsycRNvJDdu0uq9hS0a2j2XCygvZ2Y.ssYGPOp8WK.MvzNDPY6Jzn9wezu+7 tyO2SMgRvXTCh0vXmVF0hWGFoOvNsbrE27C9.Ee1NNs8NS5.7ZTt8CO2W20x y2nlqMyhWhpyabptgoqf7BFHmgmKJwrAVng.KnM.KXnu8.KIfLjaiyaaguBz BdkdEp8ixcHrNI+k20oPDV2mvREUGxHzeQipPI2uaBU6h5UuDfplPgpTAbYo jXDTBdOJGbFRqSxTzvZGi1G2HSjqh9xPnyUk9ig4HeHDEJh0GbBG4iiy2y4W vErbK7klL.SA0MYkAUbmkIJ6z.5mgH8QAxarPZR9kb3AcFeMoBSRo8VRE0vU +qJiaF+dE+yeZWmKnoNdvosNd2ZMPwSJLfCBkn.1NnPahWO8CGLs5eY0cfHq 9gar7sdyxGtm+Rs90.qUBmXYInA3HqTxuSS9UasnMASg1BlBj4HDf6cvdUre fbaArVBAiTKzSgL.3DAP73FrhbSe59WQM8N4arGAXi4YHF1U4Fnlmj40eAzV 5YeHvl9KdusHf0bPDChkAWiVh6PfHaCKxryMSaPftJATm0U2TZ0lBCfxMWUI uyQ5HDDIS9f3f+bWXyW3BtzMx95TumQqXl7iXsxYFK8cBhh61GDyZAj9ZxO+ 4425H58PGy.25lG4ZwLkIkZ8aQ3wXRcM6cj6v9AAGfj6viHn+LucP5kxMCoa yDwxKYW2BuvLdXJ0ZFoXpBffLmVs60Dh2AcLt7rkC53gmTz4Zoc.rFcLU4lm XZGCDeMqHIUn4LkDwozM4XooKS3kOz56png1KBA1a+DIMYZVvFDsrXrB8Cs8 bpkHmUdrwIk0JOT7xm0JzGYOaiv4f15E+OtgwznisEJgBv59VPy+9Bu27Gyz 6GZJFFaK98pIeJ98Jiq6H+9IXeeCkD24J76DKewHnWN3FKAAdU2de6gphCka ZP2lstgaGjkRpXz71se1mZ2vBZ8YKMMs2N8Z0NZ59Bte3dkj9DiywJR0+KRs vDIgyg2WllYgp1u9xSnBWfBUMuwklPAVdhznrxEbplSbBt.0cAiPl.f4UlhV fxT3BTl7VdxzBT0sD0biwkY7rJRHzxClP3EnpyeLxT3BTlhVfxTvBTlfKOYB N2rBFkPcDWzom66X7ZdjnO0Bk+haEdAKukAiVdhzn7DftAYhewue3+Yolh9M -----------end_max5_patcher-----------
Personnaly, I tend to put the different parameters I want to control in different bpatchers, with a pattrstorage in each of them.
You could then also have a pattrstorage that manage which preset is on in each bpatcher.
Hope this could help you…
I have been struggling with this problem as well. My MIDI assignments are strewn throughout my patch and I want those MIDI assignment boxes to have a separate preset from the other parameters.
The only thing I’ve thought of is having a bpatch that has all the MIDI assignments in it, and then the MIDI controls are routed to the controls throughout the patch.
Any breakthroughs on your end, Daniel?