Hi all,

I noticed that it seems like there is no MIDI signal generated when changing layers using the layer buttons on the controler.
Is there a way to either detect layer changes caused by the layer buttons on the controler (before another MIDI message unique to the new layer is send), or set feedback (like letting the LED of a button blink or setting the led ring behaviour) based on the active layer ?

This would be useful in order to give visual feedback to the user on states of functions which might get changed externally (e.g. on another controler or in a GUI), if the same physical control has different functions (and therefore different states) on different layers of the controler.

I am using firmware 1.12 (according to X-TOUCH Editor 1.21), using the factory preset for standard midi operation. I send and recieve MIDI messages using a python wrapper for rtmidi on Windows 10.

Greetings,
ebosseck

Hello,

While working on a programm in order to be able to use the Behringer X-Touch Compact remotely with OBS, I noticed that when remote controling the button LEDs, the LED will not turn on if I send the message [145, 0, 1] (Note On, Channel 1, Note no. 0, velocity 1), as it should according to the quick start guide. On the other hand, when I send [145, 0, 2] (Note On, Channel 1, Note no. 0, velocity 2), the LED turns on, as it should according to the manual for velocity = 1. I was able to witness the same off-by-one error for setting the LED to blink.

Is there a off-by-one error in the user guide or am I missing something ?

I am using firmware 1.12 (according to X-TOUCH Editor 1.21), using the factory preset for standard midi operation. I send MIDI messages using a python wrapper for rtmidi on Windows 10.

Greetings,

ebosseck

Hi, I have an X-Touch One for evaluation with Cakewalk by BandLab. It works pretty nice in MC Std mode but I'd like to change the mapping of some keys to have access to FLIP and SEND.

So I switched to MC user mode but noticed that the DAW navigation behaves differently, although no mapping was changed so far. (The Assign feature displays the same name as labelled, for each button.)

After more detailed investigation it is obvious that the Channel> and <Channel button use different events in MC Std compared to MC user.
with MC user: Channel> = C#3 (49), <Channel = C3 (48)
with MC Std: Channel> = C#1 (25) on 1st push, then D1 (26), D#1 (27), ..., G1 (31). With each push the note value is increased, up to 8 times. This corresponds to the 8 channels in the fader bank.
Similarily, <Channel decreases from F#1 (30) to C1 (24).

Questions:

1. Why do the mappings of MC Std and MC user differ?
2. How can I get the navigation behaviour of MC Std with different mappings on keys F1 to F6?

Thanks for your help!

Somethings wrong with my Unit. I use it on Nuendo/Cubase. The fader and a number of buttons were not functioning. I was searching for a hard reset but found none. The Firmware started with V1.04 then upgraded to V1.07 but it will not update to V1.08. HELP!!!

I have a X Touch and the Ethernet Port is not working to be able to connect to our XR18. I updated it to the newest firmware after we discovered that it wasn't working. The activity light blinks on for a brief second after plugging in a cable and then immediately turns back off.

Any ideas?

Hi, I have a couple of questions, I use Cubase Pro 10.5 and the full version of XTouch:

1. Does the Xtouch editor work with XTouch or only X-touch One / compact etc? 

2. How do I activate the use of the footswitch (1/4") to punch in/out? In other responses it has been noted that other units (one / compact) need to be placed into midi mode in order to work. This would remove the normal cubase compatibility functions under the MC protocol which I wish to retain. 

3. When selecting a bank of 8 channels which are not displayed on-screen (if there are a large number of channels) using the fader bank function on the XTouch, the screen in Cubase does not follow the selection of the next bank without pressing the select button for the last channel in the new bank of 8. When it is pressed the next bank of 8 channels come in to view. Is there a way to edit the function of the XTouch so that the view in Cubase follows the selection of the new bank on the XTouch?

4. When scrolling through the plug in list using the rotary encoder (plug-in button selected) the list jumps through plug-ins in groups of 4 or 5, this means that many plugins are not selectable from the XTouch plug in settings. Is there a way to make the encoder scroll through the plugins one by one?

5. The Xtouch One has overlay templates showing the different button assignments for different DAWs is this available for the XTouch?

Kind regards

I have a problem. Just got a brand new X-Touch with a brand new HP Envy completely updated and I cannot even see the X-Touch as a Midi input. Therefore, I could not update the firmware because it is not seen by the program. However, it is weird that I can see it in the Device manager under audio devices. Any help would be greatly appreciated.

Hi just purchase xtouch ( 8 channel ). I have upgraded to the latest version of Cubase 11 pro and updated the firmware to the latest one on the website. 1.2.1.

Alot of the buttons are not working.

Click track button

Had to program it using function keys.

Utility save , undo

marker track

midi track, input, audio track, aux , busses, ouyputs, user buttons all not working

solo button not working

drop button not working

Is there a new firmware update being created so this product will actually work with daw programs