Firmware 1.23 for the X-touch and Extender (2 separate files) has been released and is available on the behringer website.
I can’t find the official release notes.
Hi there, first of all…thanks to Bjoluc for this wonderful script. Last week I bought the X-Touch so I am a newbie with this item. I figured out quit a lot already (thanks to the script) but I’m stuck with choosing the next plugin on the same track. Let’s say I have an EQ, Reverb and delay put on channel one. After choosing ‘Plug-In’ on my X-Touch I expected that I could choose the next plugin with the X-Touch by pressing previous/next channel but apparently this doesn’t work this way. Is there anybody who knows how to operate this feature?
Hi,
I’ve manualy assigned 3 touchs (F6/F7/F8) for this purpose.
Below you will find the links I’ve used (but as I translate from my French Cubase words can be slightly different on your side).
-Selected track/Insert and Strip effects/Actions/Previous insert effect
-Selected track/Insert and Strip effects/Actions/Next insert effect
-Selected track/Insert and Strip effects/Parameters/Edit the plug-in
1 Like
Hi Matthieu, thanks for your quick reply. This is just the solution for my ‘problem’. I’m very glad with this. Thanks again. With kind regards, Ron Weber.
Hi folks, I’m running CBPro13 (pc too old for 14). When I used CB11 I ran everything through the generic remote section and was able to assign a midi note to each plugin slot (midi note 32 - slot 1, 33 - slot 2 etc), so I could just hit a button and whatever plugin was in that slot (usually 1-8) the edit window would open and I could blast away, press it again and it would close. I used this every single mix as I would open more than one plugin to see how they were interacting with each other etc and it made it so fast to open edit and close plugs. It was also great because it meant that if changed a plugin mid mix it wouldn’t matter to cubase that it was a different plugin I was asking it to open because the command was specific to the slot number not the plug. 13 appears to have removed the VST mixer portion from the selectable assignments in the new midi mapping so I can no longer assign midi notes to each plugin slot, it only opens the last ‘focused’ plugin, which seems completely bonkers to me. Whilst bjoluc’s script is awesome (I’m using it now) I find navigating the plugins with it difficult after having it so easy. Are the assignable slots back in 14Pro, will they make a return in the future or am I back to mousing selections? I have to re-write my PlugData patch to accommodate the 16 bank switching issue anyway (screen doesn’t move with bank switch), but I was hoping to not have to mess around with complicated plug scripts. Anyone have any ideas? Cheers folks.
Hey all back again and almost have it all working, one quick question… Has anyone ever had the channel one fader link to the master at opening a project? If so how do I turn that off?
I have previously set up my x-touches with the original generic MC system.
Now I am trying out this midi remote.
Am I correct in thinking that placing the .js file in the correct folder is all I need to do to see the midi device come up? What about the layout? Is that part of the .js file?
I can’t seem to get that file working - and when I add a remote, it just builds a new empty one with a json file, not a js file?
this is latest V14 - wondering if it is buggy?
Thanks
Max
Hi Max, it will work fine on C14. Your best bet is to google Bjoluc and github. When you get to Bjoluc’s github page for this script, scroll down to the Readme section and follow the instructions there. From what I remember, you need to import the script from within Cubase, but the Readme will tell you all you need to know.
Yeah - I got it working - the dash was still in the folder name…
Working on the extenders now - love the coloured displays!
@doctorlaz
Thanks for that speedy reply doctor!
Okay - got the main and extender xtouch working well.
I have two questions:
Is it possible to change the bank amount regardless of fader count? My previous setup with MC paged just 8 channels at a time even though I had 24 faders.
Is it possible to select more than one fader at once with this remote? Like how I can hold shift and select multiple faders with the mouse? This used to work on Cubase 12 but has not worked since - a big slowdown for me…
Hi - is it possible to select more than 1 fader at the same time just from the XTouch? Like holding shift and clicking on a second fader with the mouse to select both?
This worked back in V12 but has been broken since - wondering if anyone has a workaround?
thanks
Max
@bjoluc
I have two questions about your terrific script!
Is it possible to change the bank amount regardless of fader count? My previous setup with MC paged just 8 channels at a time even though I had 24 faders.
Is it possible to select more than one fader at once with this remote? Like how I can hold shift and select multiple faders with the mouse? This used to work on Cubase 12 but has not worked since - a big slowdown for me…
Thanks for any insight…
I have fixed this script for my system.
I use X Touch over RTP MIDI, not USB, so the port names are custom. Edit behringer_xtouch.js, find the detectionUnits array, and add your names. Example:
var deviceConfig = {
colorManager: BehringerColorManager,
hasIndividualScribbleStrips: true,
detectionUnits: [
{
main: function(detectionPortPair) {
return detectionPortPair.expectInputNameEquals("X-Touch").expectOutputNameEquals("X-Touch");
},
extender: extenderPortPairConfigurator
},
{
main: function(detectionPortPair) {
return detectionPortPair.expectInputNameEquals("X-Touch INT").expectOutputNameEquals("X-Touch INT");
},
extender: extenderPortPairConfigurator
}
],
In my case, the result is:
var deviceConfig = {
colorManager: BehringerColorManager,
hasIndividualScribbleStrips: true,
detectionUnits: [
{
main: function(detectionPortPair) {
return detectionPortPair.expectInputNameEquals("X-Touch").expectOutputNameEquals("X-Touch");
},
extender: extenderPortPairConfigurator
},
{
main: function(detectionPortPair) {
return detectionPortPair.expectInputNameEquals("X-Touch INT").expectOutputNameEquals("X-Touch INT");
},
extender: extenderPortPairConfigurator
},
// Your devices drivers names:
{
main: function(detectionPortPair) {
return detectionPortPair
.expectInputNameEquals("Network MCU C")
.expectOutputNameEquals("Network MCU C");
},
extender: function(detectionPortPair, extenderNumber) {
var name = extenderNumber === 1 ? "Network MCU L" : "Network MCU R";
return detectionPortPair
.expectInputNameEquals(name)
.expectOutputNameEquals(name);
}
}
],
Notes:
-
Add a comma after the closing
]if more properties follow in the object. -
Do not add a comma if this is the last property in the object.
-
Avoid trailing commas inside arrays or objects—Cubase’s JS engine is strict.
1 Like
No-one?
Hi,
Cubase 14.0.40 is out. The issue is supposed to be fixed in this version.
uff… installed and by the momemt its getting worse… Activated the script but no really functionall until I opened and closed Midi Script options. Then I see led scribs with color but all the faders down and not responding. Again, oopen and close Midi Remote Assistance button and faders goes to their position BUT in cubase all faders are down…. really Messy….. :-S
Will the auto bank switching issue ever be sorted out? Bank of 16 faders on the desk, move bank along by 16 on x touch, mixer on-screen doesn’t follow until you select a track on the x-touch (or with mouse). I have a PlugData patch that I used to use with my x-touch to automate that process and honestly its one of the most useful things ever (apart from the plugin control - see my previous post). But the new midi remote protocol doesn’t like running the new script with the PlugData patch in the background, so I’m back to moving to next bank, then selecting the last track in the bank so the view follows then selecting the track I actually want, whereas in the PlugData patch you just press the fader bank switch once and the faders move to the new positions and the screen follows. It seems like such an obvious utility function to leave out.
Another reckless like me has updated…?
FINALLY Got it working.
I managed recovering projects without crashing and without faders going down at startup;
1 . Open an old project with Xtouch+Extender phisically off or phisically disconnected.
2 . In Midi Remote Manager IN THE LOWER ZONE (in floatibg windows doesn’t works) delet the third Ghost Midi Remote instance.
3 . Rename and Save project (just in case).
4 . Turn On and/or reconnect the Control Surface and open the recently saved project.
NOTE: in some cases I had to delete the TWO Ghost Midi Remote Instances. Then when reopen with the controls surtface connected I needed to add a new surface (like i had to do always, before 14.0.40). And after that, If if close and reopen C14 finally remembers the Script and its working everything propertly.
1 Like