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

Cubase
,
286

Oh, thanks for pointing this out!

287

@matthieu_guihot I’ve released v1.10.1 fixing Shift + Channel Left/Right navigation of plugin parameter pages :v:

1 Like
288

Oh yes!!
You’re the king. Thank you very much!

1 Like
289

Well, I feel a lot more royal now :crown: Thanks :smiley:

1 Like
290

Here very good ideas fro implementation https://youtu.be/D9KQu1ijrrs?si=II1buL0oZabc7Cdi

292

Evening thought…
With the “SEND” section I would like to be able to use it easily and without been dependant of my computer screen. This means I need to have the effect name displayed on the Xtouch.
Actualy we can see “Niveau” or “PrePost” (I’m French…) on the small screens but I’m not able to know which effect is selected.
So, in use, I would like to have also the name of the corresponding effect affected (for example below, on the second line)
In addition, the must would be to switch automaticaly in “FLIP” mode as soon as I press “SEND”.

293

Really helpful with my channel strip plugins with many parameters. Thanks again!

1 Like
294

Talking about Shift functions. I tried to set up additional Shift mappings (SHIFT-LEFT), but I didn’t manage. Dear @bjoluc - is it possible to edit the SHIFT subpage in Cubase or can this only be scripted?

If it only can be scripted, I’d post a feature request via GitHub for more details.

1 Like
295

" * The function buttons F1-F8 can only have one assignment per button, no matter whether “Shift” is held or not (“Shift” activates a sub page and the Mapping Assistant doesn’t consider sub pages)"
https://github.com/bjoluc/cubase-mcu-midiremote

296

If you referred to my suggestion: I was not talking abour the function buttons, but a possible assignment for the “cursor keys” on the X-Touch - either in the Mapping Assistant (but you say this won’t be possible) or in the code.

Please see Additional Shift Functions for Viewport Zooms ¡ Issue #43 ¡ bjoluc/cubase-mcu-midiremote ¡ GitHub for more details.

297

Thanks @matthieu_guihot, I fully agree. This has been on my list for a while and I’m hoping to get to it soon.

2 Likes
298

Hi Bjoluc. Been using this script for a few months now and it’s working great. I have a request, but I don’t know if it’s difficult or impossible. In normal use, would it be possible to use both the upper and lower display lines for track names as an option? So instead of “pan” taking up room on the upper line, you could fit in “backing vocals” without concatenation. I’m guessing the Mackie protocol makes this problematic, but it would really enhance the system.

299

Hi there,

First of all, I want to thank you for your great work.

May I ask you why you didn’t use the key mapping like the description on the keys of the X-Touch? Or have I done something wrong?

And my second question is, is there a key for activating the click?

Greetings,

Oliver

300

Hi,
Amazing work on this for Cubase. I don’t suppose you have worked on an xml mapping file that can be imported into WaveLab for the X-Touch?

Or does anyone have one?

Sorry, complete novice with WaveLab.

Thanks,

301

Does this work with Studio One?

302

Hi and welcome to the forum,

No, this great feature is Cubase only. :+1:

303

Hello Bjoluc,
Is there now finally the possibility in Cubase 14 to recreate the hidden channels in Cubase on the X-touch in the MIDI remote??
That would be great
and thank you again for your excellent work on this script

greetings chris

304

Cubase 14 has the new Drum Track that’s has to be enabled too…

:scream:

Thanks in advance Bjoluc

:stuck_out_tongue_winking_eye:

Just another question, if I will install new releases of your Midi Remote in Cubase, I will lost all the mods I set on the Xtouch button? I customise some of them…

Cheers again, Eriberto

305

Looking at the documentation, it does not appear there has been any updates to Midi Remote in Cubase 14, so we are still waiting for them to implement the follow visibility feature. In fact, the github documentation for Midi Remote has not even been updated to reflect the new key commands added in 14. It seems like Midi Remote has been forgotten about already…

306

It’s a shame, I hoped for nothing again!
More and more new half-finished things are being put in place and the old half-finished things are not finished → Who benefits from something like that??
If this continues, we’ll soon only have a HALF-finished entire Cubase :face_exhaling: