dx1200

Hello, Attached is a patch I'm using within a bigger project. It's four, four channel delay lines with feedback. I'm using it embedded in a bpatcher in the main patch. Problem is that when I send a signal to a certain target, it goes to all poly~ subs. I'm using a another similar patch within the main patch as well and that works fine. Although not using a bpatcher for that one.

Has anybody any idea why? hope it is down to lack of experience on my part...

Hello, Attached is a patch I'm using within a bigger project. It's four, four channel delay lines with feedback. I'm using it embedded in a bpatcher in the main patch. Problem is that when I send a signal to a certain target, it goes to all poly~ subs. I'm using a another similar patch within the main patch as well and that works fine. Although not using a bpatcher for that one. 

possible-poly-bug

On Aug 27, 2008, at 7:15 PM, dx1200 wrote:

> Problem is that when I send a signal to a certain target, it goes to 

You didn't attach the patch the lives in the poly~.

> Problem is that when I send a signal to a certain target, it goes to  
> all poly~ subs.

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

sorry about that. Here's the whole thing again. poly~ subpatch first. poly~ main patch, with proper message to sfplay~ this time, second.

No, the target message works as expected here.

But you might consider to think about your whole structure. Why do you 

put four delays into the poly~ and not just one? You can use the same 

poly~ several times if you want to distinguish between several inputs...

For your presets, you should consider the use of the pattr system, as 

your present patch can't really pass all delay times into the poly~, 

only one target will be addressed, as the preset only remembers the 

dx1200 schrieb:
> Has anybody any idea why? 

But you might consider to think about your whole structure. Why do you 
put four delays into the poly~ and not just one? You can use the same 
poly~ several times if you want to distinguish between several inputs...

For your presets, you should consider the use of the pattr system, as 
your present patch can't really pass all delay times into the poly~, 
only one target will be addressed, as the preset only remembers the 
values of your main patch...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


Quote: Stefan Tiedje wrote on Thu, 28 August 2008 06:39

----------------------------------------------------

> Why do you put four delays into the poly~ and not just one? You can use the same poly~ several times if you want to distinguish between several inputs...

I was thinking I could put four delay units in one poly~ and distinguish signal inputs using target. I'll try your approach it makes more sense now.

> For your presets, you should consider the use of the pattr system, as your present patch can't really pass all delay times into the poly~, only one target will be addressed, as the preset only remembers the values of your main patch...

The preset is only standing in until I can make time to go and learn pattr family. Think it's best we get acquainted now.

Quote: Stefan Tiedje wrote on Thu, 28 August 2008 06:39
----------------------------------------------------
Hi Stefan, thanks for checking my patch.

I was thinking I could put four delay units in one poly~ and distinguish signal inputs using target. I'll try your approach it makes more sense now. 

The preset is only standing in until I can make time to go and learn pattr family. Think it's best we get acquainted now. 

On Aug 28, 2008, at 8:03 AM, dx1200 wrote:

> The preset is only standing in until I can make time to go and learn 

> pattr family. Think it's best we get acquainted now.

For simple storage needs autopattr is pretty easy to use. I have an 

example, called PattrKitty, on my examples page - 

On Aug 28, 2008, at 8:03 AM, dx1200 wrote:
> The preset is only standing in until I can make time to go and learn  
> pattr family. Think it's best we get acquainted now.

For simple storage needs autopattr is pretty easy to use. I have an  
example, called PattrKitty, on my examples page - http://www.xfade.com/max/examples

Possible poly~ bug?