ComfortableInClouds

Hi, thought I'd combine a couple of questions I have into a single post as to not clutter this forum even more.

I am using Puckette's immensely fun bonk~ and was curious as to what he means by "cooked" output? what is the significance of the 3 numbers given by the 'cooked' outlet, and why is it that in his example he chose the 3rd element of the list to determine pitches for the synth?

On a completely different subject: how is it that I would connect an autopattr object in a bpatcher to an autopattr in the parent patch? i'd like to be able to save the states of bpatchers when i save the state of the rest of the patch.

bonk-question-and-autopattr-question

On Jun 28, 2008, at 8:59 AM, Kyle Kaplan wrote:

> On a completely different subject: how is it that I would connect an 

> autopattr object in a bpatcher to an autopattr in the parent patch? 

> i'd like to be able to save the states of bpatchers when i save the 

Assuming that you have the pattr/autopattr stuff set up in the parent 

patch, all you have to do is give the bpatcher instance a Scripting 

Name to have it be seen by the top level autopattr.

> On a completely different subject: how is it that I would connect an  
> autopattr object in a bpatcher to an autopattr in the parent patch?  
> i'd like to be able to save the states of bpatchers when i save the  
> state of the rest of the patch.

Assuming that you have the pattr/autopattr stuff set up in the parent  
patch, all you have to do is give the bpatcher instance a Scripting  
Name to have it be seen by the top level autopattr.

Chris Muir
cbm@well.com	
http://www.xfade.com

It's three values are: the instrument number (in case you trained 

bonk~ to distinguish between several objects); the overall loudness in 

the weird units, and the brilliance of the sound, AKA color 

temperature, measured as the center of gravity of the "raw" vector. 

If you try putting various sinusoids in and banging bonk~ to poll its 

measurements, the color temperature should tell you which filter the 

> I am using Puckette's immensely fun bonk~ and was curious as to what 

> he means by "cooked" output? what is the significance of the 3 

> numbers given by the 'cooked' outlet, and why is it that in his 

> example he chose the 3rd element of the list to determine pitches 

It's three values are: the instrument number (in case you trained  
bonk~ to distinguish between several objects); the overall loudness in  
the weird units, and the brilliance of the sound, AKA color  
temperature, measured as the center of gravity of the "raw" vector.   
If you try putting various sinusoids in and banging bonk~ to poll its  
measurements, the color temperature should tell you which filter the  
sinusoid matches.

> I am using Puckette's immensely fun bonk~ and was curious as to what  
> he means by "cooked" output? what is the significance of the 3  
> numbers given by the 'cooked' outlet, and why is it that in his  
> example he chose the 3rd element of the list to determine pitches  
> for the synth?


thanks for the reply barry, that's interesting stuff.

as for my autopattr concerns, it seems that giving the bpatcher a scripting name doesn't save the state of the objects within that bpatcher. no number boxes, no function states, no toggles are recalled. i am thinking of creating an inlet in the bpatcher and connecting it to the objects i'd like to be exposed to autopattr. Tho it seems like there should be an easier method?

You don't really connect autopattr objects to anything.

Check the pattr help files...particularly pattrstorage.

On Jun 28, 2008, at 7:16 PM, Kyle Kaplan wrote:

> thanks for the reply barry, that's interesting stuff.

> as for my autopattr concerns, it seems that giving the bpatcher a 

> scripting name doesn't save the state of the objects within that 

> bpatcher. no number boxes, no function states, no toggles are 

> recalled. i am thinking of creating an inlet in the bpatcher and 

> connecting it to the objects i'd like to be exposed to autopattr. 

> Tho it seems like there should be an easier method?

>
> thanks for the reply barry, that's interesting stuff.
>
> as for my autopattr concerns, it seems that giving the bpatcher a  
> scripting name doesn't save the state of the objects within that  
> bpatcher. no number boxes, no function states, no toggles are  
> recalled. i am thinking of creating an inlet in the bpatcher and  
> connecting it to the objects i'd like to be exposed to autopattr.  
> Tho it seems like there should be an easier method?
> --
> -k.


You are doing something wrong, somewhere. What has to be in place 

- all the things you want found by autopattr need scripting names

Then, in the top level patch, the bpatcher itself needs a scripting 

I have an example of a simple storage system built w/ the pattr stuff, 

called PattrKitty, on my examples page. I just added a bpatcher to 

On Jun 28, 2008, at 7:16 PM, Kyle Kaplan wrote:
> as for my autopattr concerns, it seems that giving the bpatcher a  
> scripting name doesn't save the state of the objects within that  
> bpatcher. no number boxes, no function states, no toggles are  
> recalled. i am thinking of creating an inlet in the bpatcher and  
> connecting it to the objects i'd like to be exposed to autopattr.  
> Tho it seems like there should be an easier method?

You are doing something wrong, somewhere. What has to be in place  
inside the bpatcher is:
- all the things you want found by autopattr need scripting names
- you need an autopattr in the bpatcher
Then, in the top level patch, the bpatcher itself needs a scripting  
name.

I have an example of a simple storage system built w/ the pattr stuff,  
called PattrKitty, on my examples page. I just added a bpatcher to  
that example.
http://www.xfade.com/max/examples

Bonk~ Question and Autopattr Question