Thank you for information. Sounds nice!

-J-

Any news on multiple controllers for TotalMix FX? Especially regarding OSC?

I've used a "workaround" to use multiple midi controllers in my setup (each musician controlling his monitor from one submix) :
all controllers are connected to a "midi brain" , and each of them has a "take control" button
when button is pressed the brain sends the "submix select" CC, and activates the controller
doing that i'm sure one musician won't mess up someone else's mix, but it requires a midi brain/router.

Also to make things clear I made a Table with all midi CC to make things easier to program
download the RME Totalmixfx midi CC table
I've tested all CC for the UFX so the table should be correct, not tested the HDSP CC, neither the note buttons.
The two notes in red i modified from the ones mentioned in the (french) manual i have, because in the manual, the note name doesn't correspond to the note number. So either one or the other is wrong.

@muggel74 I built a midibox, it is a DIY friendly project with a great community. It is easily customizable as it is under GPL license. If you don't know it already, take a look at Midibox Project

no it is not possible, but the "trim gain" function could help

Hello, i've found another way to use multiple midi controllers, and no hardware needed, only free software !

You have to use Pure Data (Win/Mac/Linux portable) and the patch i've created.
The goal here, is to have each midi controller controlling a unique submix (4 controllers to 4 ear-monitors in my case).
The patch can be easily modified for your specific needs.

I've tested it this afternoon with several USB midi controllers on a macbook, and it works perfectly for me.
The trick is : each time a midi controller starts to send messages, the patch inserts a "submix select" CC before forwarding the controller messages. PureData is fast enough to do it realtime, even when several controllers are moved at the same time ! The totamix GUI blinks fast when "Submix linked to control" option is activated, but it works.
It may not be perfect, but up to now, it looks pretty stable.
You could either use usb midi controller, or standard midi controllers on the TWO ports of the UFX
[img align=C]http://rmouneyres.free.fr/puredata/totalmixmultiple.jpg[/img]

If interested, take a look at my page and download the patch.
My Pure Data patches

I'm using pd-extended v0.42.5-extended

you're right this may work too. But i see one drawback : an individual event processor would add a "submix select" CC in between every CC message of each controller, so this would add a lot of unnecessary messages. This may work too if totalmix is ready to accept that much (i think yes), it would need some testing.
The advantage of having the multiple midi controllers connected to one brain (hardware or software) is that the messages are added only when necessary.

Thank you for the table.

I think there is one bug: CC 102 on channel 13 does not act as a toggle for Trim gain. It activates only.

CC 103 will deactivate trim gains (and thus all controler faders will be inoperant). It works in normal mode but not in "Submix linked to MIDI control" mode. In this case, CC 103 does the same as CC 102.

Second thing: Notes only work in Mackie Control Mode.

Nicolas

Well you could easily modify the patch to integrate OSC, as pure data can use OSC :
using OSC in puredata

RME staff has not confirmed.
i think that if you can duplicate the bug on your side, then it's worth opening a support ticket

At the beggining of this thread RME says "TM FX 0.98 is prepared for multiple controllers" let's see what they come with in the future !
Sure the midi is too short to get everything with a big madi setup Sysex would be great thing, but it is more work to program external devices with the messages. The cool thing a CC is it is very standardized.

I've updated my puredata patch to be able to control the submix volume with the midi controller. I have 4 remote (3 home made which are programmed the same way, and an evolution keyboard with pots), the submix controlled depends on which midi port you plug the controller. I found it very handy for live/rehersal soundchecks.
You can use any usb-midi extension with the number of midi ports you need.

Go to my page with puredata patches

hey nice to see osc is reaching totalmix

Unfortunately, Totalmix is not sending midi (and probably OSC, not tested here) data when you move a slider or select a submix when you're in standard midi mode.... so a bi-directionnal communication is not possible. So you have to take care not touching the GUI with your mouse when using remote control !

I wish RME staff would add that feature : send the midi out data when you move a slider, and the faders positions when selecting a new submix. Thant would help a lot when not using the mackie control protocol.

edit : i may probably be wrong about osc as TouchOSC is working ok when not using puredata...sorry. So something about the puredata config maybe ?

I'll try to make a video of my solution in the near future, as when two users move their controller at the same time, it is all working perfectly. Although the Totalmix window is blinking like a pulsar, the CC messages are all processed, and the audio is moving accordingly.

jerash: I have had a similar experience as you.... eventually the messages do all get processed, but it can be very slow for example, if 4 people are modifying submixes at the same time (all dragging faders). In fact, we found it unusably slow. It can take a few seconds for the Fireface to "catchup", simply because the "select submix" command has lots of overhead - just like your PULSAR description. We had 5 Behringers BCF2000's (one for each submix) connected to a custom high-speed realtime 5 channel midi merger which would intelligently keep track of which submix was last selected in order to prevent calling the command without need. When just a few "moves" were being made at a time, the setup was blazing fast, but occasionally, the musicians would all move multiple faders at once on many submixes, and the "pulsar" slows down to the point that somebody who just wants to make a quick change has to wait for all the pending changes to be processed first (in extreme cases, this can take up to 10 seconds - which is too slow for realtime use).

It would be so much more wonderful if we could do this without first "selecting submix", presumably because the TotalMix could do this in the background, without needing to change the selected submix (GUI). In fact, with this performance increase, the Fireface could very truly start competing with digital mixers for on-stage + in-studio musician monitoring, at a fraction of the cost!

Just my two cents!

Burtan: yes! 100% agree!

BTW, we have a new version coming up that has two new global OSC commands for directly selecting the desired submix. If you want to try:

https://archiv.rme-audio.de/download/tm … 986rc1.zip

https://archiv.rme-audio.de/download/tm … 986rc1.zip

https://archiv.rme-audio.de/download/os … 121020.zip

Hi,

I've just found and OSC Controller for Android.
It is not as far developed as TouchOSC, but the man behind it seems to be very active. I've already created a beta template which is similiar to the one for TouchOSC. I'll develop it further this month.

https://play.google.com/store/apps/deta … ico.dawosc

Current template: http://dawosc.forumotion.com/t39-rme-totalmixfx

Have fun!

A bit late to the party but I'm trying to create a lemur fader that will automatically select the right submix.  Have you been able to get this working?

For example I have a lemur fader set to "/1/volume3" which controls Submix 3 and I would like to add an On Expression script that sends something like:

oscout(0, "/setSubmix", 3);

I was hoping this would work but Lemur returns an error.  I'm thinking either it's not possible or my syntax is wrong.

Any ideas?

Thanks a lot that's great.  I can already select any fader (submix, input/playback/output, fader number) using Osculator and touchOSC but the multiple OSC targets of lemur is pretty useful.  I had the same floating number issue with Osculator but obviously my syntax was out at any rate.

I'm using this to set up different in-ear mixes onstage so in theory nobody should be using the totalmix window.  Hopefully that will mean the sync issue won't be a problem.

Thanks again and I agree that dedicated OSC addresses would be amazing and must be on the way at some point but it must involve a significant re-write I would have thought.