Hey guys! I recently added an x-touch compact to my setup for Logic Pro X - I've had success using it, but I'd really like to be able to use rotary encoders 9-16 when in in plugin control mode. Is there a way I can do this? In the manual it says that turn is not assigned - so is there a way to activate and assign them? 

I'm having an issue with my BCF2000 controller where two buttons have suddenly started behaiving very strangley. The buttons in question are buttons #47 and #51. Button #47 now thinks it is button #46. When I try to edit button #47 the BCF2000 selects button #46. And for button #51 something even stranger happens. Pressing button #51 once does nothing, pressing it a second time puts the BCF2000 in Edit mode for button #49, and pressing it a third time it puts the BCF2000 in USB Edit mode! 

This happeded when I was recording a MIDI track in Live. I should mention, I use a custom sequencer in Live that comunicates with the BCF2000 via MIDI and I am wondering if somehow a MIDI loop was created while recording and perhaps that may have somehow caused this problem?  

I have tried resetting the Presets and reinstalling the factory firmware but neither has fixed the issue. Otherwise the BCF2000 seems to work fine as long as I don't use those buttons but I would very much like to fix this issue if possible. Anyone here ever experince this issue? Any suggestions would be greatly apprecated.  

Behringer : X touch one 

DAW : Ableton 10

Wondering how to use the faders with automation rather than just volume on projects ? 

csnt seem to find anything online is there a link you could direct me to for mapping this template ?

Hello 

just a quick help link for anyone who gets puzzled when plugging in a controller like the x touch. into cubase and then has the controller's faders trigger midi note on information when a virtual instrument is selected to monitor (by illuminating the little speaker icon next to the rec button under a virtual instruments name)

anyway cubase has this cool feature that allows multi-midi / multi audio instrument simultaneous record cubase's preferences is automatically sent to allow midi thru 

if you have a control surface connected however, you will have to make sure that each midi instrument's midi-input is set to a particular midi input device which is not the hardware DAW controller

otherwise your DAW controller will also send note on / off messages to the virtual instruments that are all set to midi input to all midi inputs (as the DAW also is capable of sending midi data).

If you leave the virtual instrument's input to All midi, and then go to record a midi track say from a midi piano like controller, if you or someone else touch's the x touch faders at the same time, you will get lots of unwanted midi note on / off messages on top of your awesome midi keyboard performance ... which would suck

I also have a problem with the x touch's faders sometimes not working, and i am not entirely sure what that is. but hey ho. i guess i have only had the controller for a few days. 

so.....well see..... at least i am not at the stage of sending it back or smashing it up, through frustration.... any one has any ideas as to why the controller's faders don't work during these times. would be interested in listening to your opinion / help.

thanks

Hi,

I've purchased a Beringher X-TOUCH in August 2021 and it has firmware 1.14

I've tried to upload v1.21 using SysEx App but, after connecting USB and the App detects the X-TOUCH and shows the "UPDATE" device, its starts sending the data but the display on the X-TOUCH shows no percentage progress (as it should) and the update never gets done :-(

Hi guys, I worked on my XTouch with Daw (Magic Samplitude) some weeks ago, everything was fine. But I wanted to start a mix now and discovered that the scribble scrip, channel meter, timer (SMPTE) screen not working. Faders and other buttons worked.... every means of getting it working failed. What could have been the problem and likely solution pls?

I am using an X-Touch Mini with Pure Data, receiving and sending MIDI data to and from it. Mostly, it works very well, but it has one behavior that keeps it from being truly useful for my music.

The LEDs in the buttons can be controlled by sending the appropriate MIDI notes and velocity values, but only if their layer (A or B) is currently selected. E.g. I can send a MIDI note-on of 1, velocity 1, and the first button will light up, *if layer A is selected*. Now, if I switch to layer B and send the same note-on (1, velocity 1), I would not expect the first button to light up, because the first button of layer B is controlled by note-on 25, but I would expect the *state* of the first button in layer A to be updated to 'on' so that when I switch back to layer A, it is lit up. This is not the case, however. Apparently, the note-on is ignored if it is not in the currently selected layer.

Because of this, it is not practical to use the two layers consistently.

Is it feasible to fix this?

Thank you,

Phil

Second attempt as this message as first one crashed, probably due to the amount of time and words it was taking.

Purchased the X Touch and very dissapointed. Great looking and good feel but implementation very poor. Basic stuff works out of box but that leaves a stack of buttons that dont send the command they are labelled with or just dont work. I fail to understand this as the majority of the buttons on the X touch are found in Cubase. Things like undo, save, cancel, shift, click Etc are all mapped to something totally different and cannot be changed. Other controller I have and have had over the years came with software which would allow remapping of the buttons, X Touch does not. OK i though i will simply remap them in Cubase using the excellent generic remote functon. I have used this on loads of gear in the past with excellent results, not with X Touch. While Cubase will accept button presses and save them, they cant be remapped to send to another command. Never had trouble like this in the past other than my last Behringer purchase, the FCB1010 foot midi controller. Again out of the box this was fairly useless and not until I purchased a third party firmware chip was it really usuable. Oh how I wish some clever person would create a custom firmware for the X Touch. This unit is a few years old but still liiks modern and is still for sale under current items on the Behringer site. Therefore I would love to think they actually cared about customers and would release another firmware to fix everything, perhaps creat templated which we can choose upon setting up?

Failing that a software editor should be available. Its like getting in your car pressing the horn and your wipers come on. 

Ihave seen there is a guy that has created some scripts in PureData to try to work around the many short comings of the X Touch, however its not a simple task to install so I am hoping there is another way to get this to function as it should. They should not be allowed to call it universa. The scribble strips dont change colour unless used with another Behringer product, the cursor buttons dont light, infact there are several buttons that dont light even though the website shows they are lit. 

I am now going to look at the possibility of using Midi software to intercept the data from the X Touch and convert it to the correct data for that particular function Etc.

If anyone has Cubase and has this workiing better than it did out of the box I would really appreciate some advice otherwise it will be sold and will be the last Behringer purchase I ever make.

Hello!

I have recently purchased a Xtouch Universal control surface. 

I have managed to link the device to Cubase using Mackie controls and assign tools to the function buttons. There are issues with the transport, global view, automation and utilty buttons not doing as written. The buttons themselves show a MIDI input level when pressed. 

I have updated the controller to the 1.21 firmware.

Please help!!