X-Touch (+Extender) MIDI Remote Script (MCU mode)

Cubase
,
204

Ha, funny you mention that…

Right after I posted the comment, I found out about rtpMIDI, installed it, got it working and gave it a spin…

It works, kind of…

I was able to get all 24 tracks working across the three extenders, but the behavior on the Ethernet connected one is a bit erratic… sometimes all the faders would move into position (or just a couple of them), sometimes they would not…
I’d have to move the mixconsole faders in the software, and then suddenly the hardware faders would “wake up” and start to function, but there doesn’t seem to be much rhyme or reason to it…

It was taking up extra space on my desk, and since your usb implementation with just the one extender is so solid, I just said forget it and put the second extender in the closet… I have it as a backup if I ever need it, and I got the extender for free so I don’t really care anyway… lol.

Thanks for getting back to me, and i’ll be working happily with the 16 faders in the meantime.

Cheers

1 Like
205

Ahhh that sweet sound of the fader when the xtouch initializes with a new project! Thank you so much for the update, it was a pain to add the controller by hand with every new project for months. Great work!

1 Like
206

My XTouch has disappeared from C13. Is that the condition you are talking about? It wasn’t clear to me the steps to get it going in Cubase again. But I guess if there is a new version of the script, the best move is to install from scratch using the new script.

207

Yes, it had to be added by hand for new projects.

1 Like
208

I won’t support this in the script, but you can do it anyway by adding the following lines to the very bottom of the script file:

Reveal code snippet 
devices
  .filter(function (device) {
    return _instanceof(device, MainDevice);
  })
  .flatMap(function (device) {
    return device.controlSectionElements.buttons.transport;
  })
  .map(function (button) {
    button.onSurfaceValueChange.addCallback(function (context) {
      button.mLedValue.setProcessValue(context, 1);
    });
  });

This works with the latest version, but I can’t promise it will work with all future versions. If it stops working with any future version, just drop me a PM and I’ll consider updating this message.

209

Well, that’s odd. This exact setup is working for other people, so I don’t think it’s an issue with the script. Sounds like a faulty network MIDI connection to me.

I’m speechless :joy: Pretty sure you’ll find a buyer in this thread :sweat_smile:

210

That’s great!

1 Like
211

Hi mate. Your script is awesome. Thanks so much. I have xtouch and 3 extenders. All work great with the colours now etc. Do you ever have issues with jerky fader movements in automation? Sometimes if I shift the faders 1 to the left or right they become less jerks. Just in reading automation. Thanks again. Ed

1 Like
212

Hello mister bjoluc. Congratulation for the accomplished work, and sharing it. If everybody was as generous, the world maybe better !
Anyway, i was lost with the mackie script, and your script works perfectly with my cubase 13 Elements.
Nice :yum:

1 Like
213

Thank you very much.
I deleted the Console1Fader file in the folder called User Settings and re-installed the driver and it worked.

214

Hello, I am thinking of adding an X-Touch 1 to my setup and was wondering if this script will work with it. I was reading through and it seemed someone was working on a version for it but I didnt see that it was completed. Thanks!

Edit: I see @Darren.Jones has been working on this, would i be possible to share a walk-through guide on how to get this working in CB 12 for the XT1? Thanks!

215

Yeah, it’s on my “list of things to do for my Youtube channel”… I will endeavour to get it done this week!

216

I think Behringer ought to send you a nice check. Without your exceptional work, the X-touch would be useless for most of us, but you have made it a really valuable tool.

1 Like
217

@EddieJames They are not always as smooth as I’d like them to be, yes. Would you mind sharing a little video clip showing what kind of jerkiness you mean? I already looked into ways of interpolating fader movements, but it’s hard to do without reliable timer functions available. I might try again with the new API features in Cubase 13.

218

I’ll do a vid tomorrow and upload. Strange that it goes away if I shift all Channels to the left or right. Thanks

1 Like
219

Heres


the vid i did of the dodgy faders under automation. Note when i shift all to L or R, the action becomes smooth…
Hope this helps. Thanks mate

220

Also
Note how the fader to the right now works with the dodgy fader when I shift them. Although the fader is an empty track. Then when I switch back the erratic behaviour is still present.

221

This is a great help, thanks @EddieJames! So what you are facing is not an issue with the script itself luckily (otherwise the fader on the unassigned channel would be sent down and stop moving when you switch channels). Instead, something else seems to be sending MIDI to the X-Touch at the same time – looks like a traditional MCU device or maybe another script instance? I hope you’ll find the culprit!

222

Ah ok. Got you. I still have all 4 set up in mackie control. Should I get rid of that as now set up in midi remote. Thanks for looking in to this.

1 Like
223

I deleted all 4 mackie control instances. Now working spot on. Thanks for that. Amazing. You are a star.

1 Like