is EQ in TotalMixFX controllable via MIDI?

Did you find your answer?

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.

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

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.

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.

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)

As @Deny figured out ...

... 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??

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.

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).

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).

Do I understand correctly that I can't hard-wire knobs on a midi controller to get an analog mixer circuit with sends? something like this: I want to have 3 knobs that send the signal from mic input 1/2 to outs 3/4, 5/6, 7/8 (outs rme goes to pedal inputs). three sends to different effects pedals, one stereo pair. or one mono channel, but the point is to have 3 sends, always, on certain inputs. I planned to use the novation launchcontrol xl through the kenton usb host converter.

I don't understand how should I select the output to which I want to send the incoming signal?

Is there any way to toggle Mute groups via MIDI? The corresponding command is available for USB ARC, but I want to do it using my existing MIDI controller.

It's unfortunate RME does not make so many functions MIDI-mappable —probably an attempt to sell more ARC USBs. Meanwhile, the USB ARC is a device that could potentially be extremely versatile but RME chose to design it in such a way that it can only control TotalMix, instead of allowing buttons to be configured to transmit regular MIDI CC, note, etc messages. I was on the fence of buying one but eventually chose not to because I can't warrant the desk space.

If you don't need continuous control i.e. you just need to recall fixed values, you will have better luck using TotalMixFX Snapshots which can be recalled via MIDI, assuming you don't need many (max is a measly 8).

Yes it should be simple and I would like to see RME add the ability to create custom MIDI maps and to map most parameters, as well as the ability to use the ARC controller with third-party software. I would have bought the ARC controller but eventually I decided it was a waste of desk space. Besides, I think users would welcome a remote control with several rotary encoders not just one, to control multiple levels without having to push a button first.

Yes, i had the same point, a time ago:
Deny is right - but, maybe, he did not mention, that his findings are based on the Mackie Protocol.

It makes sense to understand what CW(Clockwise) and CCW(Counter Clockwise) means. Due to Mackie rotary endless Encoders (and "newer" Midi Specs).
Advantage1: You will never get "jumps", if you switch between the banks or busses in your sw. Thus, you can use a endless-encoder-knob for multiple functions.
Abvantage2: Professional SW/HW needs a more precise resolution. The dinosaur-MIDI Standard lets you assign 0-127=128 Values for each cc#. If you look into the Pans in TM, it offers 100 Steps to the Left and 100 to the Right (=200 Values).
Not mentioning the Volume Faders or Level meters here...
It is just my opinion, but the good old Midi Standard is more like a legacy support workaround.

I should mention at this point: I did not check the behavior of my Unit in MIDI Standalone Mode, as it is always plugged in to a Host.

So you have to enable Mackie Protocol for your Midi Controller in TMFX.
In Mackie World, you can control up to 8 Channels per controller (Plus Mastervolume). But you can move left, right, top, down (yes, not comfortable, but its the Mackie Standard).
You can assign other MIDI Controllers as Extendes to get 16 Channels at once...
-> You will see the orange channels highlited in TM FX.

If you have a endless-rotary-Poti (Knob) you can assign f.ex for 1st channel Pan (orange highlighted in TM):
on Rotation to the Left for each Step (CCW): 5 Values to Left in TM: B0 10 41 (or CH1, CC016, Value 65)
on Rotation to the Right for each Step (CCW): 5 Values to Right in TM: B0 10 01 (or CH1, CC016, Value 1)

If you have a dinosaur-Midi Controller with a "normal" Knob in Range from 0-127, like me, it depends on your Hardware...
I could achive to control the pans via midi cc#s (and some sysex/hex tweak - assigns) in my old Doepfer Drehbank (from 1992 ). Big Respect to Doepfer at this point!
But it is always a compromise, thus my controller can only send discrete values and has a limited memory for each knob.

Here is my list, i just created for you.

direct link for ff users:
https://imgbb.com/VxC4TdY

You can even play with SW (like Pocketmidi), to get a better understanding...

direct link for ff users:
https://ibb.co/cLVN6tN

No rocket-science, but i hope it helps some people.

regards, maggie

'Normal' MIDI does not deliver feedback. TM FX is not designed to be used as general MIDI controller - makes zero sense with this product. Only OSC and Mackie protocol will give feedback as its the way they work.

I'm trying to do something quite simple with my Fireface UCX 2
I want 1 fader on a midi control to set the fader volume level for the Main out
and another fader (on the same midi controller) to set the same track's fader volume but for a different submix (lets say Out 3-4)
Basically exactly how you'd have on an analog mixer 1 track being set either to main out to do an aux out
I tried the Submix link to Midi Controller 1/2/3/4 in TM
I tried the trick to have 2 windows open
But nothing works
It would be helpful to understand exactly which Channel and which CC number is mapped to each thing
if CC 102 is fader volume of track 1 in TM for main submix
what are the channel and CC numbers for the different submix ?
I find it very confusing for something that could be quite simple
thanks for your help

