mattyo

If I'm using MC _inside_ a poly, how do I get an mc signal out? I often wrap audio engines in a poly~ with a single instance to disable them when not in use, but if there is an mc signal chain, I can only get a mono output. mc.poly~ gives me an mc patchcord, but still with only one channel of audio. I'm not talking anything fancy here, just stereo...

There's no such thing as [mc.out~], (or an mcs.poly~, which might do it if I understand mcs correctly) so are we stuck with using one channel/[out ] with poly~?

out~

mc.pack~

cycle~

mcs.play~

comment

number

mc.*~

mc.selector~

mc.poly~

mc.dac~

poly~

If I'm using MC _inside_ a poly, how do I get an mc signal out? I often wrap audio engines in a poly~ with a single instance to disable them when not in use, but if there is an mc signal chain, I can only get a mono output. mc.poly~ gives me an mc patchcord, but still with only one channel of audio. I'm not talking anything fancy here, just stereo...

There's no such thing as [mc.out~], (or an mcs.poly~, which might do it if I understand mcs correctly) so are we stuck with using one channel/[out ] with poly~?

If I'm using MC _inside_ a poly, how do I get an mc signal out? I often wrap audio engines in a poly~ with a single instance to disable them

mc-*-as-poly~-outputs

same need here, please keep us posted, Cycling!

I am also experiencing the same situation - would be great to hear of any solution to this

I have the same situation and I use mc.send~ to send stuff out of the poly~

Using send~ of any flavor across a poly~ boundary isn't supported by Cycling, (or at least it wasn't last time I checked), so use at your own risk. Maybe someone more official than I can confirm that...

So I've been told... But I have been using send~and receive~ in poly~ for the past few years. Never had any issues. Even in nested poly~'s 

https://wfs-diy.net/2020/04/12/systeme-wfs/ download the project. 

Even in process heavy configurations it's been rock solid.

So I've been told... But I have been using send~and receive~ in poly~ for the past few years. Never had any issues. Even in nested poly~'s 
You can try it for yourself ;)
https://wfs-diy.net/2020/04/12/systeme-wfs/ download the project. 
Even in process heavy configurations it's been rock solid.

I used to do it all the time as well, but I heard some vague rumblings once that there was no guarantee the functionality would last, and I dreaded having to rebuild a lot of stuff if an upgrade suddenly took it away. So I would say carry on, but to be safe , and mc.out~ would be handy, just in case.

Also, it adds a vector of delay, so depending on your application, that can also be a problem...

Also,  it adds a vector of delay, so depending on your application, that can also be a problem...

Maybe this thread is coming to an end with Max 8.3:

mc.in~ / mc.out~: MC versions of poly~ signal input objects

Unfortunately the mc.in~/mc.out~ still do not seem to work for me and the poly~ outputs mono signal...

mc.* as poly~ outputs