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

[Norbury_Brook]

the drum track doesn’t show on any harware controller not even Eucon unless you add separate outputs then you get the tracks.

Try assigning some spearate outs and you’ll see them appear on your controller.

M

[m.c]

@edemunari

do I miss something?

I’ve just checked the script of @bjoluc, I see in the mapping→index.ts file the list of the types of tracks the bankZone is handling. This list is inherited from the file util→config.ts. Now since the drum track is a new type of track, and I don’t see it included in the types of the midi remote API, it’s logical that you don’t see it on your displays. My suggestion for a workaround to our friend bjoluc, until this is fixed by Steinberg (but I cannot possibly know when), is to use instead of the included track types list, a list to exclude track types. For example, I see in the code mentioned that he actually includes all track types, except for the usual suspects input/output tracks. So, this part of the code could actually exclude just the input/output tracks. This way, all other track types, either ones already included in the API or ones that may be added in the future, will be available.

[m.c]

@Norbury_Brook

the drum track doesn’t show on any harware controller

Hi, as shown in my screenshot, it does show on my controllers, by using midi remote.

And here’s a photo of my Novation SL MK3, again with a drum track included, by using a midi remote script:

[edemunari]

@m.c

Hi, as shown in my screenshot, it does show on my controllers, by using midi remote.

And here’s a photo of my Novation SL MK3, again with a drum track included, by using a midi remote script:

I seems that NI Kontrol MK3 works fine with drumtracks without any mod… something similar should be done also here?

Thanks a lot, Cheers, Eriberto

[Norbury_Brook]

ah, Ok that’s a first then as there’s been a few threads about this already.

Eucon doesn’t show it and niether does Behringer unless you do as i say by adding outputs.

M

[bjoluc]

Happy new year everyone (if you celebrate it on Jan 1)! I’m not finding much time to work on this at the moment, but I had a number of features laying around waiting to be released and an iCON V1-M/V1-X version of the script, so here is a new release: v1.11.0

And a quote of the release notes:

Features

• Add a config option to disable jog wheel zoom in zoom mode
• Add a config option to flip scribble strip display rows by default
• Add a config option to map the channel left/right buttons to encoder parameter page navigation by default
• Add an iCON V1-M script variant
• Add Cue Send 1-4 encoder assignments
• Allow toggling the input phase by pushing encoders in the “Input Phase” encoder assignment
• Display “PreFadr” instead of “PrePost” in Sends encoder assignment
• Display changes to secondary encoder parameters (e.g. EQ band on/off, Send slot on/off) made by pushing encoders
• Make EQ gain encoder pushes invert EQ gain without holding Shift and reset it when Shift is held
• Make mapping the main fader to the control room level an opt-in option to reduce differences to the default Cubase MCU integration
• Make pushing a plugin / quick control / channel strip encoder toggle its value if it is at its minimum or maximum
• Make the “Sends” encoder assignment show send effect names on the scribble strip displays

Bug Fixes

• Avoid displaying encoder parameter value changes upon switching encoder parameters
• Fix encoder display mode for the “Sends” assignment
• Show Cubase 14 drum tracks

Cheers!

[edemunari]

Thanks a lot and Happy New Year!!

But for drum track showing need to modify the setting in:

• The flags below control which channel types will be visible (i.e. mapped) on your device(s).
  • For each channel type,
  • • true means the corresponding channel type will be visible on your device(s).
  • • false means the corresponding channel type will be hidden on your device(s).
  • By default, all channels except input and output channels are visible, like in the
  • Cubase-builtin Mackie Control mapping. Feel free to change the flags below to your liking.
    */
    channelVisibility: {
    audio: true,
    instrument: true,
    sampler: true,
    midi: true,
    fx: true,
    group: true,
    vca: true,
    input: false,
    output: false,
    },
    At the present no drum track are shown on my Cubase 14 .
    Cheers, Eriberto

[matthieu_guihot]

Thanks a lot for this new release!!!
On my side I applaud for this 3 updates :

• The display for the Sends
• The push for encoders
• The revert gain for Eq

[matthieu_guihot]

An option is missing to flip to fader automaticaly with Sends

[Danix78]

Thank you @bjoluc
Always better… but:

The zoom button does not switch to zoom mode and does not light up blue!

I do not know what caused the malfunction. Everything works fine with a project created months ago, but not from today. I have not tried to create a new project, tomorrow I will try.

I have not been able to restore the correct functioning of the zoom button. But trying to click different keys, such as Motor, Shift, Read and SMPTE / BEATS I was able to switch from transport to zoom but the blue LED did not light up. I do not know in which order or which combination of keys unlocked the zoom function. Same “random” procedure to switch from zoom to transport.

What I have described may be helpful for a more in-depth investigation into the issue.
Latest version of the Script.

[blissdrums]

@bjoluc