Hi,

If this is really all you need to do, you can go around the current midi control limitations of TMFX by:

1) Setting up your first fader to control your fader on submix no 1.
2) Setting up your second fader to same midi CC on another channel
3) Installing a midi router app that allows you to reroute midi using filters. Free example for mac: http://www.subtlesoft.square7.net/MidiPipe.html
4) Using that midi router to create two virtual in+out ports,
5) Routing fader 1 midi channel to virtual port 1, and route fader 2 to virtual port 2 + add a message converter to change the midi channel back to same channel that fader 1 uses.
6) Setting TMFX mixer window 1 to receive midi commands from midi router virtual port 1 only
7) Opening a new TMFX window and setting that to listen to midi commands from router port 2 only. You can even lock your midi remotes to control a single submix only, to avoid mistakenly changing the submix and controlling some wrong one.

This is just one example of how this can be done. Other examples include:

-Sending a bunch of midi messages from single controller in correct order. i.e. select submix, set fader level, go back to 1st submix. (this way you won’t easily get correct feedback to your faders, but you might be using a controller with non-motorized faders where this is not a problem, as they don’t have feedback anyway.) Your controller might not support sending multiple commands from a single fader, so extra software might also be needed. For example: https://www.bome.com/shop/bome-midi-translator-pro

-Using OSC / midi-osc mapping.

Hi maggie33, good to see you active!

I’m not at my studio mac right now, so I’m not a 100% sure, but if I remember correctly, you cannot remap midi channels using IAC or AMS.

The problem here being that ahnatek wants to control the same input fader on two different submixes.
Most probably the midi controller only has one ’physical’ midi port visible to Mac / AMS, so the mac cannot differentiate the two identical incoming midi CCs of the two faders controlling the same input, without manually separating them to two different channels (/commands) first, and then remapping/rerouting them one way or another. I might be wrong, of course, so feel free to correct me at any time.
But this is why I assume that at least a midi router with basic remapping functions (or a midi translator that can add the submix change in front of fader movement) is needed in this use scenario.

Another Option, just came in my mind: Isnt the Trim Function exactly what you meant ahnatek? You could also set Speaker B and Link them... And/or use the Fader groups...

bsfreq, sorry if i am wrong.

1)

Which sw (or whatever) can seperate identical MIDI CCs, with identical Channels, coming in from the same MIDI Port (HW Controller)?

2)

Me too. With the addition: The incoming Midi Messages from the HW Controller and from two different Faders/Knobs (whatever) have at least to have one different Parameter (either Channel, CC, Port, or whatever). Just to be able to seperate the Data (in whatever SW).

Trim mode can be used for relative or/and for 1-1 in-sync controlling...

---

Just an impression how you could seperate Routings by Channels in AMS:

And of course, it depends on the "Quality" of the HW-Controller itself. F. ex. I love my old Doepfer Drehbank (anno 1992) as you can totaly freely assign MIDI Messages however you want for each Knob...

Yes, absolutely d'accord. I asked, just to clarify "so the mac cannot differentiate" - no MIDI sw can differentiate this, except you have a lower access to the controller... etc...

My english isnt perfect - maybe i misunderstand some parts, sometimes. But we have generally the same view.
I generally prefer to avoid 3rd party apps if possible. Thats why i tired to experiment wit the AMS things.
Yes - you are right - AMS can just filter Channels, but no reassign/reroute them. 

Absolutly.

Although i do not use "basic" MIDI for controlling TM. But was/is always inspiring to discuss/share ideas with you.

You might need to refer to the detailed MIDI implementation section in the TotalMix FX manual for other output mappings like AN 1-12.  For AN 1-12 outputs, you can try the following mappings:
CC21 on Channel 1: AN 1 Output

CC22 on Channel 1: AN 2 Output

CC23 on Channel 1: AN 3 Output

CC24 on Channel 1: AN 4 Output

CC25 on Channel 1: AN 5 Output

CC26 on Channel 1: AN 6 Output

CC27 on Channel 1: AN 7 Output

CC28 on Channel 1: AN 8 Output

CC29 on Channel 1: AN 9 Output

CC30 on Channel 1: AN 10 Output

CC31 on Channel 1: AN 11 Output

CC32 on Channel 1: AN 12 Output

Reading the manual should (as always) help out.

Chapter 28.5 MIDI Control

Select submix (fader) in third row:
- channel 1/2: BC 68/69 xx
- channel 3/4: BC 6A/6B xx
etc.

Says it all...
Or translated into a list this would be (for Channel 1-30):