Preset problems!
Hello,
I've been putting together a monosynth over the last few days with a sequencer and I wanted two separate preset systems... one to handle the sequencer patterns and another to handle the synth voice settings. I didnt want one to change anything on the other, but the synth voice presets seem to all be changing the sequencer patterns! Ive connected the 'disregard' output to all the objects i think i should have, but no luck! Any help is appreciated..
As far as I can see it's behaving as expected given the way you've made your patch.
I haven't used preset in a long time (have you looked at pattr?) but I think you shouldn't need to make this so complicated. Simply keep the left preset as is, and then connect the right preset's leftmost outlet similarly to the objects you want it to control. In other words, you don't need to _exclude_ all of the objects you don't want to control, just _include_ the ones you do.
hi, thanks for the reply. It's made me think, maybe I will begin again with new preset objects and use only the 'include' patch cords on specific objects (one of them was 'including' everything except from a few objects).
I have looked into pattr and i'd love to use that (for its interpolation too, sounds great) but for some reason im finding it quite confusing.
What part of this procedure is confusing?
1. Select each UI object whose value you want to store. Open the object's Inspector and type a name into the Value column for the Scripting Name attribute.
2. Add a pattrstorage object to your patch. Give it a name by including an argument (e.g. pattrstorage mine)
3. Add an autopattr object to your patch.
That's it. To store a preset called "1", send the message "store 1" to the pattrstorage object. To recall a preset called "1," send the message "recall 1" to the pattrstorage object. *That's* complicated?
Oh - and if you *really* still want to use the preset thingy once you've done things 1 - 3, all you do is plop the preset object down in the patch, open its Inspector, and type the name you gave the pattrstorage object (in the above example, it was "mine") into the Value column for the pattrstorage attribute at the very bottom of the inspector.
Well, to be fair, the autopattr approach works amazingly well when you want a single preset control for your patch. He wants a way to create two preset controls for specific, discrete parts of his patch - pattr is a bit more complex to configure in this case, no?
Thankyou both for the suggestions, I had another look into pattr, I get it now.. (the last time I tried pattr was some time ago when I was still finding my max feet a bit more than now)..
I have incorporated an interpolating pattr preset system for the synth settings and used a separate [preset] linked onto to pitch, velocity and duration controls in the sequencer to control the sequencer - it works a treat, thanks a lot. :)
-->Well, to be fair, the autopattr approach works amazingly well when you want a single preset control for your patch. He wants a way to create two preset controls for specific, discrete parts of his patch - pattr is a bit more complex to configure in this case, no?
I'm also wondering about this, the use of [pattr] seems to be patch-wide. Any way to have separate ones control different collections of objects in the same patch? Of course you can do it with bpatchers etc., but all in one patch?
Also there's no need for the external .xml file with [preset], which is helpful.
Looks like you're right, pattr seems to be global for a given patcher. Somehow I thought this wasn't the case, but it shouldn't be too big a deal to find a workaround - just use subpatchers or bpatchers, as you say.
hi
you can use a second pattrstorage for a specific patcher that you desactivate
in the main pattrstorage (message "active") to avoid including the presets of the former into the latter
cf.pattrstorage reference
N.
You could also use different pattrstorages in different subpatchers. Keep the synth and the sequencer in separate subpatchers, maybe as bpatcher and there you go. pattrstorage is only looking up the tree...
Stefan