X-Touch One: A Better Script for Remote Nirvana in Cubase

[@balaftuna]

So useful! Thanks for that. I was resenting the X-touch one since I got it and finally we are in friendly terms again.

[@bwithGoldie]

Great Job 👍👍

[@gregormendel1885]

Massive thanks! I only just received the Touch One today and it's now working like a dream - I did start with the MACKIE set-up as suggested by Behringer but now dumped for the real deal!

[@remixk]

you are a genius!! thank you for sharing!!

[@CircusNormal]

Was going to get an SSL UF1, absolutely no need whatsoever now. You just saved me £600 quid!

[@jrgroberts]

Thanks for your efforts. Version 1 installed, now replaced with v2. VERY useful. I had seen the original script but the setup was a bit complex...

[@paulsmusicuk]

Thanks so much for posting this, and for the script! Is it possible to also map the footswitch (which I normally use to trigger 'Record')

[@wzzo2007]

Thank you!!!

[@schragemusik]

Many thanks for this. Very useful.

[@TandisJenhudson]

Many thanks. Does it work both ways, ie select channel on screen -> xtouch follows, select channels with xtouch, cubase on-screen follows?

[@musictechtuition]

Yes, that's it - it stays in sync throughout (more details in the other video)

[@-Deena.]

Great stuff!

[@willynanita]

Can you edit the "master" button to point to the control room level instead of the master fader in the mixer?

[@musictechtuition]

I shall look into that...

[@willynanita]

@@musictechtuition thank you!!! It really is more useful to have it in the control room instead of the master fader…

[@willynanita]

@@musictechtuition Never mind, the script points that button to the control room volume. Thank you.

[@JudgeFredd]

Great ! Thank you !

[@richardarvai4580]

Hey! Is there an option to use the Wheel as an AI Knob with this script?

[@TandisJenhudson]

Do you know if this could be applied to the SSL UF1, which has the same sync issue? Thanks

[@musictechtuition]

I think someone asked a similar question on the previous video on this. I think one thing to do would be to try altering the script to work with the SSL. You can find/replace the X-Touch one in the script with the MIDI port names of the SSL and see if it works?

[@jukkaposti4198]

Thanks again very much

[@zeljkoveljkovic3541]

are there any solution to increase jogger reach ? Now the full round is about 1 sec , and if you work with longer project , it is unusable . Is there a way to turn 1 round to be 10 sec ?

[@MrAlexCasey]

Many thanks! Can I set fader so that I could change CC selected (under mouse) in Cubase?

[@musictechtuition]

Unfortunately not (without Javascript programming, anyway). The Cubase Remote system works in terms of controlling specific Cubase functions, so being able to do that isn't something it can do, I think.

[@edrugmanmusic]

Hi. I have the 8 fader version not the one fader. do I use this version of the script?

[@musictechtuition]

No, you'll want the version from this page - github.com/bjoluc/cubase-mcu-midiremote/releases/tag/v1.9.0 - but you'll need to put it in the appropriate place. That script is called behringer_xtouch.js so you'll need to put it in a folder called xtouch, not X-Touch One as shown in this video at 1:51 - the folder needs to be named the same as the script is after the _ character. Then you'll be up and running with the right script. HTH.

[@musictechtuition]

There's more on the main page of the script on github - github.com/bjoluc/cubase-mcu-midiremote, in the setup section.

[@willynanita]

First, I want to thank you for this... A question: Does the script have several pages? If I use the mouse scroll wheel over the image, some icons change color and functions. For instance, the pan LR knob, when I push it I want it to activate monitor on selected track, but it changes if I move the scroll whell on the mouse or even if I switch tracks... One other thing, can you export the script as you have it and share that file? it's easier to load in Cubase... Thanks again...

[@willynanita]

This is what I mean… kzbin.infoO0WFzu8U52o?si=zRSmY6xcr7XaGybq

[@willynanita]

The script was made for the X Touch 8 channels... I assigned the same function to all push encoders and no more issues...

[@musictechtuition]

Yeah, as you've discovered, when you scroll with the mouse wheel it's showing its origins of 8-channels and cycling through them.... I've updated the page - musictechtuition.com/2024/04/05/updated-behringer-x-touch-one-script/ - with the .midiremote version that Cubase exports for you.

[@willynanita]

@@musictechtuition Thank you! I'm having an issue with track navigation... Pressing the CH button, when the controller gets to the end of a bank it doesn't select the next track, I have to manually select the next track in the bank to keep using the button, is this right? My workaround is using the leftt and right keys in my PC keyboard to navigate the tracks.

[@musictechtuition]

