I heard similar stories. Their rep is not the best for a reason. Yet, we keep buying stuff from them. They win by the sheer amount of sales, not from their quality!

I am running the latest 1.10 firmware. I already wasted hours trying to make it work as it should. Thanks.

This is just how it is in Pro Tools. Mine currently sits around gathering dust. My son likes playing with it though, and watching it move

I am a Logic user at the moment and just got one of these. I decided to get the One instead of the larger one, for reasons of physical footprint as well as not wanting to spend 400 usd before I even quite know exactly why I am buying it. I know I need a convenient transport control, and without any setup the X Touch One handles that well. Beyond that, maybe switching between tracks, scrubbing, nudging, not sure.

Can you send the X-Touch midi or other messages from the DAW, or from another device? I have a problem with a missing feature in Logic and it just occurred to me maybe I could script the X-Touch itself to help with this. The thing I need to do is imitate "Wait For Note" midi recording, which is to me really import at certain times to punch in exactly on the one, like with drums.

It's just an MCU. You can customise all the controller assignments, or addd your own if you can design the handling in such a way it doesn't interfere with existing functionality.

How exactly would you be expecting to implement that? With a control surface? Talk me through your strategy for implementing this feature...

Doesn't a count-in help by indicating what the recording tempo is going to be before you start recording?

um well in many cases the count-in is good. But in many common wait-for-note scenarios, the one I use most often is on the MC909 or the MPC 4000, when you arm the recording in "wait" mode, the metronome starts, to cue you to the tempo. then you punch in and your first note becomes the first note of the measure.

it is very useful in certain cases, like I really need it to save time when doing drums.

I am not sure how to implment this.

I am aware that Logic has scripting. I was thinking of maybe detecting any midi note in a logic script and then simply call the scripting function to start recording, and then send the detected note through to the environment somehow?

I have done some midi scripting in Gig Performer and I have the code written which listens in a midi port for any midi note, and then sends the correct midi message to Logic to start recording through IAC. The actual midi note(s) to use I am not sure of yet.

It occurred to me that since the whole job of the X-Touch is trafficking in these kinds of control messages, maybe I could send the start recording to it, but I think its not necessary.

Long story short, every DAW should have "wait for note" it is super useful and doesn't detract from the other amazing ways to count in or start recording midi.

Ok. Yes, this has nothing to do with the controller as such, more just a way of MIDI-triggering the recording. You can do this easily enough by dedicated a MIDI button or key to start recording, but you want to do it without losing that triggering note due to the controller assignment, which is a bit tricker...

