Exit Only

Just wanted to say that I'm super excited about the new "mc" concept in Max 8.

I've been doing a lot of work with a seaboard rise recently and have always been frustrated by the workflow mechanics when developing a synth using poly~ which usually required patching in mono for a while, then eventually making it a multi voice poly~ and then always having to make sure all the objects in the poly~ have the correct values etc. Being able to patch a multi-voice synth the same way I would any other max patch is going to be a game changer.

One of the things that I always loved about Supercollider was the concept of multi-channel expansion where an array of Ugens would effectively be an array of channels and they could be summed at the end to be mixed down to stereo. It's amazing to think that msp can do something very similar now along with all the other things that make max awesome already.

 I've been doing a lot of work with a seaboard rise recently and have always been frustrated by the workflow mechanics when developing a synth using poly~ which usually required patching in mono for a while, then eventually making it a multi voice poly~ and then always having to make sure all the objects in the poly~ have the correct values etc.  Being able to patch a multi-voice synth the same way I would any other max patch is going to be a game changer.  

Just wanted to say that I'm super excited about the new "mc" concept in Max 8.
 I've been doing a lot of work with a seaboard rise recently 

super-excited-about-mc

Came here to say the same thing. MC is absolutely killer! Can't believe you've been sitting on it for a whole year :)

Yes, me too: as you may have already read in another thread, i'm so excited by MC, i've decided to change my name and become an MC Wrappa myself.

(P.S. if possible, it'd be great if the future Max8 SDK would show how we can integrate MC in our own custom external-coding... if not, no worries, i will just stick with mc/mcs.gen~ etc. but just thought i'd mention it to put it on anyone's radar if possible)

Yes, me too: as you may have already read in another thread, i'm so excited by MC, i've decided to change my name and become an MC Wrappa myself.
Word ;)

(P.S. if possible, it'd be great if the future Max8 SDK would show how we can integrate MC in our own custom external-coding... if not, no worries, i will just stick with mc/mcs.gen~ etc. but just thought i'd mention it to put it on anyone's radar if possible)


I am delighted to join this holy choire of praises initiated by our new Master Of Ceremony MC Wrapper 👐.

Just when I thought that the attention had (temprarily) shifted and the visual part is now the darling, you brought audio back into the race. 🏄

I am delighted to join this holy choire of praises initiated by our new Master Of Ceremony MC Wrapper 👐.
Just when I thought that the attention had (temprarily) shifted and the visual part is now the darling, you brought audio back into the race. 🏄

@raja more detailed information for advanced external MC development coming in the future, but just a quick comment that pretty much any object that can work in parallel for mc usage will work as is with the mc.wrapper~ implementation. That just makes N copies of the object and dispatches the N channels to the N instances. You just need to add something to your package's init folder with lines of the form:

If you need to do special things like access multiple channels from within one single instance, like mc.mixdown~ does, you'll need to wait on the updated SDK. However if you look at init/audio-objectmappings.txt file (inside the app bundle/resources), you'll notice that most MC versions of standard msp~ objects are simply using the wrapper.

☝️ @josh oh sweet, thanks so much! this is good info. to know, (i was particularly interested because i'm wondering how my own custom stuff might impact CPU when created into multiple instances within this context, this info. explains enough about that to give me a good starting understanding and a place to begin testing).

  ☝️ @josh oh sweet, thanks so much! this is good info. to know, (i was particularly interested because i'm wondering how my own custom stuff might impact CPU when created into multiple instances within this context, this info. explains enough about that to give me a good starting understanding and a place to begin testing).
thanks again, truly appreciated 🍻


Just to add to the praise, though I have to adapt my St.ools now, I had been waiting for this literally for more than a decade... 

As important as poly~ was back in the days...

Just to add to the praise, though I have to adapt my St.ools now, I had been waiting for this literally for more than a decade... 
As important as poly~ was back in the days...

Super excited about mc