Behringer X-Touch Compact and Cubase

Has anyone managed to get a Behringer X-Touch Compact controller working in Cubase 13 as a midi controller, Cubase does not seem to want to recognise the different cc commands assigned to the faders? Has anyone written a script using the midi mapper?
Assistance would be appreciated.

Yes and yes. It works here. However…

Have you downloaded the application from Behringer? For me, it goes like this. Once Windows launches, I turn on the Compact. Then I run the Behringer app, and it’s only then that the unit gets the data. After that, I launch Cubase and all works fine. For this reason alone, the application for the Compact has made its way in the Startup menu of Windows, so that I don’t have to run it myself every time.

I’m talking about custom assignment of CCs and modes of relative encoders of course, in MIDI mode, and not the MCU mode of the unit.

1 Like

I started in the sequence you suggested, X-Touch Compact first, then load Editor preset and choose setup, then open Cubase.
Only cc1 works, no cc11, cc21, cc7 etc. Is there something else I should be doing in the editor?
The X-Touch is in standard mode, not MC mode.

Any assistance would be appreciated.

If I posted my editor banks, and my script, would you be willing to try them out?

Ok, here’s the script.
Behringer_X-Touch Compact.midiremote (12.5 KB)

You load this from here:



And here’s my Layers A and B for the Compact
X-TOUCH EDITOR_v1-21.zip (703 Bytes)

You load these from here:


Find the file ggmanestrakiLayerA.bin in the explorer and dump to Layer A, like this:





Then do the same for ggmanestrakiLayerB.bin and dump it to Layer B of the unit.




  • Layer A is where the MIDI Remote works.
  • Layer B is to pass raw CC messages to a track, starting with CC1 to CC8 for the 8 faders, and CC36 for the master. You can change these in the X-Touch Editor Preset if you want to customize it for your own use.
  • The remote’s layout is completely crazy, and only useful to me.

The goal here instead is to see if things generally work. Open a project, do the motorised faders work? Can you use the faders for volume control? The bottom buttons as Edit Channel Settings? The top encoders for panning? That’s for Layer A.

For Layer B, if you load a vst instrument and set its input to ALL MIDI IN, can you record CCs on the part by moving the faders?

If it’s yes for both of these scenarios, you’re good to go. Scrap my script, and start building your own the way that suits you from the Surface Editor.

1 Like

Thanks mate

I downloaded and installed as instructed.

Unfortunately nothing worked, the faders went crazy.

I did a factory reset to remove everything.

Anyway, thanks for the trouble of trying to help me, much appreciated.

How do you test if CCs are working? Had you set up a MIDI remote of your own? Do you want to use the compact as a generic additional MIDI devices to record CCs to MIDI tracks? Or as a DAW controller through MIDI Remote?

Sequence of events,
Turn on x touch in standard mode. Load Behringer editor
Load scripts then turn on Cubase.
Result
Doesn’t work for me.
Faders go crazy and start vibrating

Let’s first make sure that things load as they should in Compact, and worry about Cubase later.

Once you turn on the Compact, run the editor and press this button. Then, go to the next Tab: Faders+Foot and show me a screenshot of that.

Edit: Did you close the Editor before launching Cubase?? I forgot to tell you.