I have not done this so im only guessing but i think you need to set each version of totalmix to use a different port in OSC setup. Then you need an app to send the commands to more than one port.. I know touchOSC cannot do this. I am not sure about Lemur but the program that i know does it and does it really well is OSC commander.. It is Android though so if you only have ipad you are out of luck, (unless Lemur supports this feature)..

Also bare in mind if you want to control two versions of totalmix from one tablet layout your commands will be duplicated so if you raise master volume on one it will mirror on the other.. If this isnt what you want and you want totally independant control of both i think you will need a second tablet.

there are 4 index tabs because totalmix allows 4 individual OSC controllers at once.. They all need to at least have a different port setting but it can be 4 tablets etc.. The numbers 1-4 in submix determine which controller will have priority selecting output.. As far as how that affects the controllers, i havent played with it too much because i have only ever had one device controlling one totalmix but its there to allow up to 4 different devices..

Also i just checked out Lemur, it looks like you can send OSC to multiple ports from it so if you are on iPad and have that app it would work contrary to what i said earlier.. Although if you are using max its altogether different..

Also another option with learning totalmix OSC is to just load the totalmix template in touchOSC editor, that allows you to click each faders/button and see the associated OSC command. And there is an excel file with all commands also if you search the forum you should find it..  If your PD setup is working thats cool but it those other options might be quicker for you to refer to..

Have you sent OSC from Max to totalmix already ? If so did you just use 127.0.0.1 as the IP ? I tried to send OSC from Reaper and i couldnt get it to work, i wasnt sure if i had the setup right.. I thought i did but for some reason i was suspicious that totalmix wasnt accepting anything from 127.0.0.1 as the loopback IP...

have you successfuly sent OSC from max to totalmix ?

So does anyone know how to reliably address a specific Totalmix via OSC?

I'm not sure what you mean by "open the first instance" ---- when I open TotalMix, two mixer windows are immediately displayed, one for the first UCX (lower serial number) and the other for the second UCX (higher serial number).

The Settings page does not seem to have separate sets of "in use" options for each of these. There is just one "in use" section. There are 4 possible values and each one does allow you to set different ports and I had set each of them to 7001, 7002, 7003, 7004 respectively.

However, when I sent Max OSC messages out to /1/Volume1 (for example), it didn't seem to matter which port I used, the fader on the first UCX was almost always changed.

Now, there was exactly ONE occasion where (somehow) it looked like it was working ---- sending /1/Volume1 to the first 7001 changed the slider on the first UCX and sending the same message to 7003  (not 7002, by the way, that still seemed to go the first UCX) changed the fader on the second UCX.

But when I quit TotalMix and restarted, I was NEVER able to make that work again. Now, I don't know whether TotalMix is not properly opening and closing its listening sockets.

I guess my next step is to install nmap on that machine and see what ports are open for UDP messages. But I shouldn't have to be doing that --- this stuff should just work.

I have sent OSC messages from Max on the same machine (using the target 127.0.0.1) and from a different machine (using the visible IP address of the target machine, in this particular case 192.168.23.141)

Ultimately, I need to be able to
a) use two sliders on one of my keyboards to adjust two channel strip faders, one on each UCX (by having Max listen to MIDI output from the slider and generated the appropriate OSC data) and
b) modify a lemur template I'm already using to control other data in Max (via OSC messages from Lemur) to do the same thing.

Was never able to get MIDI working on it --- same issue, don't know how to address it.

When I decided to buy these (upon the recommendation of someone else in my band) I was told that RME support was amazing --- so far, with my questions to date, they have been incredibly unhelpful

there is a basic midi control description written in the manual.. its mentions the formula used for midi CC mapping to each channel.. i dont fancy your chances of getting control of the second UCX with it but worth a shot i guess..

Im not interested in PD or max really, it was just something i kept seeing people mention so i checked it out..  All id like to do is send OSC command mainMuteFx to totalmix from reaper and possibly automate some faders, but its proving to be very difficult to accomplish.. i have gotten fader control with midi from reaper but no luck muting FX.. I havent actually had any luck getting OSC into totalmix from any another software application, i initially tried to do it with reaper and no luck.. Then i downloaded PD just to test that function and still no luck although i can get PD to send OSC to reaper start/stop etc.. 

i recall some previous posts on here with people asking for "midi learn" in totalmix.. that and global OSC addressing would be good additions..

