X-Touch (+Extender) MIDI Remote Script (MCU mode)

Why is it mentioned in the instructions:

Setup with an extender unit
To use your device with an extender unit, follow the same steps as above, but edit the script file before restarting Cubase: In the configuration options at the top of the file, replace devices: [“main”] with devices: ["extender ", “main”] (or devices: [“main”, “extender”] if you have your extender on the right side of the main device).

Then restart Cubase and configure the MIDI Remote by clicking the “+” button in the lower zone’s MIDI Remote pane.

Even if I don’t add it, the Extender is displayed in the MIDI Remote, but it doesn’t reflect the script… only the X-Touch still works

1 Like

I solved!!!
It was time!!!

After adding the second Controller with these settings:

With all the problems already mentioned…

… I disabled the script by selecting the first X-Touch Controller… and both Control Surfaces disappeared… and only the “+” sign was left… i enabled the script…

Now, adding a Controller with the “+”, sees all 4 ports!!!

This is the correct configuration of the 4 ports!!!


Thanks for helping each other out, guys! As always, I’ll gladly take suggestions on how to improve the docs – maybe in the form of a trouble shooting section?

1 Like

Hi guys!

I’ve been using this script for a while, and I have to admit that it works pretty well. However, I’ve noticed a couple of quirks that I would like to address.

First, sometimes, the script is removed from the MIDI Remote Tab, so I have to re-add it. Maybe it’s related to some crashes in Cubase, but no other remote script has this issue.

The other thing I want to do is define F1 on the controller to shift the entire X-Touch setup (I have 3 units with 24 channels and one master fader) to the first page. This can be achieved by defining the bank size (24 channels) and assigning F1 to the command. The issue is that I have to do this EVERY TIME I restart Cubase because the bank definition is lost. Is there any way to make this permanent within the script?

Thanks in advance for your help!


1 Like

Hey Antonio,

that’s odd. I can’t repro and I don’t know what to do about it – if there’s anything I can do at all :confused:

I was surprised to find we have to select the bank size under Mix Console > Mixer Bank Zone > === Setup === in the Mapping Assistant’s Function Browser when it’s already given by the script.

Nothing I can do to fix the root problem, but what about mapping “Reset Mixer Bank” to Shift + Bank Left by default? I think it’s quite useful in general to have a button that jumps to the first mixer bank.

Here’s a quick note that I just released v1.7.0 with some new features and a few improvements:

  • There’s a script variant for the original MCU (Pro) hardware now, thanks to @skijumptoes and @blissdrums’ joint testing efforts :heart_hands:
  • “Shift + Bank Left” navigates to the first mixer bank now (@Antonio_Escobar)
  • “Shift + Display Name/Value” now flips the scribble strip display rows – really only needed for horizontal display metering on the MCU, but doesn’t hurt on other devices too
  • X-Touch users can now set useEncoderColors to false in the config section to always use channel colors for display backlights, regardless of the active encoder assignment

Wise men say this release might also fix potential issues with button lights in future Cubase versions :crystal_ball: :sparkles:




1 Like


I just noticed that I can’t really write automation data with “touch” anymore, that is, the data is only overwritten on an existing automation curve as long as I always move the fader, but not if I just touch it, as it actually would be in the Mackie Control protocol. Have I overlooked a setting or does this really not work?