@@willynanita I think that comes from a limitation in the protocol used (it's based on the mackie control, which only uses banks of 8 and I can see that Cubase is highlighting them a bank at a time). You can change to the next bank with the bank change and then move up channels that way. TBH I never use those buttons as I don't navigate with them, but if you want to stay solely on the remote you can do it using bank and then channel.

[@marcinwasilewskipl]

I have a question. Do You know how to get VST Control Room using Midi Remote? There is something like that under Generic Remote. It is useful to control CR's inserts. All the best

[@georgieporgie2087]

Thank you. Worked perfectly until I got my new Mac. I’ve updated to cubase 14, so not sure if it’s Sequoia 15 or cubase 14 that’s the issue.

[@meljames172]

Is there a script for the Behringer X-Touch Compact?

[@musictechtuition]

I'm not sure but I would try changing the MIDI name in the script to that of the X-touch compact and see if it works with it. Other behringer controllers share the same messages (hence the XT1 working by originally changing just the name of the MIDI device), and that may well just work with that done.

[@deanomcbride362]

good man..Thanks

[@petrzeman24]

Hello. Today i installed your prevoius script. I dont understand what is better in this script... and if it is necessary to update from this video🙏

[@musictechtuition]

Hi. The other script works pretty much the same. The main advantage with the new one is that you can assign the function keys easily, and that the appearance in the lower zone in Cubase matches the XT1 (rather than the 8-fader version).

[@petrzeman24]

@@musictechtuition Ok! Thank you. I will check it🌞

[@djrichierichh8519]

Hi thank you so much for doing these.. Just about to begin an opportunity- of -a lifetime project here ( ! ) .. and I'd love to have my x touch One doing the doo properly. My question is based on the fact I'm also running an original big x touch, as well as being an owner of this....I'd rather have the 'One' as the main master if anything for my most basic workflow for the project.. will this work where both units are making sense? I'm looking forward to trying it anyway,of course asap. Thanks again

[@musictechtuition]

@djrichierichh8519 I don't have both to test with, but I'd think it would be totally possible to do what you want, but you'd need to set the XT1 up as seen here, and then you could set up the 8-fader one either as a mackie control or possibly using the 8-fader version of the script that bjorn created at github.com/bjoluc/cubase-mcu-midiremote - you would follow the instructions he's put for that (and I've put in another comment on this video), and you could run both like that. Let us know how it goes (and good luck with the opportunity!)

[@djrichierichh8519]

@@musictechtuition awesome thank you for the reply - Having the 3 different X-Touches must be a first - I just don't have the mini. I 'm going to give it a go.. The compact I hope to not use the faders as they're so loud they drown out the studio speakers. X Touch somewhat quieter.

[@musictechtuition]

@@djrichierichh8519 If you get it up and running, it'd be good to see a quick video of them in action?

[@maciejdzikiewicz6040]

Does the Master Level key work for you? If I press it, the master fader does not work... it is not integrated with the device at all...

[@musictechtuition]

Oddly, I've just checked it and it is now not working... I will see what the issue is and hopefully get back to you...

[@maciejdzikiewicz6040]

@@musictechtuition Thanks!!

[@reid1967]

@@maciejdzikiewicz6040 Thanks for making the video, I just installed and it looks generally great, but I saw this issue with the master fader straight away, I've also had an issue where stepping through tracks will set the fader to minimum which is a bit if a problem. Also, what does 'CH Select' do in cubase? (top row of buttons, third fromt the left) I can't see that it's doing anything except staying lit.

[@jrgroberts]

Right. I'm just trialling Nuendo 13 (Why? hint: proper automation! - and it's more stable even on Mac) and I'd be pleased to say that your packaged script works great on Nuendo - except that it doesn't. What DOES work is to import the midiremote controller script and manually install it.Other than that, so far, so good! Ta again.

[@raincape7042]

I bumped into kind of an issue here: the script is showing in the list in Cubase but it doesn't seem to be recognized as active midi controller so the midi controllers list is empty and the surface isn't showing either. Trying a different USB port did not help. Do you have any ideas on how to fix this? My X-Touch One is working with standard setup though, running on MC Cubase Mode in firmware 1.10. I'm running Cubase 12 on my Windows 11 computer. Thanks for your work!

[@musictechtuition]

Have you removed the Mackie Control device from the Studio Setup page? If not. then it will override the use of the MIDI ports and won't be seen by the MIDI Remote part of Cubase...

[@raincape7042]

@@musictechtuition Thanks for your answer. Yes, I removed the mackie control from the setup page. I tried removing, unplugging and restarting many times :(

[@musictechtuition]

@@raincape7042 OK... so what are you seeing in Studio > Stuudio Setup > MIDI Port Setup? Do you see the X-Touch one input and output in the list there when it's plugged in?

[@raincape7042]

@@musictechtuition Yes, both In an Out of the X-T1 are showing with the boxes checked and in active state. I can even create my own script, edit the controller surface and assign buttons to my X-T1, it's all working. Seems like the script from your tutorial can't be assigned to my X-T1 even though both script and controller are showing up in Cubase. I may try with the version directly from github and give an update.

[@musictechtuition]

@@raincape7042 That is weird....the script seen on-screen is the one I'm currently using in my DAW (I downloaded it and installed it on there from the site, and just re-did this in case there was something wrong). The github one in the main branch won't work without modification as it's for the X-Touch with 8 faders (whose MIDI device is called something different). What are the X-Touch One's MIDI ports names in the Studio Setup? And are you 100% sure the files are in the right folders? Also, are you using OneDrive?

[@محمد-ب-ز7ث]

Hi, thank you for your great and helpful videos. I'm seeking assistance in creating an AutoHotkey script that would streamline filtering in Cubase's MediaBay. I have no prior experience with scripting. Here's what I aim to achieve: - To be able to filter MIDI loops by instrument, key, and genre. - To filter audio loops by category, subcategory, tempo, key, and character. - To filter VST presets by category, subcategory, genre, tempo, and key. Additionally, I want the customization of the filters I make to be saved for each selection, so that the filtered parameters remain individually saved for MIDI loops, audio loops, VST presets, etc. Moreover, I would like to have a shortcut to switch directly between different selections: MIDI loops, audio loops, VST presets, etc. Also, I hope that the filters remain saved in MediaBay so I don't have to reset them each time. Sorry for the off-topic

[@NorthernProductions886]

I this for Mac aswell?

[@musictechtuition]

Yes, works on macOS and Windows - the scripts are platform-agnostic.

[@NorthernProductions886]

@musictechtuition I just downloaded the file but its coming up as a Read Me file instead of Zip folder?

[@musictechtuition]

@@NorthernProductions886 Not sure what's happening there - I've redownloaded it just now from my site, and it's a zip file - musictechtuition.com/wp-content/uploads/2024/04/xt1_updated.zip - How are you unzipping it?

[@NorthernProductions886]

@@musictechtuition Ill try again mate.

[@NorthernProductions886]

@@musictechtuition Still no joy mate. Ive just done a Screen recording

[@LochnessGreen]

👍

[@enzotreppa]

Followed everything. Won't recognize script. Grayed out. Running CB 13 on M1 Powerbook. Relistalled and restarted a couple times. No Bueno..

[@enzotreppa]

I opened Cubase 12 and it seemed to work. Is there an update for 13?

[@musictechtuition]

@@enzotreppa Same script should work on both (providing it's the later script - older one will work but has some minor issues in 13). Does the Xtouch appear as a MIDI device in your studio setup window?

[@enzotreppa]

@@musictechtuition only in 12. But even then the functionality is not all there. I am going to test again. I am also using a Mpk mini. It shows up in 12 also. I was going to try the Makie script and see what happens as well.. Thanks for the reply.

[@musictechtuition]

@@enzotreppa Yeah, I would try removing the script and then see if it works in Mackie control mode via Studio Setup, and take it from there. I did have some weird behaviour at one point as I had both set up at the same time (somehow!)

[@enzotreppa]

@@musictechtuition I can report that the following day I was able to gain most functionality in CB 12. I followed the function buttons assigning suggestion. I can see them on the screen but some are not fully functioning properly. May be operator error as I am brand new to Cubase. Will look into further. But for now thank you for your feedback and assistance and for posting the script. Making it drag and drop is extremely helpful to those of us out here that need this kind of access!

[@-Deena.]

Soooo gutted. Tried everything for days, including reinstalling Cubase Pro 13. Have checked and rechecked the folders are correct and tried every trick in the book and it isn't found. Turned on and turned off Mackie, renamed the js file as one I know works. Checked my general PC documents path as it;s set to a different drive from C, even recreating the Documents Folder on C. Have searched my whole PC for folders called midi remote! I know that this is a bit cheeky but could you export it as a .midiremote script and add a link to that? I could then try importing the script. So disappointed. I bought an X-Touch One just because of this script 😢 *Update* I found a folder called midi remote it in a weird path C:\Users\Dell\AppData\Roaming\Steinberg\Cubase 11_64, added it there and it works!!!!!!!!! There is one odd behaviour I'm finding. Functions 5 and 6, whatever they are assigned to seem to work to open the midi map editor, plus faders and tracks will still will only work on the first 8 tracks.

[@musictechtuition]

Sorry to hear that... your wish is my command (and someone else had asked!), so the script is also as a midiremote file on the link on my site - musictechtuition.com/2024/04/05/updated-behringer-x-touch-one-script/ - let me know how you get on.

[@-Deena.]

@@musictechtuition Thank you!!!!!!! 🧡