TURN EN 6 CC 1 CC21 Relative3 - PAN PAN TRACK 6 TURN EN 5 CC 1 CC20 Relative3 - PAN PAN TRACK 5 TURN EN 4 CC 1 CC19 Relative3 - PAN PAN TRACK 4 TURN EN 3 CC 1 CC18 Relative3 - PAN PAN TRACK 3 TURN EN 2 CC 1 CC17 Relative3 - PAN PAN TRACK 2 TURN EN 1 CC 1 CC16 Relative3 - PAN PAN TRACK 1 PUSH EN 8 NOTE 1 D#1 - MOMENTARY SELECT TRACK 8īT 1 NOTE 1 G#-2 - MOMENTARY SOLO TRACK 1īT 2 NOTE 1 A-2 - MOMENTARY SOLO TRACK 2īT 3 NOTE 1 A#-2 - MOMENTARY SOLO TRACK 3īT 4 NOTE 1 B-2 - MOMENTARY SOLO TRACK 4īT 5 NOTE 1 C-1 - MOMENTARY SOLO TRACK 5īT 6 NOTE 1 C#-1 - MOMENTARY SOLO TRACK 6īT 7 NOTE 1 D-1 - MOMENTARY SOLO TRACK 7īT 8 NOTE 1 D#-1 - MOMENTARY SOLO TRACK 8 PUSH EN 7 NOTE 1 D1 - MOMENTARY SELECT TRACK 7 PUSH EN 6 NOTE 1 C#1 - MOMENTARY SELECT TRACK 6 PUSH EN 5 NOTE 1 C1 - MOMENTARY SELECT TRACK 5 PUSH EN 4 NOTE 1 B0 - MOMENTARY SELECT TRACK 4 PUSH EN 3 NOTE 1 A#0 - MOMENTARY SELECT TRACK 3 PUSH EN 2 NOTE 1 A0 - MOMENTARY SELECT TRACK 2 PUSH EN 1 NOTE 1 G#0 - MOMENTARY SELECT TRACK 1 Also, I haven't tested the F1-8 functions yet hopefully they will work.ĬONTROL TYPE CHANNEL NO. One challenge that I ran into was that Premier Pro (and presumably Audition) did not recognize many of the valid commands such as Solo, so I only had a few that I could map. I used a couple of Mackie Control/MIDI tables that I found online, and also used the MIDI Monitor window in Presonus Studio One to view the commands from the board while it was in MC mode. Apply the settings using the X-Touch Editor software (download from ). You'll want to copy this into a text editor so that the tabs will render correctly (or download the attached text file). !(upload://b1aJdYwg9kuZbOjLUOHdGrJdR7m.In case it helps someone save time figuring it all out, here's my MIDI map for the Behringer X-Touch Mini. You will need to edit the aliases to the controller and application ports you are using. I’ve attached a diagram of the proper setup to do this as well as an example project file. Please be sure to annotate which fader you are moving and the resultant fader movement in ATEM within the log capture so that we can adjust appropriately. Then you can turn on logging and we can have a look. What you need to do for me to be able to help is set up Bome MIDI Translator with your MIDI controller as input and the ATEM application as output (IE Bome MIDI Translator 1) and visa versa with the routing as shown below. I’m not that familiar with ATEM capabilities but if you can monitor the MIDI messages that are being sent with your controller that moves your faders (using the logging capability of Bome MIDI Tranlsator) then we can certainly translate these messages the way you want them. I believe the ATEM OSC bridge only works on Mac. There is software you can get for your ATEM to accept OSC messages and then you can use OSCulator to translator MIDI to the OSC message of your choice (whatever the ATEM OSC bridge accepts). Now, if the ATEM does not allow for direct MIDI control of the faders,Īnd you are running OSCulator. If the ATEM allows for direct MIDI input, and the sliders are already defined MIDI messages, then yes.įor instance if ATEM allows for Mackie MCU MIDI control of the faders, then we can use Bome MIDI Translator to translate the fader 5 mackie MCU message to the fader 1 MCU message and so forth.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |