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

[bjoluc]

@matthieu_guihot

Here what I see : When I start Cubase (v13.0.30 pro) the “PAN” key is lit for the encoders functions. If I push one other button (“TRACK”, “EQ”, “SEND”, “PLUGIN” or “INST”) nothing change. But if I press one of them and after I press “SHIFT” or one one of the “FADER BANK” or one of the “CHANNEL” the screens display the corresponding info and I’m able to use the encoders correctly…
Is there something normal or anormal and what should I do?

@Robohub

I’m quite new to Cubase so I’m running the latest version 13.0.30 on a MacBook Air M2.
Like @matthieu_guihot above I have the same problem. When pressing for instance the Flip button, it doesn’t activate immediately - only after pressing e.g. Shift, the Flip command executes. Same behaviour for the Encoder Assign buttons. Also, there Assignment display is always black.

This is not how it should be @matthieu_guihot @Robohub Is this new with Cubase 13.0.30 or was it also in 13.0.21 – and does/did it work with Cubase 12 on your systems? I tried 13.0.30 on macOS Ventura a couple of days ago, but couldn’t reproduce what you describe

@matthieu_guihot

I don’t understand how to use the “SEND” touch with your new function. Can you explain me how its works?

@matthieu_guihot Have you already read the following part of the Readme?

the “Sends” button […] turns the rightmost push encoder and the jog wheel into controllers for the value that’s currently under the mouse cursor – like the Steinberg CC121’s AI knob.

[bjoluc]

@matthieu_guihot

Something is going wrong with the Plugins : I would like to limit the acquisition of this parameters to 4 pages only. I’m sure it will solve the issue.

@matthieu_guihot You mean the Plugin encoder assign button banking behavior? It is mapped to the InsertPluginViewer’s next parameter bank action once you’re in the Plugin encoder assignment. No looping involved. But I don’t understand how this would relate to the other issues?

[doctorlaz]

@bjoluc: I know that it’s possible to have the scribble script text black on white, or white on black, using SysEx methods. I think you just add 40 to the channel number. I’d like to try this out, but I can’t find anywhere in the script to alter. Is it possible? If not, could you consider this a request for a future update? I think in certain lighting conditions it would be easier to read

[bjoluc]

AFAIK, this does not work in MCU mode (only XCtrl or so if I remember correctly). But if you manage to find a SysEx message that does this in MCU mode, I’m happy to add it as an option!

[doctorlaz]

@bjoluc

AFAIK, this does not work in MCU mode (only XCtrl or so if I remember correctly).

You do remember correctly! As a quick hack, in SetChannelColor, I tried changing colorVariable.set(context, color); to colorVariable.set(context, color+0x40); and no change. While I was there I also tried +8, +0x10 etc, but still no difference. Maybe in v1.23…

[Robohub]

My input to the (my) issue:
(X-Touch (+Extender) MIDI Remote Script (MCU mode) - #260 by Robohub)

Running Monterey 12.5 on MacBook Air M2. X-touch 1.22.

1. Cubase Artist, 12.0.70 (Rosetta 2, don’t know why): X-touch works perfectly:)
2. Cubase Artist, 13.0.30 (Apple Silicon). X-touch works as described above, not as expected:(

Can’t remember if it worked on previous Cubase 13 versions. @bjoluc

[fischnek]

Hi,

since yesterday i noticed that the encoder assign buttons (pan, EQ, send etc.) only work when i press them together with SHIFT. Also, the display doesn’t have the numbering of the sub-page I’m on in say EQ.
This situation persists even after I reloaded the script.
I wonder what is the reason for this?

…sorry, I see now that this problem has been reported before. Well, I have this in Cubase12, not 13.
Has anyone managed to find a solution in the meantime?

Update:
I experimented and found the following about the “encoder buttons” problem:

1. Basically the problem is project dependent. The encoder buttons work fine when opening a new project or an existing project.
2. However, when opening certain projects, the operation stops. And when this happens, projects that were already working don’t work anymore.
3. If I restart Cubase (the controller doesn’t need to be restarted), operation is restored as long as I don’t open any project that breaks operation.
4. I have tested the project causing the error. I deleted all the tracks in sequence, first the instrument, then midi, audio, etc. In the end the project was completely empty, I even deleted the pool: but the error persists for that project.
5. I noticed: for good projects, when I press the encoder buttons, the “last touhed control” parameter (shown on the midi remote page) shows at the moment of pressing what action is being done (for example: Activate Subpage “EQ 1”, but when the button is released, it automatically and immediately returns to “Record (Transport)”. For those projects where there is a problem, when the EQ is pressed, the button lights up but no change is made, and for “Last touched control” the value "Activate Subpage “EQ 1” remains, it does not automatically return to “Record (Transport)”. If I press the record button, the recording starts AND switches to EQ mode. After pressing any encoder, if I press the record button, it will switch to the desired mode.
   That’s it so far. It would be nice if this would help solve it.

[matthieu_guihot]

Thanks you for the good description and analysis @fischnek. I have exactly the same issue with Cubase 13.

Maybe it’s possible to save and send a very simple projet with the issue to help to locate the issue root cause? (as @bjoluc wasn’t able to reproduce it at the moment)
I can try to provide it if someone is interrested.

[matthieu_guihot]

[quote=“bjoluc, post:265, topic:831493”]
This is not how it should be @matthieu_guihot @Robohub Is this new with Cubase 13.0.30 or was it also in 13.0.21 – and does/did it work with Cubase 12 on your systems? I tried 13.0.30 on macOS Ventura a couple of days ago, but couldn’t reproduce what you describe
[/quote]thanks a lot for your help.
I hope we will find what happens.

[bjoluc]

Thanks @fischnek for your investigation – also for opening the issue on GitHub! This is very useful information.

@matthieu_guihot

Maybe it’s possible to save and send a very simple projet with the issue

Yes, please! I would’ve asked for this next, so you saved me a bit of typing

[SignalsMusic]

Excellent script, thank you for your work @bjoluc! I have been making some modifications to my preference and doing pretty well considering I have a very basic understanding of scripting. The one thing I am struggling with is I would like to restore the original MCU style of paging back and forth through subpages using the channel left and right buttons. I can’t seem to understand what the correct action binding to assign to these buttons would be to accomplish this.

[matthieu_guihot]

Test_issue_script_Xtouch.zip (196,6 Ko)
Here is an empty project with the issue.
On my computer I was able reproduce the bug each time I load the project even if I restart all (computer, Xtouch and extender).

I’ve included :
A screenshot to show the Cubase version used.
The .js file used with my settings.
The .json with my personnal assignements.

PS : I’m under Windows 10 version 22H2.

[bjoluc]

@Crincy @doctorlaz @matthieu_guihot @Robohub @fischnek I experimented a bit with the demo projects you provided (thanks!) and it appears that disabling and re-enabling a script solves the issue for any project it occurs in!

Can you confirm this works for you too?

[bjoluc]

@SignalsMusic

The one thing I am struggling with is I would like to restore the original MCU style of paging back and forth through subpages using the channel left and right buttons. I can’t seem to understand what the correct action binding to assign to these buttons would be to accomplish this.

@SignalsMusic Right, that’s not at all trivial to do. I refactored a lot of the encoder assignment logic recently which should allow me to add a config option for your use case in a future version

[matthieu_guihot]

Yes your solution works on my side @bjoluc !
Thanks a lot!!!
If we don’t know at the moment why it happens if we are able to make it work again it’s not longer a blocking point.

[matthieu_guihot]

At the moment I just two suggestions :

• I wich I could change the “mapping” of my faders easily : there is a configuration in the script the set which tracks are enable (Inputs/Audio/Inst/etc.) but we are not able to modify this during a mix. When I use the dedicated buttons on the Xtouch it just show/hide the traks on the Cubase mixconsole but it doesn’t change the corresponding mapping of the Xtouch fader. It’s a shame, I use this a lot whith the standard MCU protocole.

• The plugin parameters manager looks a little bit strange. I wich I could have a solution to go back to the previous page if necessary instead of having to go through all the banks to return to the first ones.
  In addition I don’t know why but after scrolling through all the banks there is a shift (the first parameter is not affected the first pot but on the second or third ones).

That’s not blocking points but with this improvements the scripts will answers all my current dreams

[Crincy]

Hello bjoluc ,hello everyone,
Yes… that works for me again with the zoom → then the projekt save once
Ok ->> as a workaround at first

Thanks for trying it out.

[bjoluc]

Hi all,
I released v1.10.0 a couple of days ago with lots of subtle performance improvements and some additional button mappings. The release also adds port auto detection for those of you using multiple extenders (via MIDI over ethernet) if you name the extender MIDI ports “X-Touch-Ext”, “X-Touch-Ext2”, “X-Touch-Ext3”, … from left to right. Finally, there’s also an official X-Touch One version of the script now.
Cheers!

[matthieu_guihot]

Thanks for this new version! I can’t wait to test it.

[matthieu_guihot]

I don’t understand what means this : “Allow switching encoder assignment pages via Shift + Channel Left/Right”

Edited : ok I’ve understood but its a shame that it’s not operational for plugins.