1 (edited by Deny 2016-10-29 05:20:15)

Topic: MIDI control mappings for TotalMix

Hi there,

My Behringer X-Touch Mini arrived today and I was baffled to realize I couldn't control my RME Fireface UCX with it - well, at least not the way I wanted to. Let me just start by saying I truly HATE Mackie Control protocol, I think it's stupid, unflexible and even for "midiots" it's a total disservice because it's supposed to be "plug and play" but has near zero customization options.

Here's what I initially wanted to do:
- Map the 3 first encoders to AS 1/2, AN 7/8 and AN3 hardware outputs faders;
- Map the 3 buttons right below those encoders to mute/unmute those 3 hardware outputs.

Seems simple enough, huh? After all, any studio worth its salt has multiple monitoring options that we want to be able to switch for mixing and mastering, it doesn't get more basic, useful and essential than this.

But as far as MC I couldn't come up with a solution to implement what I wanted. Even in standard mode it's not an easy task, but after a lot of tweaking and hacking I've finally come up with a solution that works and am going to share it with you guys.

So for that particular example, here's what can be done:

Instead of mapping mute buttons, which is complicated because the same MIDI channel (1) and CC messages are used for either HW Inputs, Playback and HW Outputs depending on cycling through those 3 channel groups using another MIDI CC message, what I did was store 3 snapshot mixes, each one of them with one of the 3 HW outputs unmuted, because those are directly assignable so the 3 buttons can be used as "click to select output" which is actually kinda nice.

Mix 1 (main monitors): AS 1/2 unmuted, AN 7/8 muted, AN 3 muted
Mix 2 (headphones): AS 1/2 muted, AN 7/8 unmuted, AN 3 muted
Mix 3 (Auratone): AS 1/2 muted, AN 7/8 muted, AN 3 unmuted

After storing your desired Mix Snapshots, fire up the Behringer X-Touch (note you can't open the X-Touch for programming if it's assigned to TotalMix, you need to either unassign it first or disable MIDI Control under Options).

Go to the "ENCODERS" tab, and enter the following values:
1) PUSH
   - EN1: Channel 1, Type Note, F#2, 0, 127
   - EN2: Channel 1, Type Note, G2, 0, 127
   - EN3: Channel 1, Type Note, G#2, 0, 127

2) TURN
   - EN1: Channel 9, Type CC, CC112, 0, 127
   - EN1: Channel 9, Type CC, CC108, 0, 127
   - EN1: Channel 9, Type CC, CC104, 0, 127

Go back to the "GLOBAL" tab, select "TO HARDWARE - Dump A".

Open TotalMix and under Options -> Settings set MIDI In to "X-TOUCH MINI". Leave "Enable Protocol Support" checked under "Mackie Control Options"

Make sure that "Enable MIDI Control" is turned on in the Options menu.

Done, you can now push an encoder to select an output and turn it to set the volume for that channel!

2 (edited by Deny 2016-10-29 05:38:07)

Re: MIDI control mappings for TotalMix

As the OP thread title says, I'm also going to share my findings on the MIDI control mappings for the Fireface UCX.

GLOBAL
MIDI Channel 1
Note G 1   : Global Solo
Note Ab 1  : Global Mute
Note A 1   : Show Trim

Note Gb 2  : Mix 1
Note G 2   : Mix 2
Note Ab 2  : Mix 3
Note A 2   : Mix 4
Note Bb 2  : Mix 5
Note B 2   : Mix 6
Note C 3   : Mix 7
Note Db 3  : Mix 8

==============================================================================
Note E 1   : Cycle Section Selection for Mute / Solo Actions (*)
Note F 1   : Cycle Section Selection for Mute / Solo Actions (*)
==============================================================================
The following section depends on the selected section using F 1 / E 1 notes as described above
(Hardware Inputs, Playback, Hardware Outputs). I find this way of controlling mute and solo rather cumbersome, but since I've discovered how it works here it is.
==============================================================================
    - HW Inputs
    Note Ab -2 : AS 1 Solo
    Note A -2  : AS 2 Solo
    Note Bb -2 : ADAT 3 Solo
    Note B -2  : ADAT 4 Solo
    Note C -1  : ADAT 5 Solo
    Note Db -1 : ADAT 6 Solo
    Note D -1  : ADAT 7 Solo
    Note Eb -1 : ADAT 8 Solo
    Note E -1  : AS 1 Mute
    Note F -1  : AS 2 Mute
    Note Gb -1 : ADAT 3 Mute
    Note G -1  : ADAT 4 Mute
    Note Ab -1 : ADAT 5 Mute
    Note A -1  : ADAT 6 Mute
    Note Bb -1 : ADAT 7 Mute
    Note B -1  : ADAT 8 Mute

    - Playback
    Note Ab -2 : SPDIF Solo
    Note A -2  : AS 1 Solo
    Note Bb -2 : AS 2 Solo
    Note B -2  : ADAT 3 Solo
    Note C -1  : ADAT 4 Solo
    Note Db -1 : ADAT 5 Solo
    Note D -1  : ADAT 6 Solo
    Note Eb -1 : ADAT 7/8 Solo
    Note E -1  : SPDIF Mute
    Note F -1  : AS 1 Mute
    Note Gb -1 : AS 2 Mute
    Note G -1  : ADAT 3 Mute
    Note Ab -1 : ADAT 4 Mute
    Note A -1  : ADAT 5 Mute
    Note Bb -1 : ADAT 6 Mute
    Note B -1  : ADAT 7/8 Mute

    - HW Outputs
    Note E -1  : AS 1 Mute
    Note F -1  : AS 2 Mute
    Note Gb -1 : ADAT 3 Mute
    Note G -1  : ADAT 4 Mute
    Note Ab -1 : ADAT 5 Mute
    Note A -1  : ADAT 6 Mute
    Note Bb -1 : ADAT 7/8 Mute   