Thank you as always for all of your hard work on this… just a quick question. The visibility groups work on my Xtouch now, which is fantastic. It’s a small quibble, but once I choose a visibility group in Cubase, I then have to select a track for it to refresh on the XTouch. This is obviously not a big deal (one extra click), but I was just curious if it would be easy-ish to add some sort of refresh command to your midi remote script so this happens automagically…

Thanks for all you do!

[doctorlaz]

@Danix78

The zoom button does not switch to zoom mode and does not light up blue!

A few of us have had a similar issue. Some glitch happens in Cubase, and you can’t zoom any more. What’s worse is that this glitch is saved in the project file, and you will never be able to zoom again with that project. Worse still, unless you shut down Cubase completely beforehand, the glitch will transfer itself to a previously working project when you save it!

Sometimes, just disabling the script then enabling it again is enough to solve the issue.

Alternatively, you may have a backup project saved before the glitch occurred. Just move it to the main project folder (in C14), then open it.

If that doesn’t work, I have the following solution:

1. Shut down Cubase completely, re-open it and create a new empty project. Confirm that the zoom button works.
2. Go to the File menu, and Import Tracks from Other Project. Choose the latest version you’ve been working on.
3. Import every track from that project. All the buttons on your X-Touch will work again. Save the new project and you’re good to go.

This workaround has never failed for me. If you couldn’t get zoom to work in step 1, then you likely have a different issue.

Laz

[cparmerlee]

I have had cases where, after opening an older project, SOME of the script functioality (such as scribble strips and transport controls) works, but other features (like pan knobs and faders) do not work. It seems rather random, but I guess in most cases, the full function came back after I:

• closed Cubase,
• created a new empty project,
• closed Cubase,
• then re-opened my old project.

[Danix78]

Thanks @doctorlaz I figured there was an alternative way to work around this, just like this, although it slows down the workflow.

Thanks @cparmerlee, this alternative seems faster, I’ll try it, unfortunately the problem still remains.

I hope @bjoluc can analyze a corrupt file against a previous working version, it would be ideal to find the problem and clear the bug.

Anyway, Thanks for the help.

[butterfly]

I hope @bjoluc can analyze a corrupt file against a previous working version, it would be ideal to find the problem and clear the bug.

This is a known MIDI remote problem of Cubase 14.
It also occurred with the PreSonus FaderPort script…

PreSonus FaderPort 2 (2018) midi remote script

After opening and closing and starting a whole lot of projects, the conclusion is that the connection problems has almost gone away on my system. I had to refresh the remote control device twice by hitting the reload scripts button under scripting tools in the lower zone. You might have to hit the cogwheel to make that menu visible in the midi remote tab in the lower zone. There is also a keyboard shortcut for reloading the scripts, but unfortunately that doesn’t work for me unless the Midi Rem…

PreSonus FaderPort 2 (2018) midi remote script

Don’t think this is any help but… Cubase project which Faderport likes in Cubase 13 but not in 14. I attempted and failed to import the tracks from the 13 project into a 14 template. All arrived corrupt. Opened the project in 13 (all good with FP) now ran backup project. Opened backup version (all good with FP) closed 13 opened 14 FP now likes the project in the backup 13 version. Saved that (so becoming a 14 version) and all is well with FP. What have I learned ? Not sure !!!

[Danix78]

Well, I didn’t know.
@bjoluc you’re safe.
We’ll wait for @steinberg.

[SuperG]

Must have been a tough decision to include a Javascript engine within Cubase, knowing you’d bring a whole new class/domain of problems to the table. I believe it was the right decision for the long term. We need that flexibility.

But, buckle-up ‘buttercup’, it’ll take some time to work the kinks out.

[Antonio_Escobar]

Hi everyone,

I’ve encountered a frustrating issue in Nuendo 13 when using this script with my system. I have three X-Touch units connected via the network protocol, but every time I restart Nuendo, it forgets the entire setup. I have to reconfigure everything from scratch after each restart.

It seems like others have had similar problems with Cubase, as I’ve seen mentioned in this thread:

• User mat (January 23, 2024): Reported that Cubase forgets the X-Touch configuration upon restarting or opening a new/empty project. However, it remembers the setup if the controller was configured in an existing project.
• User edemunari (November 15, 2024): Mentioned that on macOS, the script needs to be reinstalled and MIDI channels reassigned every time the system is restarted, as Cubase does not retain the configuration.

It seems this issue might be related to how the software handles MIDI Remote configurations. Has anyone found a solution or workaround for this problem, specifically in Nuendo? I’d appreciate any advice or updates from the community!

Thanks in advance!

Antonio

[doctorlaz]

It might help if you give some details about your system. I’ve never encountered this problem using Cubase on a PC.

[Antonio_Escobar]

MacOS Ventura, Nuendo 13.
3x Behringer X-Touch connected using the Network system.

Best,
Antonio.