Using many pattrstorage objects in the same window
I am having trouble figureing out the do´s and do not´s behind pattrstorage and pattr
It seems it is ok to have many pattrstorage objects if one uses [p ] objects but not in the same window – is it possible to have two pattrstorage objects in the same window – and if so – how do I designate which pattr object belongs to which pattrstorage object
The reason I want to do this is that I want to be able to interpolate two sets of parameters seperatly, and I dont want to put either slider window I am interpolating, because I want to see them both in the same window
P.s – is there any way to make UI objects visible (and inter-actable (if that is a word :) in the main patch, if those UI objects are actually placed within a subpatch/bPatch? (similar to the vizzie objects for example)
All the best
I don’t have Max with me at the moment to check this, but if you double-click the pattrstorage objects I think you get a list of all the objects connected by pattr. There are tick boxes which turn control on/off for each object connected. Will these solve your problems? If you had 8 objects connected, for instance, have 1-4 checked on pattrstorage1 then 5-8 checked on pattrstorage2.
For your UI question, have you looked into Bpatcher? I think it’s just what you need, interface tutorial 1 covers it pretty well. Also bear in mind that you can open patchers inside of Bpatcher in presentation mode, just check the ‘open in presentation’ checkbox in the patcher inspector before you save and load into Bpatcher.
Well the trouble I am having with the checkboxes you mention is that they all show up in one but not the other pattrstorage object
Ill check out the other stuff… thanks
Ah yes, what you need to do is set your pattrstorage objects to subscribe mode in the inspector (1). You then send them messages to add objects individually, so if you connect your pattr to a dial and call it pattr dial2, send the message subscribe dial2
Hope that works,
Thanks – Using the bPatcher also works very well
silly me, didnt realize that the bPatcher everyone was talking about was an object and not just a nomenclature for a regular subpatch :)