Cubase 10.5 w/ Behringer X-Touch

[mjdevries]

@ChrisDuncan

I had an X-Touch in the Cubase 9.x days, and it worked fine with Cubase. However, I ultimately sold it and bought an actual Mackie MCU. The things that bothered me may or may not be important to you.

There were some initial frustrations trying to figure out how to do particular things on the X-Touch because there is absolutely zero customer support from Behringer. And I do mean zero. There are some video tutorials that are very well done, but they all focus on Logic users and there’s none for Cubase. There’s a user forum but even that is sparsely populated. Eventually a few folks helped me out and I got things working.

One of the biggest problems for me was the angle of the LCDs. The X-Touch LCDs are flush mounted with the unit, so it’s really designed to sit on an office desk where you look down at it. Trying to view them from an angle, like you would meters on a mixer, was almost unreadable. I eventually stuck a rolled up towel underneath the back to tilt it at about a 30 degree angle. LCDs were readable at that point but still not optimal. Plus, a pretty clumsy setup having to prop up with a towel.

Another thing that bugged me was the build quality. It’s a plastic unit, the faders and jog wheel feel cheap, and that’s all understandable. The unit is cheap. $600 for the X-Touch versus $1200 for a Mackie MCU. However, the Mackie is metal and built like a tank. It also has a perpendicular display for the LCDs, and the price wasn’t an issue for me. So, I replaced the Behringer with the Mackie and have been very happy with the latter.

Of all the things I listed, the most important thing you should consider is placement and the ability to view the LCDs. You really need to be looking almost straight down at them, so if you’re able to sit at a desk where it’s directly under you it should work fine, although you may get a stiff neck after a long session.

That said, as long as you can read the displays, at half the price of an MCU it’s a good bang for the buck.

To resolve the angle of the LCDs you can buy a cheap laptop Stand at IKEA , that did solve the problem perfect for me. Just € 4,99
Alle producten. Bestel online of kom langs! - IKEA The size fits perfect

[ChrisDuncan]

@pgstudio

@greggybud

@pgstudio

I made some customization using cubase + MaxMSP (or Puredata) to enhance the experience using X-Touch + Cubase.
It made my life so much easier.

https://www.youtube.com/watch?v=esOnlGyvTs4

Hello! I have been referring lots of forum posts to your video ever since you initially wrote that solution in VI control. You even said that you had “fixed” the issue that plagues most Mackie Control protocol users of no auto-banking.

The thing is…your solution is just bloody complicated for a simple musician guy like me. I love that you have achieved this. You could probably sell this solution if you could somehow package it all together so the end-user just makes a few clicks. Of course, it needs to be a total solution so when someone re-installs Cubase or changes their DAW Mackie Control Protocol controller…they can also re-install the solution that makes this work.

For myself at least…what amount would I pay a developer so I could click on Cubase channel 64…and my QconPro would autobank to channel 64…instead of me pressing the bank button 8 times? It would bring back a lot of functionality.

Ehehe… I know it’s too nerdy to make it work. But I love all kinds of nerdy/progamming/geek stuff and it was the only solution I came out and I have no idea how to “pack things” to make it simpler. Unfortunately.

I’ve “fixed” the autobank thing indeed (among other things) but it has some limitations/bugs and that’s why I didn’t released it but it works pretty well most of the time. That patch on the video has grown QUITE A BIT over the time. Now I have 2 10inch monitors over each Xtouch and the monitors show the levels and also the scribble strips text which is WAY better to read than the poor XTouch display. And everything is controlled by the patch.
XtouchDisplays.jpg

Anyway, I know it’s not for everyone and most of this stuff should also be implemented in cubase instead of a workaround like this. But unfortunately, it seems that MCU functionalities of cubase are the same for a looong time and I don’t see it changing in a near future.

Cheers,
PG

Nerdy, perhaps, but still pretty cool.

[ChrisDuncan]

@mjdevries

Seems its integrated with Logic.

From my experience, the X-Touch does a pretty complete implementation of the Mackie MCU protocol, so it’s not specific to Logic. It’s just that Behringer’s videos focused on Logic in their demos rather than showing it with a lot of other DAWs, and if I recall correctly (I no longer have an X-Touch) the button labels may have been presented from a Logic perspective as well.

So, anything you can do with the MCU protocol, be it in Cubase, Max, etc. is most likely supported on the X-Touch. You just have to figure out which buttons map to what, which was where I spent the most time.

[ChrisDuncan]

@mjdevries

y a cheap laptop Stand at IKEA , that did solve the problem perfect for me. Just € 4,99
Alle producten. Bestel online of kom langs! - IKEA The size fits perfect

A much more elegant hack than my rolled up towel.

[pgstudio]

@mjdevries

Hi pgstudio,

I love the Behringer X-Touch its a super DAW. I can handle the nerdy stuff to make it work haha. But before i take a dive in to this, is it also possible with the Pure Data or max to use it to control the settings of a VST instrument like for example an Sampler or Synth ?

Seems its integrated with Logic. Seems its possible as i see the info on max, do you have some experience with this ?

I work with the Free VST TX16Wx Software Sampler, Witch is a great piece of Software sampler, used to work with Roland S-330 Sampler in the past This TX16Wx is doing the job perfect like the parameters i use to have on a Roland.

Hey man,
To controll parameters of a plugin or a synth you don’t need any workaround. It just works straight out of the box. But in my opinion, it’s not worth the time/trouble to access the parameters. It’s better to go with the mouse or even an iPad with TouchOSC/Lemur/Metagrid will do better.

[deetee]

