Hi, Try this project file for Fader 1 only.
There are four aliases. Please point your 2 X-Touch aliases to your actual device. You will likely get prompted when you open the file. If not go to the MIDI menu and then click "Edit Project Port Aliases" to assign them
I suggest you use Bome MIDI Translator 1 Virtual In and Out for your UA-Control assignments. Then set up UA-Control to look at BMT1 instead of your X-Touch.
Set up your X-Touch for Mackie Mode.
In this example, I convert fader 1 to CC64 (First preset and translator) to send to UA-Control.
The second preset is set up to convert CC64 back to Fader 1 on your X-touch.
As long as UA-Control sends CC64 back to BMT1 this should move your motorized fader assuming you have UA-Control set up to UA console and you are moving the fader on UA Console. UA-Console and UA-Control need to be able to pass MIDI messages in both directions for this to work correctly.
Change the CC number as required for your Fader.
Mackie protocol uses pitch bend for fader movements - E0 pp qq for fader 1 , E1 pp qq for fader 2 up to E7 pp qq for fader 8 and E8 pp qq for master fader. This is why you need to set up your X-touch for Mackie Mode.
In this example I have set up Preset Fader to CC with X-touch as input and UA-Control as output. I set up CC to Fader with UA-Control as input and X-touch as output. Any translators under this preset will follow that convention unless you override them within the translator.
The below video tutorial shows how port assignments work in MT Pro.
PS. If resolution of your physical fader is to low when you move it, set up in rules of Fader to CC, translator Fader 1 so that it reads rr=0. My controller that I testing with is not standard Mackie so it sent with the bytes reversed (rr=1).
Bome Customer Care
Also available for paid consulting services: email@example.com