HELP!
C14 needing to reocnfigure manually each time I open C14, doesn’t remember.
Today got woprse, I deleted script as was having a strange functionallity and now I can never use the Script again.
In the Vendor i select Behrinegr but i never founds the script… Also canoot import, as teh script its on gray and impossibel to select…
Are you on PC or mac? On PC:
- Exit Cubase completely.
- If you’ve deleted the script, follow bjoluc’s instructions on his Github page carefully to install it back into the correct folder.
- Unplug the Behringer USB for a few seconds and plug it in again. This often solves some of the strange functionality for me.
- Then launch Cubase. You need to start with an empty project. You should be able to use the Behringer again. If not, just continue the next steps in bjoluc’s Github ReadMe.
- Once the Behringer is working, save the project and close it.
- Launch the project that was causing problems. If it works now, great. If it doesn’t then the glitch is in the project file. You’ll have to shut down Cubase completely, open the empty project you saved in step 5, then import the tracks from the failed project. See my post above.
These steps may or may not work on a Mac. I’ve never used one.
Hi there.
I don’t know when it starts, but i have the problem, that everytime i open a project, i have to configure the Midicontroller again. After that it is working, but when i close and open it again, the controller is gone.
Any ideas ?
Greetings
Oliver
And sorry for the next one. How can i change the speed auf the jugwheel ?
I think that I know why it’s happening. The problem is related with the names used by the script by default to detect the units. I’m using my units connected using the Network protocol, so the names are different for ones expected.
congratulations for your work, it’s great, thanks to you I was able to put my x touch one in script in the midi remote, but how do you do it for the LEDs and the countdown and measurement numbers, my x touch one remains unlit, it only has the transport buttons, the faders, volume and pan it looks lifeless, I use cubase elements 14, and the MacBook pro M4 max sequoia 15, how can you do it, when I had windows 11 it worked well, here we have the impression that it is lifeless, but congratulations because I was able to see the script and well it’s incredible 
In Cubase update 14.0.20, there have been some fixes to Midi Remote API. In particular, there was a subpage bug that I believe was responsible for deactivating the zoom button, or the top row of buttons (First, Pan, Sends etc). The deactivation is then saved with the project, making for many hours of cursing and head scratching. It happens every few days with me, so I’m excited to see whether the new update solves this problem.
I’d be interested to hear from anyone else experiencing this issue, and whether it solves it for you. I know it creates havoc with Nektar CS12 users, and the Nektar spokesperson seems convinced it’s fixed in 14.0.20
I’ve been using the beta for a long time now and It does not fix the issue with this script.
I was just going through my projects where zoom was not longer working.
All of them are working again with 14.0.20 :-))
Regards, Chriss
At least for me: with X-Touch
1 Like
Sorry for going a bit off-topic but does anyone have any ideas on how to turn the X-Touch (Extender) into a usable MIDI CC controller?
If you run the X-Touch (Extender) in MIDI control mode, the buttons and faders send fixed MIDI CC numbers and note values.
I managed to customize the first two faders with the Cubase Project Input Transformer (2 x discard note-on and 2x transform CC numbers), but there are only 4 input transformer modules so this method is rather limited.
I also found this: GitHub - Aldaviva/BehringerXTouchExtender: 🎚️ MIDI controller client for Behringer X-Touch Extender DAW control surface.
But I have no idea how to even install, run and use this and the explanation is really vague with lots of code text.
Currently looking at MIDI-OX for more comprehensive MIDI transform options. Still pretty complicated.
Such a waste that they made the X-touch send fixed CC numbers and notes. At least they could’ve made some software to configure it.
edit: Currently checking out the Bome Midi Translator Pro trial for this. Seems very usable.
Hi there. First of all, thank you for your wonderfull work. Is this script possible to use with Studio One Pro 7?
Thanks
Hi and welcome to the forum,
No, all these MIDI Remote scripts are for Cubase only.
Switch over to Cubase it’s worth doing so. 
I’m on Cubase 13 already, but wanted to use Studio One as my second DAW
Hi there, Nice Script! i am having some issues with automation on the faders though. If i automate a gradual volume increase the fader studders back and forth as it makes it up to the set volume. Please help
I had a situation with that “stuttering”. In my case, somehow I had the X-touch defined to Cubase twice, so Cubase was sending each of the incremental fader moves twice.
I think you can find the details somewhere upstream in this thread.
Thanks for the reply!! That definitely seems like my issue. I found your post from before and will try it tomorrow to see if it fixes the issue!
1 Like
I disabled the mackie control legacy and the fader is still doing the shuddering. Please help!!!
Hi There, thanx for your effort.. Although i can’t get it to work decently I just bought a used x-touch set it up as MC and usb did the firmware upgrade to 22 then installed the script 1.11 in cubase 14 on windows 11 in remote control the script is active. . also tried cubase 12 and finally 11.. encorders seem to live an own life, when i push it up it goes down just as fast.. when ik move e dader in cubase mixer nothing happens / or the fader goes to top or bottom, not in between. but i HAVE colours in the scribble 
i am goeing nuts.. .. any ideas?
and what should happen if jou add mackie control without script, is it suppoded to work but not everything? or nothing happens?
Ans why doesn’t behringer solve this?
I tried downloading the xtouch one script last night as a .js file, but it was greyed out when I tried to import it. I double checked the subdirectories and they appear correct in my local folder.
I ran into this problem trying to import a different script recently. I got around this by finding a .midiremote file if the same map. Is there any way for you to link a .midiremote version of the x touch one? Either here or on GitHub? Thanks!
I know it sucks guys but the answer to your tech problems is currently to just use Mackie Control as there is no official support for any of this via Midi Remote.
A script as complex as the MCU replacement needs to be fully supported by a full-fledged developer - probably Steinberg tbh, but we definitely one of the control surface manufactures to embrace this as heavily as Nektar has . Til then…wild west!