Holiday notice: Cycling '74 will be closed on Dec 25th, 26th, and Jan 1st. Manual authorization, support cases, and manual order processing will be delayed.
mc.poly~ in behaves different from poly~
Nov 07 2018 | 4:27 pm
I try to set up a mc.poly with mc.sfplay~, mc.matrix etc. I learned already that one still has to come out of poly with single out~ objects and hope hat there will be a mc.out~ object soon. But besides that I cannot make mc.poly~ work, it only plays the first instance, although inside the poly it does play, but all instances above 1 are not appearing outside of the poly~. What is to be done differently from the old poly~? I built a traditional poly~ in the same patcher and it works, the mc.poly~does not.
Can anyone help? Thanks
here my mc.poly~ wrapper and the two poly~ patches .
- Nov 07 2018 | 10:47 pmYou only need one out~ object with mc.poly~. I'd suggest moving your matrix to outside the poly~:
- Nov 07 2018 | 10:58 pmHi Matteo,thanks for your suggestion, but that's not what I want to do. I work with multitrack field recordings, and I want to route the tracks to different outputs, something that matrix allows. But mc.poly~does not allow that. I cannot play a 8 track file out od a single out~in a poly~. And that was already confirmed by cycling. One should be able to play multitrack out of a poly. There is a gap in the mc. concept Anyhow thanks for your effort.
- Nov 17 2018 | 8:54 amIt looks to me that your issue is you're unpacking the outputs inside the mc.poly~. The number of channels in the mc.poly~'s output is directly linked to the number of mc.poly~ instances. So if you want to play an 8 channel file out of an mc.poly~, it must have 8 instances. (e.g. [mc.poly~ polyName 8] )I've attached a modified version of your test3 file. Just load it into an mc.poly~ and attach an mc.meter~ to it and let me know if it works the same.
