Behringer X Touch Controller

Suprawill1 · January 29, 2018, 3:57am

Yes, it seems none of the known local stores are stocking it. Even some of the popular online stores.

chocobo · January 29, 2018, 8:31am

Jazzius:

Here’s a downside:

i haven’t used it too much, but when i did, this is what happened:

Imagine you use a motorized fader to record some automation. You then play back and the fader moves on it’s own according to that written automation.

Ok, you want to tweak the automation, so you grab the fader as it’s moving in “takeover” mode and move it some more. Now, at that point Cubase ignores (deletes) the written automation and starts writing your new automation as you move the fader.

BUT: the problem is that the new automation doesn’t start smoothly at the level where the old automation stopped and the new write began. There’s a jump in automation, like the fader isn’t calibrated properly, so, for example if the fader is 35mm up from the bottom it’ll write a value of 60, but next time it’s in the same position it writes 70. So you get these jumps in the automation.
Sure you can go into Cubase and manually smooth it after the fact, but that kinda sucks as this thing is supposed to be improving workflow.

It could be that i’ve got a dud or there’s some way to calibrate it, but here’s the other good news:

THERE’s NO MANUAL!!!

Really! I emailed Behringer about it and they said tuff luck, that’s the way it is.

The X-Touch is cheap, and i fear that it promises just a little too much for what is actually realistic at that price point (but no manual??)

Thank you so much for the information! Automation with motorized faders in an affordable package is the whole appeal for me and the behavior you described is just intolerable…

Suprawill1 · January 29, 2018, 9:05am

Also bear in mind that what Jazzius described only happens when writing in the “takeover” mode. The transition is sloppy but the fader reading initially worked fine.
I’ve never seen a takeover function for automating in Cubase but it’s nice to know that Cubase supports that. If it doesn’t, maybe it doesn’t implement that feature offered by X Touch. Thoughts Jazzius?

SuperG · January 29, 2018, 9:33am

Jazzius:

SuperG:

I think it’s safe to point out to everyone that issues and personal peccadillos pointed out here have nothing to do with the X-touch, and are intrinsic to Cubase’s controller implementation. Things like fader jumps are normal behavior in any Daw - naturally, if your automation lane jumps, so goes the fader.

Read my post again carefully. In what sense is it “safe to point out”?
You’ve just made a blanket statement that it’s the DAW at fault, but what evidence can you offer to back up this claim? Have you tested it in the exact way that i describe?

What i describe can’t automatically be blamed on the DAW. Maybe it is a problem with the DAW, or maybe with the X-Touch.

As i said, maybe my X-Touch is faulty, but i don’t know that for sure as it’s a sample based on a grand total of 1.

I’d advise the OP to get one to test before plunking down his cash.

I’ll stand by my statements.

First off, the x-touch is completely unaware of whether automation is new, old, or otherwise, and so it categorically cannot return a different value depending on “new” or “existing” automation. It is essentially stateless.

Secondly, you can easily prove calibration simply by picking a spot midway, say one of the marked indexes on the x-touch fader strip.

Just grab a fader, move it to the top and notice in cubase that the value shown in the corresponding cubase fader is maxed. Move the fader to the spot you selected and note the value. Repeat the test - you should be easily able get to within a few counts, every time. You can try the same test from the bottom, same results. You can do these tests with the transport stopped. You can do these tests using the well known utility Midi-Ox as well and observe from there. Same results. If there is any fault in calibration, it will show up here in these simple repeatability tests.

OTOH, you can get “jumps” in written automation which don’t necessarily correspond to fader position if you have cubase’s trim mode engaged - and this is because trim mode applies an “offset” (based on the fader position) to the existing automation, not an absolute value corresponding to the fader position. This behavior is as designed.

husker · January 29, 2018, 4:21pm

For somehow who actually has this unit - I have a dimension question. The specs list that it is 3.9" tall. Is that the height at the back of the unit, or is that the height including the knobs?

mdr_uk · January 29, 2018, 6:16pm

Oh, one other thing that may trip people up - the buttons’ actions don’t match the labels on the unit. However, there are a set of overlays that users have created which show how the buttons are mapped under Cubase - see direct PDF link here: https://forum.musictri.be/attachment.php?attachmentid=1013&d=1447342977 and forum discussion here : https://forum.musictri.be/showthread.php?9134-X-Touch-Overlay-for-Cubase

SuperG · January 30, 2018, 1:08am