==============================================================================


HARDWARE INPUTS
MIDI Channel 1
CC16 : Mic 1 Pan : Left (-) 63 (+) Right
CC17 : Mic 2 Pan : Left (-) 63 (+) Right
CC18 : AN 3 Pan : Left (-) 63 (+) Right
CC19 : AN 4 Pan : Left (-) 63 (+) Right
CC20 : AN 5 Pan : Left (-) 63 (+) Right
CC21 : AN 6 Pan : Left (-) 63 (+) Right
CC22 : AN 7 Pan : Left (-) 63 (+) Right
CC23 : AN 8 Pan : Left (-) 63 (+) Right

CC102 : Mic 1 Fader : 0 - 127
CC103 : Mic 2 Fader : 0 - 127
CC104 : AN 3 Fader : 0 - 127
CC105 : AN 4 Fader : 0 - 127
CC106 : AN 5 Fader : 0 - 127
CC107 : AN 6 Fader : 0 - 127
CC108 : AN 7 Fader : 0 - 127
CC109 : AN 8 Fader : 0 - 127
CC110 : SPDIF L Fader : 0 - 127
CC111 : SPDIF R Fader : 0 - 127
CC112 : AS 1 Fader : 0 - 127
CC113 : AS 2 Fader : 0 - 127
CC114 : ADAT 3 Fader : 0 - 127
CC115 : ADAT 4 Fader : 0 - 127
CC116 : ADAT 5 Fader : 0 - 127
CC117 : ADAT 6 Fader : 0 - 127

MIDI Channel 2
CC102 : ADAT 7 Fader : 0 - 127
CC103 : ADAT 8 Fader : 0 - 127


SOFTWARE PLAYBACK
MIDI Channel 5
CC102 : AN 1 Fader : 0 - 127
CC103 : AN 2 Fader : 0 - 127
CC104 : AN 3 Fader : 0 - 127
CC105 : AN 4 Fader : 0 - 127
CC106 : AN 5 Fader : 0 - 127
CC107 : AN 6 Fader : 0 - 127
CC108 : AN 7 Fader : 0 - 127
CC109 : AN 8 Fader : 0 - 127
CC110 : SPDIF L Fader : 0 - 127
CC111 : SPDIF R Fader : 0 - 127
CC112 : AS 1 Fader : 0 - 127
CC113 : AS 2 Fader : 0 - 127
CC114 : ADAT 3 Fader : 0 - 127
CC115 : ADAT 4 Fader : 0 - 127
CC116 : ADAT 5 Fader : 0 - 127
CC117 : ADAT 6 Fader : 0 - 127

MIDI Channel 6
CC102 : ADAT 7 Fader : 0 - 127
CC103 : ADAT 8 Fader : 0 - 127


HARDWARE OUTPUTS
MIDI Channel 1
Note Gb 1  : Main Mono
Note D 2   : Speaker B
Note A 5   : Main Dim

MIDI Channel 9
CC102 : AN 1 Fader : 0 - 127
CC103 : AN 2 Fader : 0 - 127
CC104 : AN 3 Fader : 0 - 127
CC105 : AN 4 Fader : 0 - 127
CC106 : AN 5 Fader : 0 - 127
CC107 : AN 6 Fader : 0 - 127
CC108 : AN 7 Fader : 0 - 127
CC109 : AN 8 Fader : 0 - 127
CC110 : SPDIF L Fader : 0 - 127
CC111 : SPDIF R Fader : 0 - 127
CC112 : AS 1 Fader : 0 - 127
CC113 : AS 2 Fader : 0 - 127
CC114 : ADAT 3 Fader : 0 - 127
CC115 : ADAT 4 Fader : 0 - 127
CC116 : ADAT 5 Fader : 0 - 127
CC117 : ADAT 6 Fader : 0 - 127

