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.

Hi, can the compact faders CC be edited to use for mod and expression cc1/cc11 - one of my uses would be for controlling kontakt virtual instrument expression and mod on cc1/11 - any guidance appreciated

Hey Ben. You can use the X-Touch Editor software to do this adjustment. Choose what fader sends what CC. You don’t need the MIDI Remote for this, the MIDI data will come through the X-Touch Port, so if you have a MIDI keyboard providing the notes and velocities on a track, you could change the Input to All MIDI Inputs, and have the Compact’s incoming CC data be added to the MIDI keyboard’s stream of data.

Thanks ggmanestraki - my compact is en route so when it gets here I’ll do as you say (if I understand) and post how I get on - I am on a mac, but as I understand it I can plug into a pc and make adjustments in the editor software(?)

Many thanks for your help, much appreciated

Oh boy, I don’t know anything about that. Make sure that you can run the Editor on your system, because even in my case, on PC, I’m still not 100% sure that the settings stay on the unit. I have to load up the editor on every single boot-up so that it does some kind of handshake.

If I don’t load the editor on boot-up, nothing works as expected.

So make sure the app can run on your mac, or at least see if you can run with the defaults.

But now, it’s on its way. If you encounter any problems, give me a shout, I hope that I can help.

I’m holding out hope on it saving changes - thanks I’ll give you a shout one way or the other when im up and running. I need to have another attempt at getting away from the mouse and keyboard anyways and my mixing could do with some work, so it’s not waste. It’s almost an achievement that Behringer have managed to avoid creating a mac app in the lifespan of this unit. I salute them in their lack of interest.

1 Like

I wholeheartedly hope that it does.

Even if it doesn’t, there are ways to do what you want through a 3rd party app like BOME MIDI translator, it’s just that I’m always looking for the most simple way to do things.

Hi ggmanestraki - as expected I am a little confused and i probably just dont understand the editor values yet. Ive plugged the XTC in, edited fader 1 and 2 to cc1/11 (settings seem to have stuck fine when disconnecting from pc) when i go into midi mode, layer B (where I edited the faders) I can see the DAW is receiving midi - but the faders are having no effect on (say) Spitfire strings cc1/11. In fact, button 6 along the bottom is opening/closing the VI, but not much else is actioning in midi mode. (well, thats lie, the top row of buttons are muting, but starting at track 9, middle row = track select - again starting at 9 and the bottom row nothing assigned that I can see, top encoders unassigned apart from coder 2 that seems to be controlling the fader below)

I set the XTC up as Mackie Control, the VI is Out of Contact, Ch1, In = All inputs

Any suggestions appreciated, thanks, Ben

Let’s take it step by step.

Can you record the fader? Like this?

I’m just moving the first fader (assigned to CC1) while record is running.

Hi, unfortunately I’m not getting it to record the cc1/11 (cant hear it either and the Kontakt mod wheel isnt moving) , but if I view the midi monitor I can see the 2 faders cc1/11 are actually named modulation and expression as I move the faders. BTW, dont hate me but my main DAW is Studio One. Im just hoping this is a generic XTC editor setup process

sorry, let me start again - ive got this back to front. Im in midi mode, layer B (where my cc1/11 is mapped to fader 1 and 2) - the midi monitor is showing mod and expression when i move them - they arent recording.

In MC Mackie Mode the transport and buttons seems to work fine, but faders all show pitch bend in midi monitor

1 Like

Not hating at all, but it will be near impossible to guide you on the Studio 1 side, I don’t know poopies about it.

The thing is. The compact either turns on in MC mode, or MIDI mode. There’s no easy switching between them while it’s on. In MC mode, I think the faders are sending pitch bend. Layer A and Layer B could be two banks? I haven’t really used MC mode, I went straight for the MIDI one.

What you have set up in the Layer for the faders, it’s correct. It should work when the device is in MIDI mode. But as I said, this is where my Studio One ignorance kicks in - I can’t know how, or if, you need to do something more so that the program allows the data through to a track.