Cycling 74 » Topic: send~/receive~ to/from poly~ no more? http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/feed Tue, 18 Jun 2013 16:12:22 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-59448 <![CDATA[send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-59448 Thu, 20 Oct 2011 11:27:54 +0000 g2312 Hi,

it seems that the option to send audio to/from single instances of patchers inside poly~is no more available? That would be a pity since at least I use this quite often for the dynamical creation of dsp chains. To give an example I attach the building blocks of a feedback network which works very nice under Max 5. Some dependencies are replaced with dummy patchers.

Best

Thomas

Save as “tLb.FeedbackGridNode~”:

– Pasted Max Patch, click to expand. –

Save as “tLb.FeedbackGrid~”:

– Pasted Max Patch, click to expand. –
]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213963 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213963 Thu, 20 Oct 2011 13:53:38 +0000 pm I have exactly the same problem. Can’t use send~ audio signal outside a poly…

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213964 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213964 Thu, 20 Oct 2011 23:21:35 +0000 Ben Bracken send~ and receive~ is currently not working with poly~, but we hope to have this working again down the road.

FWIW, using send~ and receive~ with poly~ should generally to be avoided.

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213965 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213965 Fri, 21 Oct 2011 13:44:15 +0000 g2312 Hi Ben,

> send~ and receive~ is currently not working with poly~
> FWIW, using send~ and receive~ with poly~ should generally to be avoided.

ok, any other (new?) way to get sound in and out of single patcher instances inside poly~ would be also fine. The framework I developed uses wrappers for abstractions made with poly~, and the number of in~s and out~s vary from time to time (e.g. sidechain conections). Doing it this way is very elegant in the context I use it. BTW, you can find it now on the “Projects” page (LSD-LVD-tLb).

Thomas

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213966 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213966 Fri, 21 Oct 2011 14:29:24 +0000 christripledot

ok, any other (new?) way to get sound in and out of single patcher instances inside poly~ would be also fine.

+1< <1024

:D

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213967 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213967 Fri, 16 Mar 2012 13:19:51 +0000 FP +1 to solve this problem.
It was ok with max4.5 and 5 so it could be possible to get it working with max6. no ?

I got a similar problem but with send and receive inside the poly, related in this thread :

http://cycling74.com/forums/topic.php?id=38508&replies=4#post-188547

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213968 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213968 Fri, 16 Mar 2012 16:09:55 +0000 Ben Bracken FP, this should be working with Max 6.0.4. Please let us know if you are experiencing issues.

Did you receive my email regarding this other thread? I have logged it as a bug and we will be taking a closer look.

-Ben

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213969 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213969 Fri, 16 Mar 2012 18:33:20 +0000 Peter McCulloch > FWIW, using send~ and receive~ with poly~ should generally to be avoided.

My two cents: I hope that send~/receive~ in poly~ doesn’t go away, because there’s certain things that are not easily possible otherwise. For example, I’m building a modular synth. If I want to add another sample and hold module or step sequencer, etc. I just add another voice to its existing poly patch. Its inputs and outputs are send~ and receive~, and I can’t think of an easier way to do this. I mute it when I don’t need it, I can use the target messages to talk to the specific instance. Lots of good things.

I’m guessing the reasoning for not doing this has to do with parallel processing? (or is there another reason?)

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213970 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213970 Mon, 13 Aug 2012 20:22:06 +0000 mrmorrisplains Not sure where this issue is at.
Currently, I’m trying to send~ multiple instances of audio from the poly~ object in Max 6.04. I have them numbered with a #0 string.
The only problem is that the numbering system seems to change each time I reopen Max.

Is there another way to approach this?

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213971 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213971 Mon, 13 Aug 2012 20:46:18 +0000 Peter McCulloch There is. If you want to get individual sends, you shouldn’t use #0, since you don’t know what the numbering base will be any time you open the patch. Instead, you can change the target of the sends after the fact using the “set yourTargetHere” message. I would recommend the following:

loadbang
|
thispoly~ (reports voice instance number!)
|
sprintf set elaborateSendName-%d
|
send~ BLACKHOLE

At load, the target “BLACKHOLE” will be replaced with elaborateSendName-1 (first voice), elaborateSendName-2 (second voice), etc.

#0 is really just for situations where you need a local send/receive; if anything else has to talk to it, it’s probably not what you want.

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213972 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213972 Mon, 13 Aug 2012 21:40:19 +0000 rama I would recommend using John MacCallum’s poly.send~ and poly.bus~ which are specifically made for this – you can get them here from the CNMAT site -> http://cnmat.berkeley.edu/downloads

]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213973 <![CDATA[Re: send~/receive~ to/from poly~ no more?]]> http://cycling74.com/forums/topic/sendreceive-tofrom-poly-no-more/#post-213973 Sat, 08 Dec 2012 14:54:05 +0000 Nicolas Deflache poly.send~ and poly.bus~ are very useful to me, but I would like to know if there are any known drawbacks using them, or any problems that should be expected, especially in large patches.

]]>