Brian H.

I have a patch which has nested [bpatchers]. Is there a way to access the inlets/outlets on a lower layer from a top layer? In other words, I'd like to connect one of these bpatchers 2-3 layers down directly to something on the top layer.

I know I can create inlets/outlets in all bpatchers to basically 'drill' into them, but I'm wondering if there's another, more direct technique? I'd like to avoid send/receive for now, but if I have to use it, OK.

Hi,
I have a patch which has nested [bpatchers].  Is there a way to access the inlets/outlets on a lower layer from a top layer?  In other words, I'd like to connect one of these bpatchers 2-3 layers down directly to something on the top layer.

I know I can create inlets/outlets in all bpatchers to basically 'drill' into them, but I'm wondering if there's another, more direct technique?  I'd like to avoid send/receive for now, but if I have to use it, OK.

bpatcher-layering

On Dec 14, 2008, at 5:59 PM, Brian Heller wrote:

> I know I can create inlets/outlets in all bpatchers to basically 

> 'drill' into them, but I'm wondering if there's another, more direct 

> technique? I'd like to avoid send/receive for now, but if I have to 

If your patch uses the pattr system, you can use it to address 

On Dec 14, 2008, at 5:59 PM, Brian Heller wrote:
> I know I can create inlets/outlets in all bpatchers to basically  
> 'drill' into them, but I'm wondering if there's another, more direct  
> technique?  I'd like to avoid send/receive for now, but if I have to  
> use it, OK.

If your patch uses the pattr system, you can use it to address  
parameters at any level.

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

Thanks for pointing me in the right direction. I didn't know about [pvar] which would be great it could talk out of its patcher. My model for what I'm doing (a working model of a particular digital mixing console for training) probably requires [send/receive]. But [pattr] is whole new world in Max! I knew it was used to store 'states' and patch data, but didn't know it was really an entire other system of objects, perfect for multi-layer patches like this. The good news is that it's probably the right tool for the job; The bad news is that learning it means I'm not as far along as I thought I was. :)

Thanks for pointing me in the right direction.  I didn't know about [pvar] which would be great it could talk out of its patcher.  My model for what I'm doing (a working model of a particular digital mixing console for training) probably requires [send/receive].  But [pattr] is whole new world in Max!  I knew it was used to store 'states' and patch data, but didn't know it was really an entire other system of objects, perfect for multi-layer patches like this.  The good news is that it's probably the right tool for the job; The bad news is that learning it means I'm not as far along as I thought I was.  :)

OK, so I'm on my way to starting with [pattr] (thanks to Chris Muir's examples on his page, which boiled things down nicely). But in order to get an actual signal from, say 4 [bpatchers] down up to the top level, the best way would be to either use multiple layers of outlets or [send~/receive~], is that right?

OK, so I'm on my way to starting with [pattr] (thanks to Chris Muir's examples on his page, which boiled things down nicely).  But in order to get an actual signal from, say 4 [bpatchers] down up to the top level, the best way would be to either use multiple layers of outlets or [send~/receive~], is that right?

[bpatcher] Layering...