Control surface encoders for x, y and z parameters of selected property in the effects control panel

[slovill]

I'm looking for more functionality from the Behringer X-Touch control surface and hope it is possible to bind inputs from the control surface encoder knobs at the top of the fader bank to x, y, and z values for a selected property in the effects control panel.

It is easy enough to map a single encoder to change a selected value, but I'd like to, for example, press the EQ button under Encoder Assign (red box, upper right), which will pre-select the first property in the Premiere Pro Effects Panel, unless a property is already selected; also, set the first three encoders on the X-Touch (8 encoders, yellow box) are bound to the x, (y, and z if there) values, and the fourth encoder is set up to navigate up and down the effects panel, choosing properties with x,y,z numeric values or a selection list. For fields with a selection list, if the x value encoder doesn't work, then the fifth encoder could be employed, leaving 6, 7 and 8 for future use.

If other Encoder Assign banks (red box) could be accessed beyond EQ (that being Send, Plugin & Inst), then three more banks of 8 could be opened up for whatever - such as Lumetri controls or color selection.

Would a combination of Adobe ExtendScript and Bome Midi Translator Pro do the job? I use the Bome software to use the X-Touch as a DMX light control board, but could something similar be done to control the Effects Control Panel in Premiere Pro (and After Effects)?

This idea could work on other control surfaces, such as those used for live-streaming, or even the configurable/programmable touch-screen control surfaces for tablets.

[slovill]

The encoder assign buttons - if they can be utilized - the first two are utilized by Premiere Pro already - the TRACK and PAN/BALANCE assignments, with the PAN/BALANCE assignment being the only one that actually change something in Premiere Pro. The EQ button lights up, but the encoders have no apparent function. It would be cool to have the EQ assignment button set up control of the track effects in the audio track mixer, the SEND assignment button set up control of the Effects Controls panel, the PLUG-IN assignment to control the Properties Panel and the INST assignment to control the Lumetri panel.

Anyway, here's a start from Grok:

First Prompt:

I would like to use the encoders, faders and jog wheel on a Behringer X-Touch control surface to navigate, edit and keyframe properties in the Adobe Premiere Pro Effects Controls panel. I would like to use Bome Midi translator to use the Encoder Assign buttons on the control surface to change the functions of the encoders. I would like to use the cursor keys next to the jog wheel on the control surface to navigate between different effects and values to be edited in the Premiere Pro Effects Control panel. For example: pressing the EQ button in the Encoder Assign section of the control surface would statically assign the first three encoders to the x, y and z values of a property selected in the Premiere Pro Effects Control panel, the fourth encoder would navigate the Effects Control panel and select which property values (x, y and z) the encoders will control.

 First Response:

15 web pages

To integrate the Behringer X-Touch control surface with Adobe Premiere Pro for controlling effects through the Effects Controls panel using Bome MIDI Translator, you can follow these steps based on available information:

Setup and Configuration:

1. Behringer X-Touch Configuration:
   • Startup Mode: Turn on the X-Touch while holding the "Select" button above the first fader to set it to boot in Mackie or HUI mode. Choose Mackie Control (MC) mode for compatibility with Premiere Pro. This setting allows the device to connect via USB or MIDI.
2. Adobe Premiere Pro Configuration:
   • Navigate to Edit > Preferences > Control Surface in Premiere Pro. Add a Mackie device, ensuring both inputs and outputs are set to "X-Touch".
   •  
   • [NOTE: This is wrong! If using Bome Midi Translator, Premiere Pro needs to look at Bome MIDI Translator Virtual MIDI Port, usually called BMT1)

Using Bome MIDI Translator:

• Mapping Encoders and Functions:
  • Encoder Assign Buttons: Use Bome MIDI Translator to map the Encoder Assign buttons on the X-Touch. For example, when you press the "EQ" button, it should send MIDI commands that Bome interprets to change the functionality of the first three encoders to control the X, Y, and Z values of a selected property in the Effects Control panel. The fourth encoder would be mapped to scroll through the properties or effects, allowing you to select which property (X, Y, Z) the other encoders will adjust.
  • Translators for Properties:
    • Create translators in Bome MIDI Translator where each encoder's movement translates to a specific keyboard or mouse action in Premiere Pro. For example:
      • Encoder 1 moves might translate to adjusting "X" value via specific hotkeys or mouse movements if Premiere supports direct value changes through keyboard inputs.
      • Encoder 2 and 3 similarly for "Y" and "Z".
  • Cursor Keys and Jog Wheel:
    • Map the cursor keys next to the jog wheel to navigate through the Effects Controls panel. These could mimic the function of arrow keys for moving between effects or properties.
    • The jog wheel can be assigned to scroll through the panel or adjust values finely, depending on how you map it in Bome MIDI Translator.

Implementation Tips:

• Static vs. Dynamic Mapping: Your setup involves static assignments where pressing an assign button changes the function of the encoders to specific parameters. However, you might need to script or use advanced rules in Bome for dynamic changes based on the currently selected effect or property in Premiere Pro, as direct feedback from Premiere to Bome isn't standard.
• Testing and Feedback:
  • After setting up, test extensively because Premiere Pro's interaction with MIDI control surfaces can be nuanced. You might need to tweak mappings based on real-time feedback to achieve the desired control over effects.
• Premiere Pro's MIDI Support: Keep in mind that Premiere Pro's support for MIDI control might be limited to basic transport and mixing controls out of the box. Your setup with Bome MIDI Translator essentially extends this by translating MIDI to keyboard/mouse actions, which Premiere Pro understands better.

Sources Consulted:

• Information from Adobe Community discussions on integrating Behringer X-Touch with Premiere Pro.
• Bome MIDI Translator documentation for setting up custom MIDI mappings.

This setup should provide a solid foundation for controlling effects in Premiere Pro, although some trial and error might be necessary to perfectly align the control surface with the software's capabilities. If you encounter issues or need more specific mappings, consulting further with the Adobe or Bome user communities might yield additional insights or solutions.

Second Prompt:

could navigation between the different properties and fields be assigned to a midi note? This way the encoders on the control surface are statically assigned to the x, y, and z fields, but dynamically assigned to a particular property with x, y and z values (or only x).

Second Response:

Yes, you can assign navigation between different properties and fields in Premiere Pro's Effects Panel to MIDI notes using a setup like Bome's MIDI Translator. Here's how this could work:

Concept:

1. Static Encoder Assignment: Each encoder on your MIDI control surface would have a fixed function, like adjusting the X, Y, or Z value of some property.
2. Dynamic Property Selection: MIDI notes would be used to switch which property these encoders are controlling. For example:
   • Pressing MIDI note 60 might switch the encoders to control the Position effect's X, Y, and Z.
   • Pressing MIDI note 61 might switch them to control the Scale effect's X, Y, and Z.

Implementation Steps:

1. Bome's MIDI Translator Setup:

• MIDI Note to Switch Properties:
  • Set up triggers for each MIDI note you want to use for switching. When a note is pressed, it triggers a preset change or script execution in Bome's.
• Encoder Configuration:
  • Configure each encoder to send MIDI control change (CC) messages. These CC messages would be consistent for each encoder (e.g., Encoder 1 always sends CC#1, Encoder 2 sends CC#2, etc.).
• Presets for Each Property:
  • Create a preset for each property group you want to control. Each preset would define which script or command runs for each CC received, based on which property group is currently selected.

2. ExtendScript for Premiere Pro:

Here's how you might structure an ExtendScript to handle this:

javascript

// Assume this script is called when a MIDI note is pressed to switch properties
function switchToProperty(propertyName) {
    var mySequence = app.project.activeSequence;
    var clips = mySequence.videoTracks[0].clips;
    
    if (clips.length > 0) {
        var clip = clips[0];
        var effect = clip.getComponent("Transform"); // Example effect, change as needed
        
        if (effect) {
            var property = null;
            
            switch(propertyName) {
                case "Position":
                    property = effect.properties.getByName("Position");
                    break;
                case "Scale":
                    property = effect.properties.getByName("Scale");
                    break;
                // Add more cases for other properties as needed
            }
            
            if (property) {
                // Store this property for later use or return it
                return property;
            }
        }
    }
    return null;
}

// This function would be called by each encoder's CC message
function adjustProperty(property, dimension, value) {
    if (property) {
        // Adjust the specific dimension (X, Y, Z) based on MIDI input
        // Assuming value is normalized (0-127) and we're converting to something meaningful
        var adjustedValue = (value / 127) * 100; // Example normalization
        
        switch(dimension) {
            case "X":
                property.setValueAtKey(1, [adjustedValue, property.value[1], property.value[2]]);
                break;
            case "Y":
                property.setValueAtKey(1, [property.value[0], adjustedValue, property.value[2]]);
                break;
            case "Z":
                property.setValueAtKey(1, [property.value[0], property.value[1], adjustedValue]);
                break;
        }
    }
}

// Example usage:
var currentProperty = switchToProperty("Position"); // Triggered by MIDI note
adjustProperty(currentProperty, "X", 64); // Triggered by Encoder 1 moving, for example

3. Integrating with Bome's:

• Each MIDI note would call switchToProperty with the appropriate property name.
• Each encoder's CC message would call adjustProperty with the current property, the dimension (X, Y, Z), and the MIDI value.

Considerations:

• Performance: Script execution can impact performance if done very frequently or for complex setups.
• Error Handling: Ensure scripts handle cases where effects or properties might not be available.
• User Interface: Users will need to understand which note corresponds to which property, perhaps using visual feedback or documentation.

This setup provides dynamic control over different properties of effects in Premiere Pro using MIDI, enhancing your control surface's functionality while maintaining a consistent interface for value adjustment across different properties.

[slovill]

The latency introduced by the several software layers required to make MIDI inputs something that ExtendScript can understand and transmit to Premiere Pro is unacceptable. Instead, using the SDK to write a custom plug-in would be the way to go, but I don't have the chops for that. Maybe somebody who can code will have a similar idea someday.

In the meantime, I'm just going to use Bome MIDI translator to do a simple version. Here is action=keystroke=control surface list.

Navigate to and select values in selected panel = [TAB],  [SHIFT][TAB] = Encoder knob 1

Change selected value (coarse) = [SHIFT][UP ARROW], [SHIFT][DOWN ARROW] = Encoder knob 2

Change selected value (normal) = [UP ARROW], [DOWN ARROW] = Encoder knob 3

Change selected value (fine) = [SHIFT][UP ARROW], [SHIFT][DOWN ARROW] = Encoder knob 4

Here is one answer from Grok about how this can be done. Note: replace example keyboard shortcuts with your choice. I've not tried yet, but will add a post later with results:

Prompt:

can you help build a practical example in Bome MIDI Translator Pro that would keep normal function for the X-Touch encoders when the encoder assign selected is 'track' or 'pan/balance'; but when the 'eq' encoder assign is selected the encoder output changes to a keystroke instead of their normal function. This will be for integrating keyboard shortcuts in Adobe Premiere Pro.

Response:

Here's a practical example for Bome's MIDI Translator Pro to handle the integration of keyboard shortcuts in Adobe Premiere Pro, specifically for when the X-Touch's encoder assignment switches to 'EQ':

Here's a practical example for Bome's MIDI Translator Pro to handle the integration of keyboard shortcuts in Adobe Premiere Pro, specifically for when the X-Touch's encoder assignment switches to 'EQ':

Setup:

1. Hardware Setup:
   • Connect your X-Touch to your computer, ensuring it's sending MIDI signals.
2. Adobe Premiere Pro Configuration:
   • Define or know the keyboard shortcuts in Premiere Pro that you want to trigger for EQ adjustments. For example:
     • Ctrl + Shift + E for increasing bass frequency
     • Ctrl + Shift + R for increasing mid frequency, etc.
3. Bome's MIDI Translator Pro Configuration:
   
   
   • Create a New Project:
     • Start by creating a new project in Bome's.
   • Define Presets for Each Encoder Assignment:
     • Preset for 'Track' and 'Pan/Balance':
       • These should pass through MIDI signals without modification.
     • Preset for 'EQ':
       • Here, you'll map MIDI signals to keystrokes for Premiere Pro.
   • Global Incoming Triggers:
     • Set up triggers for mode switching on the X-Touch.
   • Global Variables:
     • Use a global variable to keep track of the current mode, let's call it currentMode.

Steps in Bome's:

Step 1: Define Mode Switching

• Incoming Trigger for Mode Switch:
  • Assuming 'EQ' mode sends PC 1, 'Track' sends PC 2, and 'Pan/Balance' sends PC 3.

plaintext

Incoming Trigger:
  - Type: Program Change
  - Channel: X-Touch's MIDI Channel (e.g., 1)
  - PC Value: 1 (for EQ), 2 (for Track), 3 (for Pan/Balance)

Rules:
  - For PC 1: currentMode = "eq"
  - For PC 2: currentMode = "track"
  - For PC 3: currentMode = "pan"

Step 2: Encoder Behavior for 'Track' and 'Pan/Balance'

• These modes should pass MIDI signals directly to Premiere Pro without any modification.

Step 3: Encoder Behavior for 'EQ' in Premiere Pro

• Incoming Trigger for Encoders:
  • Capture the CC messages from the encoders. Let's say Encoder 1 sends CC#1, Encoder 2 sends CC#2, etc.

plaintext

Incoming Trigger for Encoder 1 (Bass EQ):
  - Type: Control Change
  - Channel: X-Touch's MIDI Channel
  - CC#: 1

Rules:
  - if currentMode == "eq" then proceed, else exit rules, skip Outgoing Action

Outgoing Action:
  - Type: Keystroke
  - Key: Ctrl+Shift+E (for increasing bass frequency)
  - [x] Repeat active for continuous control

Incoming Trigger for Encoder 2 (Mid EQ):
  - Type: Control Change
  - Channel: X-Touch's MIDI Channel
  - CC#: 2

Rules:
  - if currentMode == "eq" then proceed, else exit rules, skip Outgoing Action

Outgoing Action:
  - Type: Keystroke
  - Key: Ctrl+Shift+R (for increasing mid frequency)
  - [x] Repeat active for continuous control

Incoming Trigger for Encoder 3 (Treble EQ):
  - Type: Control Change
  - Channel: X-Touch's MIDI Channel
  - CC#: 3

Rules:
  - if currentMode == "eq" then proceed, else exit rules, skip Outgoing Action

Outgoing Action:
  - Type: Keystroke
  - Key: Ctrl+Shift+T (for increasing treble frequency)
  - [x] Repeat active for continuous control

// Repeat for each encoder you want to control different EQ parameters with different shortcuts

Additional Considerations:

• Keystroke Mapping: Ensure these shortcuts match what Premiere Pro uses for adjusting EQ. You might need to define custom shortcuts in Premiere Pro if the default ones don't match your needs.
• Performance: Test the repeat rate of keystrokes to ensure smooth control over Premiere Pro's EQ without overwhelming the application.
• Testing:
  • Verify that in 'Track' and 'Pan/Balance' modes, Premiere Pro responds to MIDI normally.
  • In 'EQ' mode, confirm that turning encoders send the correct keyboard shortcuts to Premiere Pro.
• Save Preset: Save this configuration as a preset for reuse or future modifications.

This setup will allow you to use your X-Touch in different operational modes, where 'EQ' mode specifically triggers keyboard shortcuts in Adobe Premiere Pro for EQ adjustments, enhancing your control over audio editing with a hardware interface.

[R Neil Haugen]

Reading this, just made me so glad I've got a Tangent Elements panel, as i can map most anything, anywhere in Premiere, to the buttons, knobs, and wheels of that panel via simple actions selecting the options in Tangent's mapping software.

It's actually easier than what you're showing here to map their panels, in Resolve, out of Resolve's native mapping, with Tangent's "Warp Engine" software.

[slovill]

I hear ya, brother. And the Tangent excels in Resolve. Luckily I already know Bome MIDI Translator from DMX stuff, and the X-Touch makes a decent light board! The only reason I wanted to involve scripting or SDK was to dynamically get property labels and values to display in the scribble strip and timecode display on the X-Touch. But now, avoiding ExtendScript and the SDK keeps things pretty simple and tedious, just like mapping most any other control surface.

The Mackie options in preferences are too limiting, so one needs Bome in the middle and keyboard shortcuts to expand functionalty of the X-Touch in Adobe.

Bome can get a bit heavy with the massive heap of MIDI spaghetti. I'm using Grok to twirl the spaghetti and spit out the meatballs I need for Bome, and I figured a way to make the previously underutilized Encoder Assign buttons do something cool, and how to write to the scribble strips, but only static text. Dynamic values require scripting, which is too slow anyway, or the SDK to make a custom plug-in, but 'ain't nobody got time for that.'

I'll post what I found after I reformat and clean up the Grok session. Then, after I get the Bome translators all tweaked in I'll post the file here for others to add to, or use as a start for their own control surface, or just use if they have an X-Touch.

[slovill]

Here is what I came up with:

Keep things simple. Use Bome MIDI Translator to intercept and translate MIDI from the X-Touch to keystrokes for Adobe keyboard shortcuts. But to keep the regular audio control surface functionality Bome needs to know some way of knowing which mode - audio or effects control - you want to be in. On the X-Touch are six buttons under the header Encoder Assign. While connected to Premiere Pro, only the first three, TRACK, PAN/BALANCE and EQ toggle on their lights, and even then, the EQ button doesn't seem to do anything useful. Maybe that's the magic button.

Using Grok AI to help sift through the MIDI data and determine which MIDI values to use in Bome MIDI Translator, the result is pretty flexible. Pressing the [EQ] button triggers Bome MIDI Translator Pro to senkeyboard shortcuts to Adobe instead of MIDI strings, and it also triggers Bome to send new text to display in the scribble strips. When I get the Bome file tweaked in I will post it here. The file will also include translators to change the background color of the X-Touch scribble strips LCD's, assigned to keyboard shortcuts. But for now, I'm just going to post the conclusions reached while using Grok here. If you'd like to see the whole Grok AI session, including all the MIDI captures from the X-Touch (which takes up most of the pages), it can be seen here: Grok Session-X-Touch and Adobe

And here is the conclusive stuff:

New Prompt:

Objective: To configure Bome MIDI Translator Pro (BMT) for using the Behringer X-Touch (Logic Control) with Adobe Premiere Pro, particularly for switching between audio mixing and video effects control modes. 

 
Key Points and Findings: 

Control Surface Setup: Encoder Assign Buttons (like EQ, Track, Pan/Balance): These are momentary switches that trigger state changes, often indicated by B0 Control Change (CC) messages alongside Note On/Off messages. 

The EQ button (B0 4B 05, B0 4A 11) was considered for switching to an "Effects Control" mode where controls would map to Premiere Pro shortcuts. Track and Pan/Balance buttons have unique B0 messages that could be used for mode verification or switching.  

Other Controls: Scrub Button: Momentary, toggling something (like a light) but without distinct MIDI state changes for on/off (90 65 7F for press, 90 65 00 for release). Not ideal for mode switching due to lack of unique MIDI messages for different states.  

Magnifier Button: Also a momentary button, toggling a light with Note On/Off messages (90 64 7F for on, 90 64 00 for off). No B0 messages, suggesting direct control rather than mode switching.  

BMT Configuration: Mode Switching: Use unique B0 messages from Encoder Assign buttons for switching profiles or modes. 

Direct Control: Use Note On/Off messages for controls like Scrub or Magnifier for direct command execution in Premiere Pro. 

Feedback Management: Ensure BMT ignores feedback or echoes to prevent unintended actions. 

State Management: Use BMT to keep track of control states or modes when direct MIDI feedback isn't available for state changes. 

Next Steps:  

Capture MIDI Streams: capture streams to ensure clarity in MIDI messages for each control. Refine BMT Setup: Update translators and profiles in BMT based on these cleaner streams for precise control mapping and mode switching. 
This summary should help as you restart the session with a cleaner MIDI capture, aiming to finalize your BMT configuration for an efficient integration of the X-Touch with Premiere Pro. 

New Response:

Thank you for the detailed summary. Here’s how we can proceed based on the information provided: 

Steps to Finalize BMT Configuration: 

1. Recapture MIDI Streams: 

• Setup: Ensure your BMT is set up to capture MIDI from the Behringer X-Touch without feedback. Make sure the Bome Virtual MIDI Port is correctly configured to ignore its own output. 

• Capture: Use BMT's MIDI Monitor or a similar tool to capture all MIDI messages from the X-Touch. Focus on: 

• Pressing each Encoder Assign button (EQ, Track, Pan/Balance) to note their unique B0 CC messages. 

• Triggering the Scrub and Magnifier buttons to confirm their Note On/Off messages. 

2. Refine BMT Setup: 

• Translator Creation: 

• Mode Switching: Create translators for each Encoder Assign button: 

• EQ Button (B0 4B 05, B0 4A 11): Set this to switch to an "Effects Control" profile where controls map to video effects in Premiere Pro. 

• Track Button: Could be used for switching to an audio mixing profile if needed. 

• Pan/Balance: Similar profile switching or state verification. 

• Direct Controls:  

• Scrub Button (90 65 7F, 90 65 00): Map to Premiere Pro's scrub function or similar. Since it's momentary, ensure the action resets or stops when released. 

• Magnifier Button (90 64 7F, 90 64 00): Map this to zoom or another useful function in Premiere Pro. 

• Profile Management: 

• Define profiles in BMT for each mode (Audio Mixing, Effects Control). Each profile should have: 

• Appropriate MIDI to Keystroke or Command mappings for Premiere Pro shortcuts. 

• Configuration to manage LED feedback if possible (though this might be limited with the X-Touch's implementation). 

• State Management:  

• Since some controls don't provide clear state feedback via MIDI, use BMT to maintain internal state: 

• Use outgoing commands or internal variables in BMT to track whether you're in a particular mode or if a control was toggled. 

• Feedback Management: 

• Ensure that any MIDI feedback from Premiere Pro back to the X-Touch doesn't loop through BMT, which was already corrected in your setup. Double-check this by testing with all controls. 

3. Testing: 

• Profile Switching: Test switching between profiles to ensure all controls remap correctly. 

• Control Functionality: Verify that each button and encoder works as expected within Premiere Pro, particularly focusing on the mode-specific functionality. 

4. Optimization: 

• After initial setup, refine the translators for precision: 

• Adjust debounce times or thresholds for buttons if there's any ghosting or unintended triggering. 

• Optimize the speed of mode changes to ensure smooth transitions in Premiere Pro. 

This approach should lead to a more integrated and responsive control surface for Premiere Pro using the Behringer X-Touch through Bome MIDI Translator Pro. If you encounter any specific issues during recapture or configuration, feel free to detail them for further assistance. 

New Prompt:

I think that is enough data, especially if the provided manuals are consulted, to complete the mission of using up the X-Touch control surface to navigate, select and edit values in various Adobe control panels. 
Here are the functions other than default that I am looking for exclusively in [EQ] Encoder Assign: 

1. Starting with pressing the [EQ] Encoder Assign button to alert Bome Midi Translator Pro (BMT) to translate MIDI messages into keystrokes instead of passing through the MIDI messages to and from Premiere Pro, according to defined 'translators' in BMT. 
2. Translate clockwise Jog Wheel movement to a [TAB] keystroke and counterclockwise movement to a [SHIFT][TAB] keystroke for navigation within an Adobe panel. 
3. Encoder 1 is also translated to [TAB] for CW, and [SHIFT][TAB] for CCW 
4. The scribble strip for channel 1 is sent a sysex message to display "NAVIG" on the upper line and "<- ->" on the lower line. 
5. While the [SCRUB] button is toggled on (if this state is not easily available to Bome then we will use a press-and-hold, or Note On, state of the [SCRUB] button instead), then the Jog Wheel is translated to keystrokes [UP] for CW and [DOWN] for CCW to edit the selected value in the Adobe panel. 
6. When the [SCRUB] button is toggled off the Jog Wheel translation returns to Navigation mode. Again, if the toggle state is not easily available to Bome then we will use the release of the press-and-hold (Note Off) of the [SCRUB] button. I believe this function can be part of the rule for function 5, above). 
7. Encoder 2 is translated to [SHIFT][UP] and [SHIFT][DOWN] keystrokes and the scribble strip is sent A6 message to display "COARSE" on the upper line and "ADJ" on the lower line. 
8. Encoder 3 is translated to [UP] and [DOWN] keystrokes and the scribble strip is sent a sysex message to display "STD" on the upper line and "ADJ" on the lower line. 
9. Encoder 4 is translated to [CTRL][UP] and [CTRL][DOWN] keystrokes and the scribble strip is sysex message to display "FINE" on the upper line and "ADJ" on the lower line. 

Using the information in this session, the manuals for which links were provided, and any other resources Grok may need to complete this task, please provide detailed instructions for how to set things up in Bome MIDI Translator Pro, given the following conditions: 

1. The software is installed, and aliases have been created for the X-Touch 1 (MIDI IN alias = "From X-Touch 1->X-Touch 1", MIDI OUTPUT alias = "To X-Touch 1->X-Touch 1"). 
2. The Bome Virtual Midi Port has two entries in both the MIDI INPUT and MIDI OUTPUT tabs. In the INPUT tab, one is labeled "Bome MIDI Translator 1 Virtual In"; the other is in italics (so it may be an alias but the 'edit alias' option is grayed out in the right-click context menu), and it is labelled "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out". In the OUTPUT tab there exists "Bome MIDI Translator 1 Virtual Out", and the second entry is the italic labelled "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out". 
3. Of the available MIDI items in the INPUT tab I currently have selected: "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual In" AND "From X-Touch 1 -> X-Touch 1"; in the OUTPUT tab the current selections are "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out" AND "To X-Touch 1 -> X-Touch 1". 
4. In the MIDI Router tab "Bome Virtual Port 1" routed to "To X-Touch 1", and "From X-Touch 1" is routed to "Bome Virtual Port 1". 

The instruction should include an examination of the current set-up in Bome, which is functioning correctly, seemingly, in default settings, as well as details on setting up the translators for each of the desired functions. 

New Response:

Here's a step-by-step guide for configuring Bome MIDI Translator Pro (BMT) to achieve the functions you've outlined for the X-Touch control surface when using the [EQ] Encoder Assign button: 

Examination of Current Setup: 

1. MIDI Input: 
2. Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual In: This is likely meant for feedback or internal routing within BMT. 
3. From X-Touch 1 -> X-Touch 1: Direct input from the X-Touch controller. 
4. MIDI Output: 
5. Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out: For sending MIDI messages back through BMT for internal use or for feedback to X-Touch. 
6. To X-Touch 1 -> X-Touch 1: Direct output to the X-Touch for control or display updates. 
7. MIDI Router: 
8. Routing "Bome Virtual Port 1" to "To X-Touch 1" suggests feedback or echo management. 
9. Routing "From X-Touch 1" to "Bome Virtual Port 1" ensures all incoming MIDI from X-Touch goes through BMT for processing. 

This setup looks appropriate for both capturing and sending MIDI messages while managing potential echo or feedback loops. 

Setting Up Translators in BMT: 

Step 1: Create a New Project or Profile 

• Open BMT and either start a new project or select an existing profile for editing. 

Step 2: Configure [EQ] Encoder Assign Button 

• Translator for Mode Change: 

• Incoming: 90 2C 7F (EQ button press) 

• Action: Use a Preset Trigger to switch to a new preset or profile where these mappings are defined.  

• Outgoing: Optionally, you might send a Sysex message to confirm mode visually on the X-Touch if needed. 

Step 3: Set Up Translators for Jog Wheel and Encoders 

• Jog Wheel in Navigation Mode: 

• Translator for CW:  

• Incoming: B0 3C 01 

• Outgoing: Keystroke [TAB] 

• Translator for CCW: 

• Incoming: B0 3C 41 

• Outgoing: Keystrokes [SHIFT][TAB] 

• Encoder 1 for Navigation: 

• Translator for CW: 

• Incoming: B0 10 01 

• Outgoing: Keystroke [TAB] 

• Translator for CCW: 

• Incoming: B0 10 41 

• Outgoing: Keystrokes [SHIFT][TAB] 

• Scribble Strip for Channel 1: 

• Translator for Display Update: 

• Incoming: Same as the EQ button press 90 2C 7F 

• Outgoing: SysEx message to display "NAVIG" and "<- ->" (F0 00 00 66 14 12 00 4E 41 56 49 47 F7 for upper, and F0 00 00 66 14 12 07 3C 2D 20 3E F7 for lower line) 

• Jog Wheel in Edit Mode (Scrub Button): 

• Translator for CW when Scrub On: 

• Incoming: B0 3C 01 AND 90 65 7F (Scrub Note On) 

• Outgoing: Keystroke [UP] 

• Translator for CCW when Scrub On: 

• Incoming: B0 3C 41 AND 90 65 7F (Scrub Note On) 

• Outgoing: Keystroke [DOWN] 

• Return to Navigation Mode: 

• Use the same translators but with a condition that 90 65 00 (Scrub Note Off) is not present. 

• Encoder 2 (Coarse Adjustment): 

• Translator for CW:  

• Incoming: B0 11 01 

• Outgoing: Keystrokes [SHIFT][UP] 

• Translator for CCW: 

• Incoming: B0 11 41 

• Outgoing: Keystrokes [SHIFT][DOWN] 

• Scribble Strip: SysEx to display "COARSE" and "ADJ". 

• Encoder 3 (Standard Adjustment): 

• Translator for CW:  

• Incoming: B0 12 01 

• Outgoing: Keystroke [UP] 

• Translator for CCW: 

• Incoming: B0 12 41 

• Outgoing: Keystroke [DOWN] 

• Scribble Strip: SysEx to display "STD" and "ADJ". 

• Encoder 4 (Fine Adjustment): 

• Translator for CW:  

• Incoming: B0 13 01 

• Outgoing: Keystrokes [CTRL][UP] 

• Translator for CCW: 

• Incoming: B0 13 41 

• Outgoing: Keystrokes [CTRL][DOWN] 

• Scribble Strip: SysEx to display "FINE" and "ADJ". 

Step 4: Echo and Feedback Management 

• Ensure that your MIDI routing does not create feedback loops. Your existing setup seems good for this, but double-check that messages aren't being sent back to X-Touch inappropriately. 

Step 5: Testing 

• After setting up these translators, thoroughly test each function. Use BMT's MIDI Monitor to check incoming and outgoing messages, ensuring they behave as expected. 

Step 6: Save and Enable 

• Save your project or profile. Enable the translators by activating the preset or profile associated with the [EQ] mode. 

This setup will allow you to use the X-Touch in a custom way within Adobe Premiere Pro, focusing on navigation and value adjustment within panels. Remember, you might need to tweak some mappings or add additional translators based on real-world use to account for any nuances in how Premiere Pro responds to these commands. 

New Prompt

Given the following conditions:  
 

1. The software is installed, and aliases have been created for the X-Touch 1 (MIDI IN alias = "From X-Touch 1->X-Touch 1", MIDI OUTPUT alias = "To X-Touch 1->X-Touch 1").  
2. The Bome Virtual Midi Port has two entries in both the MIDI INPUT and MIDI OUTPUT tabs. In the INPUT tab, one is labeled "Bome MIDI Translator 1 Virtual In"; the other is in italics (so it may be an alias but the 'edit alias' option is grayed out in the right-click context menu), and it is labelled "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out". In the OUTPUT tab there exists "Bome MIDI Translator 1 Virtual Out", and the second entry is the italic labelled "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out".  
3. Of the available MIDI items in the INPUT tab I currently have selected: "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual In" AND "From X-Touch 1 -> X-Touch 1"; in the OUTPUT tab the current selections are "Bome Virtual Port 1 -> Bome MIDI Translator 1 Virtual Out" AND "To X-Touch 1 -> X-Touch 1".  
4. In the MIDI Router tab "Bome Virtual Port 1" routed to "To X-Touch 1", and "From X-Touch 1" is routed to "Bome Virtual Port 1". 

Using the data from this session, the manuals and other documents for which links are provided in this session, and any other resource Grok requires, please provide detailed instructions on a practical build of a translator(s) and other setup required in Bome MIDI Translator Pro to change the text displayed in the scribble strip when the [EQ] button is pressed in the Encoder Assign section of the X-Touch control surface - using the CC, B0 4B 05 as the trigger to change the scribble strip text. Use Channel 1 in this practical build, and display "NAVIG" on the upper row and "<- ->" on the lower row. 

New Response:

Here's a detailed guide for setting up Bome MIDI Translator Pro (BMT) to change the scribble strip text on Channel 1 of the X-Touch when the [EQ] button is pressed, using B0 4B 05 as the trigger: 

Step-by-Step Configuration: 

Step 1: Create or Open Project 

• Open BMT and ensure you're in the correct project or create a new one if necessary. 

Step 2: Verify MIDI Routing and Aliases 

• Your setup already has the correct aliases and MIDI routing: 

• MIDI IN: "From X-Touch 1->X-Touch 1" 

• MIDI OUT: "To X-Touch 1->X-Touch 1" 

• MIDI Router: "Bome Virtual Port 1" to "To X-Touch 1" and "From X-Touch 1" to "Bome Virtual Port 1" 

Step 3: Create a Translator for Scribble Strip Text Change 

• New Translator: 

• Name: "Change Scribble Strip for EQ Mode" 

• Incoming Message: 

• Type: Control Change (CC) 

• Channel: 1 

• Controller: 75 (hex 4B) 

• Value: 5 (hex 05) 

• This corresponds to B0 4B 05 

• Rules:  

• Here, you might not need rules unless you're doing conditional checks, but if you want to ensure this only happens once per press, you could use something like: 

• if g0==0 then goto "SendText" 

• g0=1 

• Label "SendText" 

• g0=0 (after sending, reset to allow for another press) 

• Outgoing Message:  

• Type: System Exclusive (SysEx) 

• You'll need two SysEx messages for the upper and lower lines of the scribble strip: 

• Upper Line ("NAVIG"):  

• F0 00 00 66 14 12 00 4E 41 56 49 47 F7 

• Lower Line ("<- ->"):  

• F0 00 00 66 14 12 07 3C 2D 20 3E F7 

• In BMT, you'll set these up as: 

• SysEx 1: 

• Data: 00 00 66 14 12 00 4E 41 56 49 47 

• SysEx 2: 

• Data: 00 00 66 14 12 07 3C 2D 20 3E 

• Make sure "Send F7" is checked for both SysEx messages to properly terminate them. 

Step 4: Set up the Output 

• Ensure that "To X-Touch 1->X-Touch 1" is selected in the Outputs for this translator so that the SysEx messages are sent back to the X-Touch for display update. 

Step 5: Test the Setup 

• Testing: 

• Press the EQ button on the X-Touch and check if the text "NAVIG" and "<- ->" appear on the scribble strip for Channel 1. 

• Use BMT's MIDI Monitor to see if the messages are being received and sent as expected. 

Step 6: Save and Finalize 

• Once you confirm the translation works, save your BMT project. You might want to organize this translator into a specific preset or profile if you're managing multiple configurations. 

Notes: 

• Echo Management: Since your setup routes "Bome Virtual Port 1" back to "To X-Touch 1", ensure that this doesn't cause an echo of the SysEx messages. If you see repeated messages or unwanted behavior, consider filtering or conditional rules to prevent this. 

• Alias Management: The italic entries in your MIDI setup suggest they are system-managed or locked aliases. This is normal and indicates they're internal to BMT's routing system. 

• Documentation Reference: The SysEx commands for the X-Touch are based on the MIDI Implementation document provided earlier, particularly where it describes how to change the display text. 

This setup should now change the scribble strip text for Channel 1 whenever the [EQ] button is pressed, using the specified MIDI message as a trigger.

New Prompt:

What changes to the previous response would need to be made for displaying text on Channel 2 instead, or 3, 4, 5, 6, 7 or 8? 

New Response:

To change the text display on different channels (2 through 8) instead of Channel 1, you need to modify the SysEx messages in the outgoing section of the translator. Here's how you would adjust the setup: 

Adjusting for Different Channels: 

• Channel 1:  

• Upper Line: F0 00 00 66 14 12 00 4E 41 56 49 47 F7 

• Lower Line: F0 00 00 66 14 12 07 3C 2D 20 3E F7 

For channels 2 through 8, you adjust the byte following 12 in the SysEx message: 

• Channel 2: 

• Upper Line: F0 00 00 66 14 12 07 4E 41 56 49 47 F7 (note: 07 instead of 00) 

• Lower Line: F0 00 00 66 14 12 0E 3C 2D 20 3E F7 (note: 0E instead of 07) 

• Channel 3: 

• Upper Line: F0 00 00 66 14 12 0E 4E 41 56 49 47 F7 (note: 0E instead of 07) 

• Lower Line: F0 00 00 66 14 12 15 3C 2D 20 3E F7 (note: 15 instead of 0E) 

• Channel 4: 

• Upper Line: F0 00 00 66 14 12 15 4E 41 56 49 47 F7 (note: 15 instead of 0E) 

• Lower Line: F0 00 00 66 14 12 1C 3C 2D 20 3E F7 (note: 1C instead of 15) 

• Channel 5: 

• Upper Line: F0 00 00 66 14 12 1C 4E 41 56 49 47 F7 (note: 1C instead of 15) 

• Lower Line: F0 00 00 66 14 12 23 3C 2D 20 3E F7 (note: 23 instead of 1C) 

• Channel 6: 

• Upper Line: F0 00 00 66 14 12 23 4E 41 56 49 47 F7 (note: 23 instead of 1C) 

• Lower Line: F0 00 00 66 14 12 2A 3C 2D 20 3E F7 (note: 2A instead of 23) 

• Channel 7: 

• Upper Line: F0 00 00 66 14 12 2A 4E 41 56 49 47 F7 (note: 2A instead of 23) 

• Lower Line: F0 00 00 66 14 12 31 3C 2D 20 3E F7 (note: 31 instead of 2A) 

• Channel 8: 

• Upper Line: F0 00 00 66 14 12 31 4E 41 56 49 47 F7 (note: 31 instead of 2A) 

• Lower Line: F0 00 00 66 14 12 38 3C 2D 20 3E F7 (note: 38 instead of 31) 

Changes to the Translator in BMT: 

1. Incoming Message:  

• No change needed here; the trigger B0 4B 05 remains the same for all channels. 

2. Outgoing Message: 

• For each channel, you'll need to update the SysEx data in the translator: 

3. SysEx 1 (Upper Line): 

• Change the byte after 12 to correspond with the channel number as above. 

4. SysEx 2 (Lower Line): 

• Change the byte after 12 to correspond with the channel number as above. 

5. Rules: 

• If you have conditional logic or counters in your rules to prevent multiple triggers, these would remain unchanged unless you want channel-specific behavior. 

6. Testing: 

• Test each channel by pressing the EQ button and checking if the correct text appears on the desired channel's scribble strip. 

7. Save: 

• After adjusting for each channel, save your changes in BMT. You might want to create separate translators for each channel or use variables within one translator if BMT supports this level of scripting. 

Remember, these modifications are based on the MIDI Implementation document for the X-Touch where it specifies how to address different channels for display updates. Ensure your BMT configuration does not create feedback loops when sending these messages back to the X-Touch.

[R Neil Haugen]

slovill,

That is an awesome, epic post to help some users speed up their workflow. Thanks for posting all that!

[slovill]

Thanks! It'll be a bunch of gobbledygook to most, but I hope those who need it will appreciate it. This info can help with any control surface as long as you know the MIDI strings the device uses. With all of the podcast controllers coming out the choices are many. Using Bome to capture MIDI for each button, fader and encoder, and then individually copy/pasting and labelling them in the AI is a bit tedious (I still left 41 buttons uncaptured.), but since I could not find this data documented anywhere it was the only way. Still, using AI to help sift the MIDI mess was cool and worth the effort. I am building the Bome translators today.

[R Neil Haugen]

I know that's what a lot of people are going to run to, for devices. The Tangent stuff is still for professional use more sensible. As you can 'natively' map Hades out of Premiere on any Tangent panel, without needing to do any of that stuff.

And there are a number of used Tangent  panels for sale most of the time, for budget issues.

Still, that was an amazing bit of work you did, and will help a lot of users ... thanks again!

[slovill]

I finished the translators for changing the background color of the LCD scribble strips on a Behringer X-Touch control surface, and I am sharing the Bome Midi Translator Pro (BMTP) file here. If you don't want to download the file, here is a visual reference, which I'll use to explain what it is doing:
First, the main window where default MIDI inputs and outputs are selected. Not shown here is the installation of a Bome Virtual MIDI Port. I used Bome's VMP because it came with BMTP, but there are a bunch of VMP's available. In Default MIDI Ports section, notice the italicized label for "From X-Touch 1 -> X-Touch 1" - that is an alias for the X-Touch. Using an alias is recommended, but I don't recall why:

Then, if you click the Preset in the far left column, you'll see the Preset page:

And for the tranlator itself: the "Incoming" is the trigger for this translator. I set it to a keystroke, [ctrl][alt][4], because the bit code for blue is 04. Here are all the colors and bit codes: Red=01, Green=02, Yellow=03, Blue=04, Magenta=05, Cyan=06, White=07, Blank=00. So I chose [ctrl][alt][1 thru 8] as the shortcuts for color, but it could be any key/modifier of your choice.

The color change is accomplished by sending a sysex (system exclusive) message to the X-Touch. Bome is used to interpret a keyboard shortcut into this sysex message which Bome then sends to the X-Touch. There are no rules for this translator.

So the sysex message itself and what it is saying to the X-Touch:

F0=Hey, here is the start of a sysex message (Sysex message start)

00 00 66=I'm talking to you, X-Touch (Manufacturer, device ID)

14 72=Specifically I am talking to the scribble strip and am going to tell them a color

04 04 04 04 04 04 04 04=Make Channel 1 blue, make Channel 2 blue,...make Channel 8 blue (color bit)
F7=Over and out (Sysex message end)

Unfortunately, I have not been able to make translators 9 thru 12 to work. They are supposed to change the brightness of the scribble strip but so far have not worked.

[slovill · Accepted solution]

Okay, someone smarter than me went through all of this already. MIDI Control Surface - Premiere Pro | Peltmade PrControl

This cat went places I didn't even think of. He can have my $29.

[slovill]

In case anyone wants to tackle this on their own, or if they are just looking for a comprehensive list of which MIDI notes are mapped to the Beheringer X-Touch Universal Control Surface buttons:

Global Variable	ZONE	BUTTON	MIDI NOTE	HEX	LED ON (to x-touch)	LED OFF (to x-touch)
i0	Channel Strips	Record Arm 1	00	00	90 00 7F	90 00 00
i1	Channel Strips	Record Arm 2	01	01	90 01 7F	90 01 00
i2	Channel Strips	Record Arm 3	02	02	90 02 7F	90 02 00
i3	Channel Strips	Record Arm 4	03	03	90 03 7F	90 03 00
i4	Channel Strips	Record Arm 5	04	04	90 04 7F	90 04 00
i5	Channel Strips	Record Arm 6	05	05	90 05 7F	90 05 00
i6	Channel Strips	Record Arm 7	06	06	90 06 7F	90 06 00
i7	Channel Strips	Record Arm 8	07	07	90 07 7F	90 07 00
i8	Channel Strips	Solo 1	08	08	90 08 7F	90 08 00
i9	Channel Strips	Solo 2	09	09	90 09 7F	90 09 00
ia	Channel Strips	Solo 3	10	0A	90 0A 7F	90 0A 00
ib	Channel Strips	Solo 4	11	0B	90 0B 7F	90 0B 00
ic	Channel Strips	Solo 5	12	0C	90 0C 7F	90 0C 00
id	Channel Strips	Solo 6	13	0D	90 0D 7F	90 0D 00
ie	Channel Strips	Solo 7	14	0E	90 0E 7F	90 0E 00
if	Channel Strips	Solo 8	15	0F	90 0F 7F	90 0F 00
ig	Channel Strips	Mute 1	16	10	90 10 7F	90 10 00
ih	Channel Strips	Mute 2	17	11	90 11 7F	90 11 00
ii	Channel Strips	Mute 3	18	12	90 12 7F	90 12 00
ij	Channel Strips	Mute 4	19	13	90 13 7F	90 13 00
ik	Channel Strips	Mute 5	20	14	90 14 7F	90 14 00
il	Channel Strips	Mute 6	21	15	90 15 7F	90 15 00
im	Channel Strips	Mute 7	22	16	90 16 7F	90 16 00
in	Channel Strips	Mute 8	23	17	90 17 7F	90 17 00
io	Channel Strips	Select 1	24	18	90 18 7F	90 18 00
ip	Channel Strips	Select 2	25	19	90 19 7F	90 19 00
iq	Channel Strips	Select 3	26	1A	90 1A 7F	90 1A 00
ir	Channel Strips	Select 4	27	1B	90 1B 7F	90 1B 00
is	Channel Strips	Select 5	28	1C	90 1C 7F	90 1C 00
it	Channel Strips	Select 6	29	1D	90 1D 7F	90 1D 00
iu	Channel Strips	Select 7	30	1E	90 1E 7F	90 1E 00
iv	Channel Strips	Select 8	31	1F	90 1F 7F	90 1F 00
iw	Channel Strips	V-Pot 1	32	20	90 20 7F	90 20 00
ix	Channel Strips	V-Pot 2	33	21	90 21 7F	90 21 00
iy	Channel Strips	V-Pot 3	34	22	90 22 7F	90 22 00
iz	Channel Strips	V-Pot 4	35	23	90 23 7F	90 23 00
j0	Channel Strips	V-Pot 5	36	24	90 24 7F	90 24 00
j1	Channel Strips	V-Pot 6	37	25	90 25 7F	90 25 00
j2	Channel Strips	V-Pot 7	38	26	90 26 7F	90 26 00
j3	Channel Strips	V-Pot 8	39	27	90 27 7F	90 27 00
j4	Assignment	Track	40	28	90 28 7F	90 28 00
j5	Assignment	Send	41	29	90 29 7F	90 29 00
j6	Assignment	Pan	42	2A	90 2A 7F	90 2A 00
j7	Assignment	Plug-In	43	2B	90 2B 7F	90 2B 00
j8	Assignment	EQ	44	2C	90 2C 7F	90 2C 00
j9	Assignment	Instrument	45	2D	90 2D 7F	90 2D 00
ja	Fader Bank	Left Bank	46	2E	90 2E 7F	90 2E 00
jb	Fader Bank	Right Bank	47	2F	90 2F 7F	90 2F 00
jc	Fader Bank	Left Channel	48	30	90 30 7F	90 30 00
jd	Fader Bank	Right Channel	49	31	90 31 7F	90 31 00
je	Fader Bank	Flip	50	32	90 32 7F	90 32 00
jf	Fader Bank	Global View	51	33	90 33 7F	90 33 00
jg	Display	Name/Value	52	34	90 34 7F	90 34 00
jh	Display	SMPTE/Beats	53	35	90 35 7F	90 35 00
ji	Functioin Key	F1	54	36	90 36 7F	90 36 00
jj	Functioin Key	F2	55	37	90 37 7F	90 37 00
jk	Functioin Key	F3	56	38	90 38 7F	90 38 00
jl	Functioin Key	F4	57	39	90 39 7F	90 39 00
jm	Functioin Key	F5	58	3A	90 3A 7F	90 3A 00
jn	Functioin Key	F6	59	3B	90 3B 7F	90 3B 00
jo	Functioin Key	F7	60	3C	90 3C 7F	90 3C 00
jp	Functioin Key	F8	61	3D	90 3D 7F	90 3D 00
jq	Global View	MIDI Tracks	62	3E	90 3E 7F	90 3E 00
jr	Global View	Inputs	63	3F	90 3F 7F	90 3F 00
js	Global View	Audio Tracks	64	40	90 40 7F	90 40 00
jt	Global View	Audio Instrument	65	41	90 41 7F	90 41 00
ju	Global View	Aux	66	42	90 42 7F	90 42 00
jv	Global View	Busses	67	43	90 43 7F	90 43 00
jw	Global View	Outputs	68	44	90 44 7F	90 44 00
jx	Global View	User	69	45	90 45 7F	90 45 00
jy	Modifier	Shift	70	46	90 46 7F	90 46 00
jz	Modifier	Option	71	47	90 47 7F	90 47 00
k0	Modifier	Control	72	48	90 48 7F	90 48 00
k1	Modifier	Alt	73	49	90 49 7F	90 49 00
k2	Automation	Read	74	4A	90 4A 7F	90 4A 00
k3	Automation	Write	75	4B	90 4B 7F	90 4B 00
k4	Automation	Trim	76	4C	90 4C 7F	90 4C 00
k5	Automation	Touch	77	4D	90 4D 7F	90 4D 00
k6	Automation	Latch	78	4E	90 4E 7F	90 4E 00
k7	Automation	Group	79	4F	90 4F 7F	90 4F 00
k8	Utility	Save	80	50	90 50 7F	90 50 00
k9	Utility	Undo	81	51	90 51 7F	90 51 00
ka	Utility	Cancel	82	52	90 52 7F	90 52 00
kb	Utility	Enter	83	53	90 53 7F	90 53 00
kc	Transport	Marker	84	54	90 54 7F	90 54 00
kd	Transport	Nudge	85	55	90 55 7F	90 55 00
ke	Transport	Cycle	86	56	90 56 7F	90 56 00
kf	Transport	Drop	87	57	90 57 7F	90 57 00
kg	Transport	Replace	88	58	90 58 7F	90 58 00
kh	Transport	Click	89	59	90 59 7F	90 59 00
ki	Transport	Solo	90	5A	90 5A 7F	90 5A 00
kj	Transport	Rewind	91	5B	90 5B 7F	90 5B 00
kk	Transport	Fast Forward	92	5C	90 5C 7F	90 5C 00
kl	Transport	Stop	93	5D	90 5D 7F	90 5D 00
km	Transport	Play	94	5E	90 5E 7F	90 5E 00
kn	Transport	Record	95	5F	90 5F 7F	90 5F 00
ko	Cursor/Zoom Key	Cursor Up	96	60	90 60 7F	90 60 00
kp	Cursor/Zoom Key	Cursor Down	97	61	90 61 7F	90 61 00
kq	Cursor/Zoom Key	Cursor Left	98	62	90 62 7F	90 62 00
kr	Cursor/Zoom Key	Cursor Right	99	63	90 63 7F	90 63 00
ks	Cursor/Zoom Key	Zoom	100	64	90 64 7F	90 64 00
kt	Jog/Scrub Wheel	Scrub	101	65	90 65 7F	90 65 00
ku			102	66	90 66 7F	90 66 00
kv			103	67	90 67 7F	90 67 00
kw	Faders	Touch 1	104	68	90 68 7F	90 68 00
kx	Faders	Touch 2	105	69	90 69 7F	90 69 00
ky	Faders	Touch 3	106	6A	90 6A 7F	90 6A 00
kz	Faders	Touch 4	107	6B	90 6B 7F	90 6B 00
l0	Faders	Touch 5	108	6C	90 6C 7F	90 6C 00
l1	Faders	Touch 6	109	6D	90 6D 7F	90 6D 00
l2	Faders	Touch 7	110	6E	90 6E 7F	90 6E 00
l3	Faders	Touch 8	111	6F	90 6F 7F	90 6F 00
l4	Faders	Touch Master	112	70	90 70 7F	90 70 00
l5			113	71	90 71 7F	90 71 00
l6			114	72	90 72 7F	90 72 00
l7			115	73	90 73 7F	90 73 00
l8			116	74	90 74 7F	90 74 00
l9			117	75	90 75 7F	90 75 00
la			118	76	90 76 7F	90 76 00
m0			119	77	90 77 7F	90 77 00
m1			120	78	90 78 7F	90 78 00
m2			121	79	90 79 7F	90 79 00
m3			122	7A	90 7A 7F	90 7A 00
m4			123	7B	90 7B 7F	90 7B 00
m5			124	7C	90 7C 7F	90 7C 00
m6			125	7D	90 7D 7F	90 7D 00
m7			126	7E	90 7E 7F	90 7E 00
m8			127	7F	90 7F 7F	90 7F 00