Wait.
Auto-banking actually works with this script? Just to clarify, track 1 is focused in Cubase. Then I focus track Cubase track 137 and my X-Touch automatically shows track 137 without me pressing the bank button 17 times?
If so I might join the party.
Yes indeed. Itâs awesome.
Hi @blissdrums,
glad to see thereâs another MCU Pro user here! I silently started working on an MCU Pro version of the script this week, the pull request is here #11. Would you mind coming over to GitHub to discuss any MCU-specific issues directly in the MCU Pro pull request? Maybe @skijumptoes can also help us there.
@bjoluc ,
Awesome, thank you⌠I have created a Github account and posted to the page. Iâll give this new script a try and let you know!
@bjoluc ,
Is there a PDF or another document that nicely lays out all the functionality that your script adds beyond the standard MCU? Is it just that readme.md doc on Github? This would be a great help to take advantage of the added functionality. I love the color added already.
Thank you for your hard work. Very impressive!
I do not have the Compact and also do not know the documentation of the device.
Sorry
How would you envision such a document, besides whatâs in the readme? And is there anything I can improve with the readme? Happy to take suggestions for both. Ideally, Iâd like to keep one place to document everything and the GH readme is very convenient for me.
Iâd say no. This script might work to a certain extent, but I think creating a dedicated (non-MCU-based) X-Touch compact script would make more sense (Iâm not going to add support in this script). If youâre thinking about getting a DAW controller, consider investing into an X-Touch â the extra features are totally worth the price IMHO!
Hi mate, havenât tried your script because I donât own such controller, just a question: Do you update the MR UI accordingly? The more I use the UI the more I realise that documentation can become less necessary 
Fair point, the UI shows how everything is mapped too.
When switching Fader banks, itâs always jumping 8 or 16 faders, depending on if there is a extender connected or not. Would it be possible to always limit it to 8 channels only, even when 16 faders are available?
Hi @mat,
the MR API only offers banking actions for all channels, so thereâs nothing I can do here (despite repeatedly shifting by one channel which would run everything but cleanly). I like the way it works though 
Hi @bjoluc,
when I create a new project, or open a previous project, the X-Touch is not recognized.
What should be done?
Thank you
â > EDIT:
I think I fixed it⌠like this:
1 Open MIDI Remote Manager, Export X-Touch Script (Personal Folder).
2 Open MIDI Remote, Add Control Surface, Import Script (previously exported.midiremote file), Cubase asks to overwrite, ok.
I hope this is the correct procedure!
Hello everyone,
I connected an Extender but I canât complete the procedure correctly with the script.
I followed the instructions:
0 - I modify the behringer_xtouch.js file already present in the behringer\xtouch folder (the one used so far with the X-Touch only)
1 - replace âmainâ â> with âmain, extenderâ (behringer_xtouch.js)
2 - restart Cubase and configure the MIDI Remote by clicking the â+â button in the lower zoneâs MIDI Remote pane.
3 - I set the following parameters (image)
When I activate the Surface I added I have 2 X-Touch MIDI Controllers in the MIDI Remote screen
PROBLEMS:
X-Touch does not respond well
(faders, buttons, etc⌠do not reflect commands correctly, buttons do not light up (select, solo, mute and rec) faders do not move when operated from Cubase. The channel selector only works for the Extender. And much more!
The extender seems to respond well.
Where am I wrong?
In your behringer_xtouch.js, it must be :
devices: ["main","extender"]
Then you must set your parameters with something like this (invert the âExtâ and non-âExtâ, I use it in extender,main configuration) :
Donât use âMIDIIN2â or âMIDIOUT2â, thatâs the MIDI physical ports of the X-Touch.
Okay, letâs start over.
I replace devices in the behringer_xtouch.js Script file
devices: [âmainâ] â devices: [âmainâ,âextenderâ]
I restart Cubase and now it looks like this:
I add a MIDI Control Surface with the â+â button:
I Select from the list the dealer âBehringerâ and from the list âX-Touchâ (should I âadd modelâ?):
Creator of the script (auto @bjoluc), I see 4 midi ports, 2 IN and 2 OUT:
These are the IN ports
These are the OUT ports
I tried with this choice but I had the symptoms described in post 137:
I tried @algradâs solution (thanks), reverse the ports, but it doesnât work:
I keep doing something wrong, but I donât know where. I ask for your help, thank you.
But isnât the Extender already there in the first picture? Why would you need to add a new surface?
