As a follow up for anyone else who finds this and wants info on the X-Touch with Cubase, I have more information at this point thanks to Robert Lofgren’s help and efforts over on the Behringer forum.
He confirmed (analyzed the midi stream) that the Enter key does in fact send the Shift code. For my initial testing, I tried mapping Shift + F1. He mentioned that there have been some known issues in Cubase regarding the shift + F key mapping in their MCU implementation.
I did a little deeper testing, using MCU / Cubase mode, and can confirm that the shift key does in fact work. Kinda sorta.
- Shift + Master brings up quick controls as expected.
- Shift + Sends, even though the Sends light starts flashing as expected, does not bring up the Cue Sends as it should, but rather just the plain old Sends.
- The buttons to the right of Global View, providing 1 - 8 functionality, do work to bring up the configurations.
- Shift + 1 - 8 has no effect and doesn’t invoke the functionality specified in the Remote Control doc, e.g. Shift + 2 doesn’t show the Audio Only.
Robert indicates that the X-Touch is a 100% compliant MCU protocol device and that anything which isn’t working properly is most likely tied to the Cubase implementation of MCU. Given the effort he’s put in to researching the behavior and analyzing the midi stream, I’m inclined to trust his assessment.
I was becoming frustrated by the fact that it’s so hard to get information on using the X-Touch specifically with Cubase, and because the Shift functionality was flaky had even considered returning it and buying an actual Mackie MCU. Based on Robert’s feedback, about all that would accomplish is spending another $500 to get the same bugs in a different hardware package.
While I don’t own an MCU, I do own a Mackie D8B and have had many other Mackie mixers in years past. The Behringer’s build quality isn’t as good as Mackie - plastic versus metal and generally a bit cheaper in feel.
Mackie support is also massively better than Behringer. When trying to get info from support about the Shift key so I could determine if I had a defective unit or not, I got an email from support that in essence said “It implements MCU, now please go away.” The only useful support I got from Behringer was Robert responding on their forums, which are largely a ghost town (they should stop paying their support staff and give him the salary instead).
With all that in mind, I’ll keep the X-Touch. Mostly because it fits in my console better than an MCU would, and only partly because a Mackie is double the price but would exhibit the same bugs in Cubase. If the Mackie fit I’d be tempted to buy it anyway because they’re a better all around company. This will be my last purchase of Behringer gear.
Hope these notes help anyone else who has purchased an X-Touch so they don’t go through the same frustration that I encountered.