MIDI Channel 10
CC102 : ADAT 7 Fader : 0 - 127
CC103 : ADAT 8 Fader : 0 - 127

Re: MIDI control mappings for TotalMix

is EQ in TotalMixFX controllable via MIDI?

4 (edited by ramses 2019-04-12 07:52:19)

Re: MIDI control mappings for TotalMix

Wondering about 2 things, could you kindly explain ?

Why are there so many differencies to the handbook ?
And why is this list longer than in the handbook on page 71 ?

To put one example:
Your list: Note Gb 2  : Mix 1
Handbook: Snapshot 1: #F 3

BR Ramses
UFX+, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1650v4, Win10Pro22H2, Cub12Pro

Re: MIDI control mappings for TotalMix

jaynyc wrote:

is EQ in TotalMixFX controllable via MIDI?


Did you find your answer?

Re: MIDI control mappings for TotalMix

jaynyc wrote:

is EQ in TotalMixFX controllable via MIDI?

No, only via the OSC protocol or Totalmix Remote.

Regards,
Audio AG Support

Re: MIDI control mappings for TotalMix

Hey there,

The Totalmixer expects simple CC's for the faders and send at the same time pitchbend back to the control unit.
Should that not be the same?
I would need an crazy amount of single mappings to translate it in a understandable format for my Midi Twister.

https://www.dropbox.com/s/hjm694qykrbzx … k.mov?dl=0

I just checked a few:

102 on Ch 9 moves the left Fader in the lower row and the feedback coming from TMix is Pitch on Ch 6 and Sysex Ch 1

108 on Ch 9 moves the third Fader in the lower row and the feedback coming from TMix is absolutely the same like before

111 on Ch 9 moves the first Phones Fader in the lower row and there is no feedback at all


My goal is, to get a propper feedback for my DJ Tech Midi Twister Fighter.
When I change the Presets of the Totalmixer, the LEDs should show the new current state of faders and move it from there current positions.

8 (edited by vvilms 2021-06-17 07:55:49)

Re: MIDI control mappings for TotalMix

So as I've run out of snapshots, I'm curious to know how one might go about adjusting faders for sub-mixes via MIDI or OSC. I don't see anything about changing the hardware output the faders ("Bx yy zz") are set to address (ie. page 87 of the UFX+ manual).

Re: MIDI control mappings for TotalMix

Hello.  Looking for midi command to be able to assign a button to enable/disable MUTE GROUP 4 please?

10 (edited by extracurriculars 2021-11-28 09:29:40)

Re: MIDI control mappings for TotalMix

thank you so much for this workaround!

drives me nuts that I can't have dedicated mute buttons though. would be soooo helpful.

if they could just implement a special midi cc for mute on Phones and Main I would be so happy. Fine to use mackie control for the rest, but those 2 should have their own dedicated commands.

A nice alternative if you're only using 2 main ouputs instead of 3 is to use Speaker B to switch back and forth instead of the snapshots. Though you can't set your submixes independently when you do that.

11 (edited by ekg 2022-04-14 23:08:01)

Re: MIDI control mappings for TotalMix

Hey fellas,
I use Midi remote control in my rig ALL the time. I wanted to have a look at the solo function, because that would be super useful. The documentation of Midi remote in RME's manual is somewhat unsatisfying. so I tested and tested and now I want to share my findings.
GOOD NEWS:
Indeed is it possible to control Solo & mute via midi.
the downside of this is, that there is no "hardwired" Midi command to a specific tracks.
The logic inside Totalmix is different and very flexible.
Midi Control of Sends and Mutes are ALWAYS referring to a "BANK" of 8 channels. Just like you would control them via a Mackie Control or something similar, where you have 8 faders.
you have midi commands to move that bank around and you can visualise them, when you turn on the midi out. I'll attach a screenshot.

https://drive.google.com/file/d/1HmEm4Y5joesHCqyY1UeRTcgJMgnqQpfL/view?usp=sharing

Here are my findings in an excel sheet and a pdf with the corresponding Midi Commands
https://drive.google.com/drive/folders/ … sp=sharing

I was confused with the Midi Note naming, the official syntax is one octave higher than in Ableton Live. So, a F#2 in the manual is a F#1 in Ableton.


little sidenote about faders:
Same goes for fader control and CC's: they are not fixed. They are always reflecting what visible in the Totalmix GUI. So if you change the Channel Layout and hide tracks, everything moves to the left..... (I hope that is clear enough)

