personal_username

let's say I have a poly with 50 voices and I want these voices to be independently routed to some fx and then head to the dac.

Is there a more CPU-wise way to do this instead of having a matrix with 50 voices in (+ a few fx in)?

I don't like the idea of having a matrix with 50 msp patchcords coming from single poly instances attached in if I, let's say, need just 3 of those voices. I'm building a modular system, so I like the flexibility of having 50 voices if i need, but hate the idea of asking a lot of CPU if I'm not.

let's say I have a poly with 50 voices and I want these voices to be independently routed to some fx and then head to the dac.
Is there a more CPU-wise way to do this instead of having a matrix with 50 voices in (+ a few fx in)?
I don't like the idea of having a matrix with 50 msp patchcords coming from single poly instances attached in if I, let's say,  need just 3 of those voices. I'm building a modular system, so I like the flexibility of having 50 voices if i need, but hate the idea of asking a lot of CPU if I'm not.

poly-and-matrix

You could have a [send~ to_blabla_fx] for every effect with a [gate~], in your poly~ patch, since you have a few effects.

Also, probably place [gate~]s at the outlets if you want to stop the voice from directly going to the outlet.

Then, using the [poly~]'s "target" message, you can control every instance's [send~]s.

You could have a [send~ to_blabla_fx] for every effect with a [gate~], in your poly~ patch, since you have a few effects.
Also, probably place [gate~]s at the outlets if you want to stop the voice from directly going to the outlet. 

Then, using the [poly~]'s "target" message, you can control every instance's [send~]s.
Something like the example below.

poly and matrix