There seems to be something basically wrong in your setup. With two units connected it is not expected to open two TM FX windows. There should be only one window, so close one. In the upper right list of interfaces select one, then use the F3 - OSC dialog to type in the correct values. After that go to the upper right again, change to the other interface, open the F3 - OSC dialog and type in the correct (different) values. That way it should work and allows to use different settings for the interfaces.

If you then want to have two windows, one for each interface, you can do so via Ctrl-N.

The index is explained in the manual and relates to the use of multiple remotes with ONE interface.

It would make perfect sense except that every time TotalMix opens, it ALWAYS displays both devices, in two separate windows.

So I am guessing that there is a bug in the Settings dialog where the OSC setup part doesn't actually know which TotalMix one is trying to configure if both windows are open. Or perhaps it's defaulting to whichever TotalMix window was last highlighted --- that might actually explain how I managed to send OSC to the second TM FX once but never again.

I will try this experiment in the morning (and thank you for the suggestion) but I think that the Settings dialog should probably display (and/or let you select) which TM FX unit is being configured.

Or you just open your eyes

The title bar of the TM FX window has name and number of the device in it.

And it should be quite logical that when you exit TM FX with one window open per device, it will open those two windows again on next boot.

OK --- I have this working now ---- I appreciate the explanation for how to configure it.

However, I would strongly urge you to modify that Preferences dialog so that it makes it clear that it is referring to a specific device no matter which windows are open.

@ebulb --- now that I have this working I can guess where you were having a problem getting your totalmix to respond. Turns out you have to send out the OSC messages that mimic selecting the appropriate bus. I've attached a picture from the Max patcher I was using to experiment with this stuff. The vol sliders apply to the last section selected so you have to first send a busInput, busOutput or busPlayback message.

Certainly not the way I would have done it --- a properly designed OSC API would allow one to do things like

/busOutput/volume1  value
or
/busInput/volume1 value

http://i.imgur.com/FGvzv38.png

Thanks... I worked out the connection between PD and totalmix was working for me with 127.0.0.1.. Initially i thought it wasnt connecting and i ended up being able to get the volume faders to move but its the other OSC command i couldnt get to work for some reason.. It may be because i didnt have PD and Reaper sending the proper syntax.. I wanted to send mainMuteFx.. When the tablet does this it sends

/1/mainMuteFx 1
/1/mainMuteFx 0

It sends 1 for first message and 0 for the second message in one press.. in touchOSC editor you can simply write /1/mainMuteFx for the button and it will send both these values.. When you write /1/mainMuteFx in  PD though it doesnt send the 1 or 0.. So i added the 1 and it makes the tablets button work but doesnt react in totalmix ?? I couldnt work out how to send the two messages like the tablet does with the 1 and then the 0 so i figured it was something i was not doing in PD properly.. I dont know much about that prorgam and I ultimately wanted to get Reaper to send this which i couldnt see happening at this point in time, so i worked out plan B.

I looked at the midi control area of manual again and realised i can just make a different mix snapshots with the FX off and trigger them from midi keys.. Its not as elegant because i need snapshots for other things also so i have to double up a few of them but 8 is still enough for what i need and with one midi message from Reaper it turns off totalmix FX which was ultimately my goal.

That's great. I think it will be appreciated by many.

We're going on tour in three weeks and this stuff is working so much better than previous system I was using. In particular, your technique of explicitly using serial numbers to control the order of the seen devices eliminates a huge problem I was seeing when loading multiple MOTU 828s, which would sometimes show up in the wrong order.

Although I have it working as a hack, it would be nice to be able to address a specific fader without having to first select the submix. So for example, right now, to guarantee that a slider on my keyboard will actually move the correct fader on the TotalMix window, I have to send three other messages first

/1/busOutput 1.     // Make sure I have the Hardware Outputs Panel selected
/1/solo/1/2 0.        // This selects the desired submix, but doesn't seem to
                            // work if the hardout output panel isn't selected first
/1/busInput 1.       // Now select the input channel section

/1/volume1 xxx     // And send the desired value to the first fader

Clearly, the specific functionality (change volume1 level for submix 1) must exist independently of the user interface  (MVC anyone?) so something like

/1/submix3/inputVolume2 x

That would adjust the value of fader 2 in the input section associated with submix 3

The main reason I'd like to be able to do this is because UDP packets are not guaranteed to be delivered so there is always a risk that one of the OSC packets won't actually make it, particularly over a wifi connection, so a single atomic message would be safer.