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

Cubase
,
184

Thank you so much, cant wait for it:)

1 Like
185

Hi bjoluc,
great work! Excellent!
Thanks!

1 Like
186

I’m about to release 1.9.0 and I’d like to ask for your opinion on this simple matter: In old Cubase versions, pushing an encoder in the PAN assignment used to reset the panner to “center” instead of toggling “Monitor Active”. I’m adding a resetPanOnEncoderPush config option to support this again:

  • true means pushing an encoder in PAN mode will reset the panner to center
  • false means pushing an encoder in PAN mode will toggle the channel’s monitor mode

Now the question: What do you think should be the default value for this option? I’m tempted to make it true, but this might just fit my personal workflow and I’d like to make sure the default is a great one for most of you :v:

  • The default should be true
  • The default should be false
0 voters
187

Mind a suggestion?
Why not having both, by assigning one of these two to a double-push?

188

Sounds reasonable (despite double-pushing encoders on the X-Touch is a pain :laughing:; I can’t speak about other devices), but I don’t have any double-push logic in my script yet and I’d like to make sure all assignments can be overridden via the GUI. Feel free to PM me about this if you’d like to discuss it, so we don’t annoy the others :sweat_smile:

189

@bjoluc

Thankyou so much for all your hard work in making this script for the X-Touch and Cubase. I’ve just bought an X-Touch and am totally new to using a DAW controller.
I’m considering buying one of these magnetic Cubase overlays for the X-Touch and I’m wondering if this would match how the controls are laid out with your script?

1 Like
190

I bought a couple of those magnetic overlays last September and the layout is the same as the Behringer overlay for Cubase that comes in the box with the XT1. The main difference is that they are made of a vinyl. The glossy versions look really good and they are also beer-proof! I love it!

The owner of Birchwood, Damon is a really nice, helpful guy. He may be able to design a custom overlay, certainly couldn’t hurt to ask.

Cheers,
Steve. :smile:

1 Like
191

Thanks for this Steve!

192

Just wondering, with bjoluc’s script do the transport buttons permanently light up?
If not, is it possible to make this happen within the script?

193

Stop, Play and Record light permanently, and FF / REW when pressed.

194

That’s good to know. Just wondering if if it’s possible for the FF/REW buttons to be permanently lit in an update of the script?

195

@bjoluc

I recently picked up an xtouch and an extender, and the way things turned out I also ended up with a second extender. When I modify the script as “extender, main, extender”, I see all three units in the midi remote editor, but when I try to setup the three sets of midi I/O, I am only getting the following choices… x-touch, x-touch-ext, and MIDIIN2 (x-touch). If I look at the midi ports in Cubase’s Midi Port Setup window, I can see “X-Touch” and then “X-Touch-Ext” and another “X-Touch-Ext”.
Is this the port patching issue that you are referring to above? Is this why I am only able to add one X-touch and one extender instead of both extenders? I just want to make sure I understand if that’s my issue… thanks!

1 Like
196

is there a way to use more than one extender? i have 3

197

I really appreciate all the work that has gone into making the X-Touch most useful in Cubase. I had your script installed and working well at C12. I do have some issues at C13, as have been discussed by others above. So I want to update to the most current script.
I am a little confused about where that is. I used the one at Release v1.8.0 ¡ bjoluc/cubase-mcu-midiremote ¡ GitHub

That seemed to resolve the issue with the buttons on the Xtouch not lighting when changed from Cubase. But the pan adjustment is still off, requiring several complete rotations to pan all the way right or left. Is that a known problem?

1 Like
198

Hi all,

I released v1.9.0 yesterday, so here’s a message straight to your inbox!
Most importantly, the new version finally gets automatic port detection right for single and dual-device setups (sorry for the wait!) :tada: Moreover, you can hold shift and push encoders now to reset their values to their defaults (if a static default value is known). There’s one exception: Shift-pushing an EQ gain encoder inverts the EQ gain instead of resetting it to 0 – so we can all sweep around easily (suggested by @isdjan on GitHub). Finally, by default (like you voted above) pressing pan encoders resets channel panners now, unless you set resetPanOnEncoderPush to false in the config options. In that case, you can still reset them by shift-pushing encoders.

On a different note, the encoder sensitivity issue has been fixed in Cubase 13.0.20 – only the “I can’t reliably enable “On”/“Off” values (like Monitor) by turning encoders” issue remains with Cubase 13.

Cheers!

2 Likes
199

Hm, ok :exploding_head: It’s supposed to be like this:
transport-button-lights-lowres
That’s the way Cubase handles it and it matches the on-screen transport control buttons – I didn’t design this. No idea why it would be different for you :thinking:

200

Hey @blissdrums! I was only ever able to set up additional extenders via ethernet (rtpMIDI on Windows) due to this. That way, you can choose the port names to avoid having identical port names across multiple devices.

201

Absolutely! Just add them to the devices config option at the top of the script file – like this (depending on where you placed the extenders):

  devices: ["extender", "extender", "main", "extender"],

You’ll also have to manually select the ports (via the big “+” button in the MIDI remote pane) because the script only auto-detects up to two devices.

202

Sorry @cparmerlee – I talked about releasing a new version a while ago that I didn’t manage to release until yesterday. You were right about the latest script version at that time, it’s always in the releases section on GitHub. The encoder sensitivity issue was fixed in Cubase 13.0.20 :+1:

203

Hi,

Thanks for this. Is was more wondering if it was possible for all 5 buttons to be permanently lit at the same time?

I often work in quite a dark mixing room and it would be brilliant to have all the buttons lit at the same time to avoid pressing the wrong one by accident! I think this is possible with the Presonus Faderport and it would be brilliant if this was possible in an edit to the script?

Thankyou for v1.9!

1 Like