Control Jog Wheel in Resolve Fairlight using X-Touch Universal

david-2353 · January 23, 2026, 8:52pm

I wish to use the large Jog/Scrub wheel on a Behringer X-Touch to move up and down the timeline in DaVinci Resolve Fairlight page.
Resolve (Fairlight) have panels with large scrub/Jog knobs that do this, but in Windows it currently requires dragging the timeline cursor with a mouse.

Capturing the incoming CC when going both left and right is straight forward, but what do I use to input that midi message to the Fairlight software? Can I also control the speed of the jogging with greater turns of the X-Touch jog wheel? Many thanks DaveT

SteveC · January 23, 2026, 9:40pm

Hi and welcome to the Bome community!

I don’t think that Davinci Resolve supports either HUI or Mackie MCU for MIDI functions, however you could certainly convert your jog wheel output to keyboard shortcuts to get the results that you want.

This post shows how you can use various controllers to control different video editing software (including Davinci Resolve). I would recommend that you try it using the X-Touch One Preset. Many Davinci resolve shortcuts are included here. Presets 1-5 handle different controllers and presets 6-12 handle different video editors. The project is set up to be able to separate the incoming MIDI messages from different controllers to output different keystrokes, essentially separating the input and outputs.
It uses the perform action heavily to handle dthe MIDI to keystroke translation. In my case translator 4.7 handles the MIDI input, 4.8 monitors whether or not the scroll wheel is still moving and 10.5 handles the shortcut keystrokes. Translator 10.2 handles making sure Davinci Resolve if focused before sending keystrokes.

The attached version below the updated project file since I originally posted about this in the referenenced posting.

Video-Editor-Control-2025-12-23.bmtp (176.8 KB)

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

david-2353 · January 24, 2026, 1:50pm

Steve,
Thanks for your very prompt reply and comprehensive information. Alas my own comprehension of any Bome instructing is limited to the translation of key presses on the X-Touch into keystrokes in Fairlight, so despite looking at your .bmtp file, I’m still at a loss to input the required info to the Midi Translator to deal with my Jog Wheel requirement!
I can capture the Jog Wheel midi note from the X-Touch but that then continues issuing the same midi note, until I click the ‘X’ button to abort that capture. The ‘output’ instructions and ‘rules’ alas, as I said I am still unable to deal with. David

SteveC · January 24, 2026, 2:53pm

OK this might be more help.

Translator 1.0 will set the value of global variable ga to 1 when Davinci Resolve is focused.
Translator 1.1 will set the value of global variable ga to 0 when Davinci Resolve is not focused.
More on this later
Translator 1.2 toggles the value of global variable gb which will either set course movement (value 1) of fine movement
(value 0). It also sends the LED state of the Srub button on or off.

Most of the work happens in the rules of translator 1.3
We look at the incoming value of the jog wheel and set the value of local variable tt to either -1 (Left movement) or 1 (right movement.

If Davinci Resolve is not focused, we call translator 1.4 to focus it. We look at the value of ga as described in translators 1.0 and 1.1

Depending on the value of gb (course/fine) we will either send perform keystroke with a given value indicating which keystroke we want to send. We use the value rr to determine how much delay we want when sending the keystroke.

Translators 1.5-1-8 determine whether it is for them (based on the first parameter passed) and then send the desired keystroke.

Here are the rules of translator 1.3

if qq<64 then tt=qq
if qq>64 then tt=64-qq
Log "Log tt=%tt%"
if ga==0 then Log "Log Performing Focus"
if ga==0 then Perform "Focus"
//set delay
rr=10
// Look if scrub is pushed
if gb==1 then Goto "Scrub"

if tt>0 then Perform "Keystroke",0,rr
else Perform "Keystroke",1,rr
exit rules, skip Outgoing Action

Label "Scrub"
if tt>0 then Perform "Keystroke",2,rr
else Perform "Keystroke",3,rr

My Aliases are set up as follows. You will need them set up to point to your X-Touch. You also need your X-Touch in MC mode.

I’m on Windows so, if you are on Mac, you will need to set the application focus target in the incoming triggers of 1.0 and 1.1 and the outgoing action of 1.4

I know that this may not be as simple as you would like but what you are asking is more complicated than just a single button to keystroke action.

X-touch-Jog-to-Davinci-Resolve.bmtp (4.6 KB)

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

david-2353 · January 24, 2026, 4:04pm

Steve, That’s brilliant!
The jog wheel now shuttles up and down the Fairlight timeline wonderfully. Interestingly the ‘Scrub’ button on the X-Touch is reversed, as it works as a jog wheel when set ‘on’, and it stays in that ‘on’ mode when yon go back to another transport button. It was disconnecting previously, and now with scrub ‘off’’, it does actually allow you to slowly scrub the audio on the track.

I’m happy with all of that and I can now set about emulating the other keys that made Fairlight control panels outstandingly ergonomic….right back from the first Fairlight ‘MFX3Plus’ panel I bought in 1996 and which they only slightly refined up to the ‘Xynergi’. The current Blackmagic Fairlight Editor panels are the same layout….but alas still expensive for non-professional audio work.

Thanks so, so much. David

SteveC · January 24, 2026, 4:07pm

Hi,

Well I’m glad I could help! Happy “Resolving”!

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

david-2353 · January 24, 2026, 7:15pm

Steve, I’m not now able to capture a relevant MIDI message in the ‘Incoming’ section to set up new keys.
Prior to using the new ’Jog wheel’ project file you sent I was capturing MIDI messages such as 90 54 00. Now I’m continuosly getting MIDI F0 7E 00 06 01 F7 and am no longer able to capture the individual X-Touch key presses. This is even when I don’t have your new file loaded. D

SteveC · January 24, 2026, 7:35pm

That is because on Windows only one application or device to connect to a given MIDI port at a time, so either Bome MIDI Translator Pro or Davinci Resolve is being blocked.

To fix this, point Davinci Resolve to Bome MIDI Translator 1 Virtual Port (BMT 1) instead of to your X-touch Then add the following in the MIDI router to allow other (non-translated message) to pass through untouched.

The attached update project file now has the following aliases.

I then added these connections in the MIDI router.

Now anything without a translator will pass through untouched. You can add translators but make sure that you have the device selection correct.

For more information about device selection, see this tutorial.

X-touch-Jog-to-Davinci-Resolve-a.bmtp (4.7 KB)

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

david-2353 · January 24, 2026, 8:32pm

Steve,
I had Resolve pointed to BMT1 before, and I was getting the non-translator messages through just fine, and the usual controls on the X-Touch were working in addition to your Jog Wheel translation.
I have put in your new file, but still get that same continous MIDI Message now that doesn’t allow me to write any new translations anymore. Is the Jog Wheel now outputting a MIDI message all the time and not allowing Bome to see any of my X-Touch key press midi anymore?
So to sum up, I can copy the few key press MIDI codes from a previous project (ie 90 54 00, 90 50 00 etc) and they work OK in addition to your Jog Wheel translation, but I cannot now see any new Input midi codes to capture, as I always just get F0 7E 00 06 01 F7 incoming. D

SteveC · January 24, 2026, 8:36pm

Hi, it should work. Just make sure your aliases are set up correctly. You get to alias setup in the MIDI menu.

You can learn more about aliases from this tutorial.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

SteveC · January 25, 2026, 5:39am

This is a device query message coming from Davinci Resolve and your device should respond with another SysEX to confirm it is connected so the path from Davinci Resolve to the controller does not seem complete. Maybe restart your controller while everything is connected.

david-2353 · January 25, 2026, 2:36pm

Steve,

Today I’m able to load in new translators. That F0 7E 00 06 01 F7 query message persists whenever I try to capture an incoming midi message from the X-Touch, but if I use the Note On or Off as the midi code, I get the X-Touch key working OK. So in fact I’m happily adding in my new keystrokes. Thanks, so so much for your perserverance with me! Wonderful Support. D

SteveC · January 25, 2026, 4:12pm

I’m glad it’s working!

This version will get you beyond the initial device inquiry since the X-touch doesn’t respond. Then Davinci sends a serial number request query and I respond as I believe I should but it keeps sending the request over and over.

In either case, it seems to work whether we respond or not.

See preset 2 (Handshake)

X-touch-Jog-to-Davinci-Resolve-b.bmtp (5.7 KB)