I stuck a ruler next to mine and roughly eyeballed about 4 inches to the top of the pan pots - yeah, that spec is probably inclusive of of the knobs.

husker · January 30, 2018, 1:12am

Thank you. So it is probably 3.5" at the very back? 3" at the front?

SuperG · January 30, 2018, 1:21am

That site is helpful, and a printout of the Cubase controller pdf will help until you get a comfortable workflow established.

I created a document in Word which contains the correct labels for Cubase too - you just print it out on sturdy glossy photo paper, 4x6 will do. You just cut strips out from it, and attach to the top of the unit above a row of buttons with just a touch of good ol’ rubber cement. Nothing permanent that can’t be easily removed.

If anyone would like a copy, feel free to pm/request a copy - it’s just a Word doc.

SuperG · January 30, 2018, 1:27am

Something like that, yes, but I don’t have a way to exactly measure it. It does command a bit of presence on your desktop, but during the mixing stage, the workflow benefits make it very much worth the space.

husker · January 30, 2018, 1:47am

Thank you much SuperG.

carvingcode · January 31, 2018, 11:29am

I tried one for several days. Cubase support for the controller is lacking compared to how the X-Touch works with Logic. Logic uses the X-Touch buttons in the way they are labeled on the device. Cubase remaps a lot of them and doesn’t seem to use some others at all.

I returned the X-Touch. Not really a fault of the device.

husker · January 31, 2018, 7:34pm

I think I am going to go with the Nektar P1.

SuperG · February 1, 2018, 1:27am

Exactly! The unit is a clone of the Mackie MCU Pro (better looking IMO), operation of the unit is the same for both. Everyone will ultimately have a different experience using a controller. In my case, I was happily surprised in a positive way, coming over from having used it in Sonar.

YMMV!

Suprawill1 · February 1, 2018, 5:21am

That is the height of the back of the unit including the knobs.

Suprawill1 · February 1, 2018, 6:25am

mdr_uk:

I have one, and it works great with only two downsides. The “forward” and “reverse” transport buttons do not move the cursor according to the snap settings (I’d love it to only move in increments of gridlines, depending on how far I’m zoomed in), nor does the jog/scrub wheel.

The wheel also moves in tiny increments which I find infuriating, as I end up scrolling for ages to get it to move where I want it. I notice that it doesn’t do this in other DAWs (I’ve tried the Xtouch with Studio One, Sonar on Windows, and Logic) In the end, I largely just gave up on those functions. Otherwise, it’s a great unit.

Do any of the above posters have a fix for my two transport-related issues ? I’ve looked at everything obvious in the Cubase settings but nothing I’ve tried there has made any difference so far.

Ok, here’s what I’m experiencing. I’m in the early learning stages as I have just purchased it.

The jog wheel does move in 1/16 note increments. I’m pretty sure there’s a way to adjust the increment size, just have to experiment more.
I don’t believe it’s designed to act like a fast scroller. Cubase will have its own protocol for this so it will function differently than your other DAWs.
That being said, it’s on Cubase, not the X Touch.
The fast forward/rewind does not move in increments but I believe it’s designed that way intentionally. Hence “fast” forward. It’s designed to get you to your bar destination quicker and then you dial in with the jog function.

Suprawill1 · February 10, 2018, 7:10pm

I’ve had a chance to work with the X Touch and found there is an alternative to using new overlays to justify the right button functions.
In fact, I can reprogram “all” the buttons to respond to the designated labels on the the hardware. It’s more time consuming but the results are finite and can be saved.

digitalson · February 10, 2018, 9:06pm

As far as the automation goes I put my return to the highest amount that it will go I think it’s 2000ms so when it stops writing automation it takes 2000mseconds to go back to the other point nice and smooth

mdr_uk · February 11, 2018, 9:26am

How? I’ve seen the function key mappings in the Studio Setup dialog, but have missed how to reprogram anything else. This would be a total game-changer for me!

Suprawill1 · February 11, 2018, 9:52am

The “Mackie Control” has most of the mapping right with a few exceptions. To reprogram all of the mapping, you have to create a “generic remote”.
That mapping page has a “learn” function that enables you to program each function. In the map page, you rename the control name, click the “learn” square, then push the corresponding button on the remote device. I’m on the way to creating new mapping which I can save on export. This may take me a while as I will create in spare time but when I finish, I can provide a template that can be reprogrammed for minor alterations.