Partitioning Cpu across several patches

    Aug 22 2012 | 6:44 pm
    Hello friends,
    I'm looking for a way to create a master patch to perform with. In doing so I've run into the limitations of processing speed and the desire to have a vast array of patches to use . Thus I want to ask: does anyone know how to turn processing on and off in one patch? I tried using mute~ but am not sure how this would work in a patch that has several networks, e.g., a drum machine. Any help would be greatly appreciated.

    • Aug 22 2012 | 7:15 pm
      I'm not sure mute~ is supported now. I may be wrong. The way I would do it would be to wrap the parts you want to mute in a poly~ with one voice and mute the voice when you don't want it.
    • Aug 22 2012 | 8:08 pm
      thanks, I will give this a try.
    • Aug 22 2012 | 9:48 pm
      farfisavox is correct on both counts - mute~ is, indeed, deprecated. And using a poly~ object to wrap bits of a patch you wish to enable/disable is the current way to go.
    • Aug 23 2012 | 4:24 pm
      Do you have an implementation of this? (I'm working on the poly~ papers but these seem a far shot from what I need to do)
    • Aug 23 2012 | 4:56 pm
      Basically make the bit of patch a subpatcher, then go in and change all inlet/outputs to "in 1", "out 2", or "in~ 1", "out~ 2" for audio. Save that as a patch. Then create a new patch and save it in the same place. Once that's done create a new object called "poly~ XXXX" (with XXXX being whatever you called the poly patch) and it will load up.
      Then you can use the [mute] messages (see the poly~ helpfile) to turn it on/off.
    • Aug 23 2012 | 5:26 pm
      Thanks, Rodrigo. But, could you be a bit more specific about what "a bit of patch," and "in the same place" mean. The thing that really baffles me is having many different voices (as in one voice is a drum seq. one is an oscillator with feedback, etc...- is that even possible?
      thanks again
      (p.s. even a very simple patch might help illustrate the point.)