Forums > MaxMSP

Failed attempts to control Cuemix FX via OSC

September 11, 2013 | 4:12 am

I tried to get Cuemix controlled via osc, as it is possible to do that with TouchOSC, I thought it should work easily. But it doesn’t…

Thats what I tried: First I analyzed the osc messages from the Motu cuemix touchosc template.
TouchOsc is sending for example this message for the first slider:

/bin/fvEB+0/fvInCS+0/cdf 0.497549

I connected TouchOSC to Cuemix, and TouchOSC is telling me its sending on port 53497.

Then I tried to send the above message to the ip of my Macbook (code at the end of the post)
I also tried localhost and a broadcast…
But Cuemix does not move the slider…

I have no idea why this is failing…
There is also some kind of handshaking between TouchOSC and Cuemix happening. But I don’t know what how it is happening there.
TouchOSC does see Cuemix as Host, but it does not see Max as host. The host is delivering the information about the ports to TouchOSC.
In Cuemix I do see my iPad as TouchOSC device. I want to make it think my Maxpatch is a TouchOSC device as well… But how to achieve this…?

Has anybody got a cuemix control of any kind working? (The HUI Protocol might be an option as well…)


– Pasted Max Patch, click to expand. –


December 27, 2013 | 8:43 am

Hi Stefan,

I am using Max to establish a OSC connection to CueMixFX and control volumes of all busses with a MIDI controller:

If you want to dig deeper, you will have to check the OSC messages in the TouchOSC templates of the MOTU driver (see I have attached an example patch that uses osctools. Hope it works!


– Pasted Max Patch, click to expand. –



December 27, 2013 | 9:12 am

This is very interesting for some motu devices owners :) thanks for the infos !

February 24, 2014 | 2:57 pm

i’m trying to dig into this at the moment, and can’t understand several things…
*i don’t have touchOSC, apparently it’s used because it has a built-in template for communicating with CueMix right ? this template that "sc7" at that motunation thread reverse engineered and which is there, is that it ?
*so, one has to set CueMix in "OSC enabled" mode, but how ?…
*on which channel does CueMix send osc informations ?
Thanks, hoping someone will find it (i see dhjdhjdhj took part in that motunation conversation, maybe if he reads that… aaah, if only there was some kind of private messaging system…)

February 24, 2014 | 3:23 pm

Ok, so i just updated my motu softwares and voilà ! there is an osc enable option in cuemix fx (menu "control surfaces"). I should be going better now. Will report later if it works.

February 27, 2014 | 3:30 pm

What do the zeroconf objects do in Sarnold’s patch ? i’m lost ! .. i can receive osc messages from CueMix, but had no luck sending any of them.

February 27, 2014 | 3:33 pm

i also don’t understand what is meant by the "HACK NEEDED" paragraph……….

February 28, 2014 | 5:25 pm

It works !….

March 3, 2014 | 12:39 pm

I just got a roughly working connection from my Fostex MixTAB Midi controler to the CueMix controlling a Motu UltraLite mkIII hybrid with the below project. For your own needs just replace the mtlin subpatcher with your own connection to your controller.
This is far from being ready, not all potentiometers are connected yet, but (hopefully) you get the idea…
The patch has to act as if it is a TouchOSC on an iPad. The feedback from CueMix only happens if CueMix assumes a specific view on the iPad. This is unnecessarily difficult, but MotU seems to think along "why easy if it could be complicated…;-)"


have fun…

March 3, 2014 | 1:23 pm

hah, so that explains the necessity of the zeroconfs objects to declare as a "touchOSC like" device name ? btw i got it to work, modifiying Sarnold’s patch ; i found it just right before the gig ;)

Viewing 10 posts - 1 through 10 (of 10 total)