Ive read everything i can on this and have been using my X-Touch with Cubase 10,10.5 and had no problems. Where i have run into a problem is I wanted to add an expression pedal so plugged it in and got nothing, i then worked out the only way for the expression pedal to register in cubase was to change the setting in the midi port setup to select the “All Midi In”. This now allowed me to see that the expression pedal would sending out CC46, the problems is that touching pretty much any other button on the X-Touch also caused a variety of midi note on, cc messages to also be sent.

So does anyone know how i could set it up so that only the expression pedal sends the CC message and no other buttons, also i dont know how you can change the CC number that the expression pedal sends as there is no editor like the compact version so if anyone know how to change this as well would be appreciated.

[cparmerlee]

@SteveOakley

well it works, barely. Compared to near seamless feels like it was built for the app integration with Logic X, Cubase integration is VERY lacking and not terribly stable. some times controls lock out and quit working, especially the transport controls. in logic you can just power the X touch up and down, in CuB you have to quit the app, repower the xTouch then start Cub again. really poor and not really what I’d expect. many of the buttons are also either not implemented in CuB or work incorrectly. its at best about a 50-60% implementation.

I use one with Windows 10 and Cubase 10.5. It works OK for most of the regular stuff like transport, punching, saving the project etc. I use the faders and pan, but it seems awkward to use for any of the other VST controls so I just mouse those.

The only real problem I have is that sometimes if I am nudging the fader just a little bit, Cubase pushes it back to where it was before the nudge. In those cases, I have to make fine adjustments with the mouse, which defeats the purpose of having mechanical faders. It is as if I have an automation curve that is pushing back to the X-Touch – but there is no automation on that track.

Also sometimes the faders have become entirely one-way – they move in response to changes in Cubase via the mouse, but Cubase won’t recognize any changed in the X-Touch faders. In that case, I usually power everything down and boot clean. That happens every week or two.

The big transport knob seems pretty worthless. It is not smooth mechanically and it moves the cursor way too slow to be much use. There might be a shift sequence to move it faster, but if I have to use two hands to move my cursor, I’d rather just use the mouse or computer keyboard.

[ChrisDuncan]

@cparmerlee

The only real problem I have is that sometimes if I am nudging the fader just a little bit, Cubase pushes it back to where it was before the nudge.

I don’t know if this applies to your situation but thought I’d share in case it’s helpful.

I experienced this behavior, not just with the X-Touch but also the Mackie MCU I replaced it with. I also own a few of the CMC controllers, which I use in the live room. What I eventually realized is that having two controllers meant contention between the two, i.e. it wasn’t my X-Touch or MCU, or even the Cubase mixer that was pushing back, it was the other controller. Once I disconnected it and had just a single controller, be it the X-Touch or the MCU, the problem went away.

[cparmerlee]

@ChrisDuncan

I eventually realized is that having two controllers meant contention between the two, i.e. it wasn’t my X-Touch or MCU, or even the Cubase mixer that was pushing back, it was the other controller.

Interesting. In my case, I have just the one control surface.

[ChrisDuncan]

@cparmerlee

@ChrisDuncan

I eventually realized is that having two controllers meant contention between the two, i.e. it wasn’t my X-Touch or MCU, or even the Cubase mixer that was pushing back, it was the other controller.

Interesting. In my case, I have just the one control surface.

Yeah, that was along shot.

[BigSmo]

Hello, I’m getting issues using the X-touch in Nuendo, none of the buttons do what is expected like in other DAW’s.

Is there a work around?

It looks like the x-touch one works well with Cubase, the Click button etc works as expected but I just cannot get it’s big brother working properly.

Any help would be appreciated.

[tcastigl]

@cparmerlee

I use one with Windows 10 and Cubase 10.5. It works OK for most of the regular stuff like transport, punching, saving the project etc. I use the faders and pan, but it seems awkward to use for any of the other VST controls so I just mouse those.

The only real problem I have is that sometimes if I am nudging the fader just a little bit, Cubase pushes it back to where it was before the nudge. In those cases, I have to make fine adjustments with the mouse, which defeats the purpose of having mechanical faders. It is as if I have an automation curve that is pushing back to the X-Touch – but there is no automation on that track.

Also sometimes the faders have become entirely one-way – they move in response to changes in Cubase via the mouse, but Cubase won’t recognize any changed in the X-Touch faders. In that case, I usually power everything down and boot clean. That happens every week or two.

The big transport knob seems pretty worthless. It is not smooth mechanically and it moves the cursor way too slow to be much use. There might be a shift sequence to move it faster, but if I have to use two hands to move my cursor, I’d rather just use the mouse or computer keyboard.

Hi, If you ever find a solution to the fader nudging issue please post it here. I have the same problem and it is really the only annoying thing I experience with the unit. Exactly like I have automation running and I don’t. Have not been able to solve this problem.
Thanks.

[AMPAGE]

Can anyone with X TOUCH ONE (the smaller single fader version) and Cubase 10.5 confirm 100% for sure that a footswitch can be used to start and stop RECORDING?

[AMPAGE]

bumping for viz.

i am considering buying an x touch one to use with 10,5 pro

can anyone please confirm the footswitch input can be setup for RECORD start/stop?

[AMPAGE]

I bought an X touch and just want to let anyone else know the footswitch record works perfectly.

[Danix78]

hi, how do you control the parameters of the VIs? X-touch controls the DAW, but when we have to control a VI what is the procedure?

[111348]

Bonjour les musiciens, j’ai une x-touch, j’ai remarqué que les fader font du bruit bizarre en automation, es ce que c’est normale ? Si pas normal c’est quoi la solution

Merci