I can't remember whether Scripter will output MIDI events from it's inserted channel strip, or whether they are internal to the channel strip only (I suspect the latter, but I'd have to check to confirm). Most likely, you'd have to rig up an Environment solution, but maintaining and resetting state would be tricky.

(I'm also not sure offhand whether you can control Logic's transport via Scripter either... Again, would need to check). Here's some tips on detecting the play state that could be useful:
https://www.logicprohelp.com/forum/v...c.php?t=147901

(Edit: Looking at the API, I can't see any way to remote control Logic from a Scripter script, so I think that's probably a non-starter.)

In essence, you'd have some kind of "wait" state, then when a note comes in, that is essentially transformed into another dedicated MIDI event that is sent out via IAC and back into Logic, which is learned to trigger the recording, and the state is put into a "recording" state so no further MIDI events trigger this, until Logic is stopped again.

The downside here is that sending MIDI events out and back in via IAC will involve latency, so Logic might miss the first event or so (again, would need testing). I guess you could also resend that trigger event but it's all getting a bit hacky...

I seem to remember there was a reason they removed the wait for note recording option (it used to be there some time ago).

No, the controller wouldn't be involved in this.

Yes, I'm aware some people like the feature... I wasn't being critical of it, just that it's not something that would be easy to add in the way you would like.

But by all means, try investigating and prototyping some ideas, and see whether you can get something that behaves how you'd like - and let us know how you get on!

I will probably try to use the X-Touch to send some custom message to Gig Performer to get the whole chain going. While there may be some latency on that first note, its better all in all to do it this way, and then worst case nudge that one note if I perceive a timing problem, instead of having to nudge the entire MIDI sequence in Logic using regular count-in, in the event that I cant readily align my timing exactly on the grid, which is a bit hard with the 5-8 ms latency from the speakers to the pad back to my ears etc.

Is there a way to change the volume of the return tracks with the fader? Here it's only possible to select the "normal" tracks and change the volume. When I select a return track the unit displays "select bank". Many thanks!

Have any of these issues been resolved in recent times with either Behringer firmware or Cubase 13?

I like what I see of the Behringer XTouch One but it seems like this Cubase issue is a dealbreaker.

I use an X-Touch One with Cubase 13 and have done since version 10 - it's been flawless. Everything works as it should including bank selection.

This is good to know. Thank you. Any idea what those issues they were experiencing in above posts are caused by?

No idea, setup mistakes? I even managed to spill a mug of tea on my X-Touch and it survived!

That hasn't anything to do with set up mistakes. It is the protocol the thing is using and how strict cubase follows it.
If you use the intended Mackie Control protocol with it in Cubase and you control channel 13 with it and then click on channel 4 in Cubase you can not control it with the controller because the channel is in a different bank.
You have to change banks on the unit until you are in the right bank. On a 50+ tracks project this thing is practically a brick.
On newer cubase versions you can create your own map for this thing, but I own that one and I don't see it as my job to fix stuff that is wrongly made in the first place.
The old faderport used it's own protocol and it worked flawless ignoring all the bank nonsense that makes absolutely no sense for a single fader controller.

So what? The whole point is hands-off not click and control. 50 tracks is 6 bank-scroll clicks on the X-Touch to get from one extreme end of the mixer to the other which you can do in the blink of an eye (and would require mouse or keyboard shortcut scrolling anyway.) Most of my projects are in the 50-100 track range, bank scrolling in projects that small is no hardship and you tend to work in audio areas at a time anyway, ie drums or vocal or synths which should all be grouped and coloured nicely - obviously if I was scoring with 500 tracks it's a different matter - this isn't a problem with the X-Touch, it's a protocol thing as you know.

Calling this very useful controller a brick because you are so adverse to bank scrolling is a bit hyperbolic.

Yep.

That's because Cubase isn't implementing the MCU protocol in the way it was intended. it's *always* been a fader bank-related format, by default the MCU always responds to 8 channels per fader bank (although that increases with each extra unit in a control surface group), regardless of how many faders a hardware unit decides to have.

What happens in, eg Logic, which the MCU protocol was designed for, is that if you select a track from a different fader bank (ie, lets say you have track 7 selected (in fader bank 1 of 8 channels), then select track 26 (selected track is now the second of 8 channels in fader bank 4), Logic switches to fader bank four, and selects the second channel, so the MCU control surface can update it's status accordingly, and control the right set of faders.

And so, for Logic, the XT One behaves as expected - any channel you select in the DAW, by whatever means, is the channel the fader will control, and you can forget about fader banks completely, it's invisible and just works. I rarely use the bank switching on mine, I'm always selecting tracks I'm working on by other means (either onscreen, or from the keyboard or other MCU controllers). Sometimes I'll scroll up and down the tracks, I guess. Anyway, I really like the XT-One, it works great for me (in Logic).

I guess you should submit this as a feature request to Steinberg, if they listen to requests, to get this implemented better for any single-channel units that use the common MCU protocol.

I appreciate everyone’s viewpoint. I am surprised years later that Steinberg and or Behringer haven’t solved this the way it seems to work better on Logic. Maybe it is not a deal breaker but it does seem to make things more of a chore.

I’m curious, why hasn’t anyone given all the Cubase users complaints, created a fix with map for this?

There’s many things I like about the Behringer look and functional features but I agree with you that dealing with this banks stuff might make me feel like this is more work to do. I am shopping around for a control surface because I thought it would speed up my workflow compared to mouse/keyboard but this seems to come with its own things to deal with.

Is there any product you’d recommend for me to consider since you called this one a brick?

Thank you and everyone that has chimed in.

Something with a self programmed integration like the first faderport.
I don't know if it is possible to overcome this issue when using the Mackie protocol.
I will try the new icon nano but am prepared to send it back.

I checked the Steinberg forum and found a possible recent recent script and video that solved the bank issue.

https://www.youtube.com/watch?v=o_gV...7s&pp=2AEHkAIB

As I said....
I don't know if the time display on the unit works with this method.
I got it working with a custom XML on Cubase 11 as well but without time display etc.

I just got a X-Touch One and was ready to send it back till I watched this and downloaded the script. A few simple changes and it's working as I would hope it would (except motor noise, whuich may be defective)
https://www.youtube.com/watch?v=YmPj3136PkI
I use it in Nuendo/Cubase