mr.l

just a (simple) question: is it possible to include Bpatchers with the preset-object? If yes, how? Just puting the preset-object into the patch in which I have included Bpatchers doesnt work...

presets-bpatchers

The master-preset technique is great, I use it a lot. Many times you want presets to only handle one small collection of parameters in a large patch, and you want independent control of other groups. But then you figure out that certain combinations of those presets work well together... so... attach an integer box to the preset (minimum of 1, and going as high as the # of presets), then attach a master preset to that box and any others you have.

These int boxes can be hidden or not. If not, sometimes it's nice to use the arrow keys to scroll quickly through each preset instead of clicking. Clicking isn't a problem, you say? True in most cases, but having a number box also lets you access them programatically or automatically (though technically you can do these without it). But it also lets you use a keystroke to select the number box for focus (so you could hit "p" and know that you're now in that preset's number box, then use arrows or numbers to choose... this can be done without looking, or with windows on top, etc.) You'd probably want to hook a "set $1" message out of the "preset # recalled" outlet back to that number box, so that if you click a preset, the int box reflects the choice.

For presets to remember values inside a bpatcher, subpatch, or "object patch" (abstraction), you need to have inlets which go to the parameters desired. Then attach the preset---which in this case is outside---to those inlets, voila.

Really like the color/size controls of the new preset object, it looks great and is way more flexible as an interface object now!

The master-preset technique is great, I use it a lot. Many times you want presets to only handle one small collection of parameters in a large patch, and you want independent control of other groups. But then you figure out that certain combinations of those presets work well together... so... attach an integer box to the preset (minimum of 1, and going as high as the # of presets), then attach a master preset to that box and any others you have. 

For presets to remember values inside a bpatcher, subpatch, or "object patch" (abstraction), you need to have inlets which go to the parameters desired. Then attach the preset---which in this case is outside---to those inlets, voila. 

I will try it out and see which solution works best for me.

I now tried the autopattr object and it works great! Thanks again.

I tried this, as well as check-marking "embed in parent patcher" in the bpatcher's inpector window to no avail. I have 9 inlets going to 9 live.dials (all of which are named). I've tried hooking it up to just the first inlet, as well as all inlets.

I've also tried autopattr/ pattrstorage, but I still can't figure out how to save/ recall states for only the bpatcher in question.

I tried this, as well as check-marking "embed in parent patcher" in the bpatcher's inpector window to no avail.  I have 9 inlets going to 9 live.dials (all of which are named). I've tried hooking it up to just the first inlet, as well as all inlets.

I've also tried autopattr/ pattrstorage, but I still can't figure out how to save/ recall states for only the bpatcher in question.

In subpatcher I create inlet connected to a rotary but the preset don't recall the position of it.

I tried using send / receive doesn't recall too.

Same here.
In subpatcher I create inlet connected to a rotary but the preset don't recall the position of it.
I tried using send / receive doesn't recall too.

presets & bpatchers