Really simple to reproduce using Behringers X-Touch (with latest firmware) all set up and generally working well with Cubase except for this event.
-Start Cubase.
-Open a new project and select, for example, the 16 channel recording template.
-Once opened, on the x-touch press Enter + one of the buttons next to “Global View” (Midi Tracks, Inputs…etc).
Expected behavior (according to the Steinberg Remote Control Devices - page 10) , is to “To apply a particular channel type directly to the channel set”.
Instead Cubase freezes. Open Task Manager and it shows Cubase Not Responding.
On the other hand, pressing one of the same buttons without Enter works correctly and one of the first 8 individual Channel Visibility Configurations is applied to the channel set.
Yes, it is set up in Mackie. In fact I have both the main X-touch and the extender and they both are configured correctly and work well with Cubase.
I can control the faders,pan, EQ, and so forth. I can even apply my saved channel visibility configurations. Its only that one combination of keys that seems to cause a problem.
Regarding the function to be triggered: Here’s a snippet from the Steinberg Remote Control Devices - page 10):
To apply a particular channel type directly to the channel set, hold down SHIFT and press the corresponding button 1 to 8 in the right FADER BANKS section. This setting is not reflected in the MixConsole.
The following button combinations apply:
All channels: Hold down SHIFT and press button 1or button 8.
Audio channels: Hold down SHIFT and press button 2.
Groups: Hold down SHIFT and press button 3.
FX channels: Hold down SHIFT and press button 4.
Sorry, I don’t understand, what is the link to the “Steinberg Remote Control Devices” document, please? Where does this document come from? Could you send a link, please? Is it Steinberg document or Behringer?
It states “To apply a particular channel type directly to the channel set, hold down SHIFT and press the corresponding button 1 to 8 in the right FADER BANKS section.” When I do that Cubase freezes.
And yes, x-touch is in Mackie mode and set up and working for all other functions.
I see. I think I start to understand what’s going on here.
This is the original Mackie Control Universal hardware. This is Cubase/Nuendo template on it. As you can see the Shift button on the Cubase template is the Enter button on the Mackie Control Universal unit. So you have to send the MIDI message of the Enter key, not the one which is labeled as Shift.
So in your case, hold down Enter and press corresponding button 1 to 8 in the FADER BANKS section. Now, where can you find the Fader Banks section at your X-Touch? Again, if you have a look to the Cubase/Nuendo template, you can find out, which buttons are these on the original Mackie Control Universal unit. And as you can see, these buttons are originally named: MIDI Track, Inputs… User. So on the X-Touch these buttons are the 8 buttons above the Function F1 to F8 keys: MIDI Tracks (= Fader Bank 1) … User (= Fader Bank 8).
Thanks for responding. Everything you mentioned I had come across when I was researching how to use the X-Touch (Behringer documentation is nearly zero). So I was aware of the Shift/Enter issues.
However the issue is still the same. Using the “Enter” key (labelled Shift on the device) with any of the 1-8 buttons causes a freeze in Cubase. Using the 1-8 buttons WITHOUT the “Enter” key works well and applies my own visibility configurations correctly,
Bottom line: What is causing Cubase to go “Not Responding”…? Did the dump file I linked indicate anything?
Thanks again for taking the time to look into this.
You should use the key, which is labeled Enter on your device, which means Shift for Cubase. Please, press “Enter + Inputs” to show Audio Channels only, as I mentioned above.
Sorry, I forgot and at this moment, I have no the device, where I could resolve it again.
Could you please set the MIDI Input of the Mackie Control to Not Connected in Cubase, then add a MIDI track and add MIDI Monitor Insert plug-in to the MIDI track. Then press the Enter button. The press the Inputs button. What MIDI Messages did you get, please? Enter button should send MIDI Note A5 and Inputs button should send MIDI Note D#4 (if this is “Fader Bank 2”).
I did what you said: here are the results:
Enter button sends B4
Input button for Fader Bank 2 sends D#3
So I went looking for which buttons send the notes you were expecting:
A5 is sent by Transport Stop
D#4 is sent by Automation Write.
I found a Midi Implementation Chart for the MCU protocol on this page Mackie Control MIDI Map which shows yet a different set of notes for these functions.
On the webpage you sent, you should have a look to the last column (in the red area). This is the default label on the surface. The 1st column is as labelled by the lexan overlay for Digital Performer.
So again, the last column Enter (= Shift for Cubase) is note A5. The F9-F16 from the default label (= Fader Banks 1-8 for Cubase), are MIDI Notes D4-A4. Do you should find, which buttons are sending these MIDI Notes (A5 and D4-A4). Thy couldn’t make it more messy in Behringer… Are you sure you are in the Mackie Control Mode?
B4 (your Enter) is an Option key at the default label. D#3 is not specified for Mackie Control Protocol.
I am getting exactly the same behaviour as Zeid in Cubase 11 with x-touch and 2 extenders. That is the enter/shift button combined with the Fader Bank button causes Cubase to hang.
Without the enter/shift button it calls up channel visibility selections correctly on the x-touch mixer only
and not the Cubase mixer or Cubase tracks (contrary to the Remote Control Devices manual).
Martin asked whether x touch devices are in MCU mode and, yes, all are.
Finally, when Cubase crashes it also switches out the audio driver for some reason. But Windows and other software (eg Cakewalk) continues to use the driver specified after the crash.
What MIDI Message do the Shift/Enter and Fader Bank buttons send, please? I would review on the real Mackie hardware, which function is triggered in Cubase.
I’m getting the same issue using 2 x SSL UF8. Works as expected with one unit configured, but with 2 units using the shift button and selecting one of the 8 buttons for channel visibility, it causes Cubendo to hang. It reliably hangs anytime that combo is used and task manager needs to be used to quit and restart. All other fun tons work as expected when using an extender. So, basically exactly as originally described in previous posts.
Anyone found a workaround for this? Is this on the Steinberg side or something hardwired into the MCU protocol. Any help would be appreciated, as I’m trying to work out whether I send the second unit back. Thanks