@RME: Are there more "hidden" MIDI Commands? To build a remote which would be bullet proof, it would nessecary to "reset" the selected bank. Like E7: Move selected Bank to Hardware Input 1. I could not find any "fixed" reference point.

12

Re: MIDI control mappings for TotalMix

I don't see 'hidden' MIDI commands. All this is built on Mackie protocol, so there is no surprise on what you discovered  Mackie requires a NDA (not sure if that is still the case). So we can not disclose all the Mackie specific details. Even OSC support is mainly built on this Mackie bank design.

Regards
Matthias Carstens
RME

13 (edited by ekg 2021-12-16 13:54:01)

Re: MIDI control mappings for TotalMix

Thank you Matthias for your reply.
Now that you point it out that the midi remote is based on the Mackie Protocol it makes perfectly sense.
But the Midi commands for MUTE & Solo, moving selected channels etc are not mentioned or explained in the manual. That is why I said hidden....

And I wondered if there are more commands implemented from the Mackie Protocol other than mentioned in the manual.... (e.g for Notes E4-A6)

14

Re: MIDI control mappings for TotalMix

Definitely. And I just explained why. We dared to publish the most easy to find and defined MIDI notes as those can't be covered by an NDA whatsoever. But had to stop there.

Regards
Matthias Carstens
RME

Re: MIDI control mappings for TotalMix

As @Deny figured out ...

Deny wrote:

Note E 1   : Cycle Section Selection for Mute / Solo Actions (*)
Note F 1   : Cycle Section Selection for Mute / Solo Actions (*)

... TotalMix maintains a concept of "Focus" (my term) on one of the three groups of channels (Hardware Inputs, Software Playbacks, and Hardware Outputs). The MIDI commands Note On E2 and Note On F2 (with C4 = Middle C = MIDI 60) change the focus to the next / previous group.

Many of the commands found by @Deny (and more that I have located) operate on the channels in the group that currently has focus.

Question is: Is there any visual feedback on the TotalMix interface that indicates which group currently has focus??

16

Re: MIDI control mappings for TotalMix

Deny wrote:

Question is: Is there any visual feedback on the TotalMix interface that indicates which group currently has focus??

+1 !
this would be of high interest for me!!
or a "reset to first channel, first row" would be also perfect!

Re: MIDI control mappings for TotalMix

Well, @ekg, I've been working on my own spreadsheet, collecting info from a (meager) number of sources.

I noticed that the spreadsheet you linked to on your Google drive is no longer a valid link ... could you provide an updated link to your latest XLS? I will do likewise when I've got mine in publishable shape ...

At this point, I'm really going for auto-control from a live performance DAW (Cantabile) to I can basically switch various instruments into and out of "TotalMix Direct Monitoring" mode - in order to minimize latency. (I'm doing the Rig-setup for the piano guy, who is pretty sensitive to latency ...) ... So, it is likely I can get away with using snapshots rather than fine-grained control over every item.

18

Re: MIDI control mappings for TotalMix

Clint Goss wrote:

Well, @ekg, I've been working on my own spreadsheet, collecting info from a (meager) number of sources.

I noticed that the spreadsheet you linked to on your Google drive is no longer a valid link ... could you provide an updated link to your latest XLS? I will do likewise when I've got mine in publishable shape ...


Oh yes, I had a major google drive meltdown. all my shared links are gone..... But I update mine in the post obove.

19 (edited by Clint Goss 2022-04-26 12:01:29)

Re: MIDI control mappings for TotalMix

I've just done some testing, and it seems that TotalMix does not take any action on Note On messages.

It looks like, based on my limited testing, that only a Note Off command is required to trigger an event (I'm working with Snapshot-Change actions).

20

Re: MIDI control mappings for TotalMix

that is strange.
Do you have the protocol support enabled? That did the trick for me once.
If it is not, it does not react to the snapshot commands and mute etc....

Re: MIDI control mappings for TotalMix

I do have Protocol Support enabled. And snapshot commands are working.

It's just that I found out that TotalMix responds only to Note Off commands (aka Note commands with Velocity=0). TotalMix seems to ignore Note On commands (i.e. Note commands with Velocity > 0).

22 (edited by GKrazzhoopper 2022-06-30 00:39:56)

Re: MIDI control mappings for TotalMix

I don´t get the point... With the help of you I finally realise my problem. It seemed to be impossible to set mute/solo buttons to a midi controller well. And now I finally have to realize: It is impossible indeed!

The "focus concept" is never mentioned (instead of here) and with all the possibillities of 16 midi channels I cannot understand, why we couldn´t have all keys for each midi channel or just an "click and move" remote solution like in most DAWS. I have to change the focus in the TotalMix window instead of simply mute or solo my channel on my midi controller. Honestly? I feel kind of anger for that solution at an highend Interface. Please patch it...