bjoluc / cubase-mcu-midiremote Goto Github PK

View Code? Open in Web Editor NEW

31.0 6.0 7.0 2.2 MB

Cubase MIDI Remote Scripts for DAW Controllers using the MCU Protocol

License: MIT License

TypeScript 99.75% JavaScript 0.25%

cubase midi-controller midi-remote-script x-touch x-touch-extender qcon-ex-g2 qcon-pro-g2 mackie-control mcu

cubase-mcu-midiremote's Introduction

cubase-mcu-midiremote

Cubase 12 MIDI Remote Scripts for DAW Controllers using the MCU Protocol

The following devices are explicitly supported:

Behringer X-Touch / X-Touch Extender
iCON QCon Pro G2 / QCon EX G2
Mackie Control Universal (Pro) / XT (Pro)

Other MCU-compatible devices may work with any of these scripts, but their device surface is not explicitly displayed in Cubase. Feel free to open a discussion on GitHub if you would like your MCU-like device to be supported.

TL;DR

The Cubase MIDI Remote Scripts developed in this repository replace the default Mackie Control device setup for various MCU-like devices. They can be set up with single standalone controllers or with an arbitrary combination of standalone and extender units. The mapping is reasonably close to the default MCU mapping, with a few (workflow-)improving changes. Nevertheless, you can easily re-map most control elements using Cubase's MIDI Remote Mapping Assistant.

Motivation

Since version 12, Cubase supports the customized integration of MIDI controllers via a new MIDI Remote JavaScript API. Several vendors are producing DAW controllers similar to the Mackie Control Universal (MCU) which are traditionally set up as Mackie Control devices in Cubase. Creating MIDI Remote API scripts for these controllers allows to improve the mapping where applicable and offers users the possibility to override parts of it themselves via Cubase's MIDI Remote Mapping Assistant.

Some points for improvement of the default MCU mapping are:

The main fader controls the first output channel's volume, not the Control Room volume.
The meters do not seem to fully match the scale of the MixConsole meters.
Bringing up the parameters of the currently focused plugin requires navigating through the list of insert slots with a push encoder.
There is no single knob that can control any parameter under the mouse cursor, like in Steinberg's CC121 controller.

Moreover, some controllers have features that are not available with the default Mackie Control setup in Cubase. For instance, the Behringer X-Touch has an individual, generously padded, RGB backlit scribble strip display per channel, as well as integrated LEDs in most buttons. A MIDI Remote API script can illuminate these scribble strips according to their tracks' colors, avoid unnecessary display padding characters, and light up buttons while they are being pressed.

About this Script

The MIDI Remote Scripts developed in this repository serve as full replacements for the default Mackie Control setup. The mapping is similar to Cubase's default Mackie MCU Pro mapping, with the following exceptions:

Note In the rest of this document, all buttons except the six encoder assign buttons are referred to by their Cubase MCU mapping labels. I recommend using a Cubase overlay for your device, unless your device already has the Cubase labels printed on it, like the iCON QCon Pro G2. Alternatively, page 7 of Cubase's remote control devices documentation provides a Mackie MCU Pro overlay which you can use to figure out the Cubase button labels for your device.

Encoder Assignments

The lower scribble strip row always shows track names since they are vital to using each channel's buttons and fader, regardless of the encoder assignment. Parameter page numbers are displayed on the otherwise unused two-digit Assignment display instead. If an encoder assignment only has one parameter page, the Assignment display remains blank.
Shift-pushing an encoder resets its parameter to the default value, if a static default value is known. An exception are EQ gains which are not reset but inverted when shift-pressing their encoder.
The "Track" encoder assignment has additional parameter pages for Low Cut, High Cut, and the Track Quick Controls of the selected track.
By default, pushing encoders in the "Pan/Surround" encoder assignment resets a channel's panner instead of toggling its "Monitor Active" state. If you'd like to toggle "Monitor Active" instead, you can set the resetPanOnEncoderPush config option to false.
Instead of spreading the "Send" encoder assignment options out on four parameter pages, there are only two pages now. The "Level" and "On" pages have been combined into a single page where turning encoders modifies the send level and pushing encoders toggles a send slot's On/Off status. The "Pre/Post" page remains untouched, and the "Bus" page is omitted because the MIDI Remote API doesn't expose send busses.
The "Plug-In" encoder assignment always follows the currently focused plugin window to avoid tedious plugin selection via push encoders.
The first page of the "Inst" encoder assignment maps encoders to the VST Quick Controls of the currently selected instrument track. The remaining pages map 8 encoders to each part of the channel strip, i.e., gate, compressor, tools, saturation, and limiter. Pushing an encoder toggles the bypass status of the corresponding channel strip plugin.

The table below summarizes all available encoder assignments:

MCU button label	Cubase button label	Available parameter pages
Track	First	Monitor Pre Gain Phase Low-Cut Frequency / Enabled High-Cut Frequency / Enabled Selected Track Quick Controls
Pan/Surround	Pan	Pan
EQ	EQ	EQ Bands 1 & 2 (8 encoders) EQ Bands 3 & 4 (8 encoders)
Send	Last	Send Levels / Enabled (8 encoders) Send Pre/Post (8 encoders)
Plug-In	Plug-Ins	All Remote Control Editor parameter pages of the currently focused plugin (all encoders)
Instrument	Dyn/FX/Aux	Remote Control Editor parameters of the selected track's VST instrument (all encoders) Channel Strip Gate (8 encoders) Channel Strip Compressor (8 encoders) Channel Strip Tools (8 encoders) Channel Strip Saturation (8 encoders) Channel Strip Limiter (8 encoders)

Buttons

Like in the MCU default mapping, the 8 channel type buttons apply MixConsole channel visibility presets 1-8. In the likely case that you don't want to waste 8 prominent buttons for loading visibility presets, feel free to re-assign some buttons in the MIDI Remote Mapping Assistant.
The Channel Left/Right buttons below the Fader Bank buttons do not navigate between encoder parameter pages, but move the fader bank left/right by one channel. Navigating parameter banks can be achieved by pressing the respective Encoder Assign button multiple times to cycle through the available parameter pages in a round-robin fashion.
Pressing "Shift + Bank Left" navigates to the first (=leftmost) mixer bank.
Pressing "Shift + Edit" closes all plugin windows instead of only the currently active window (I couldn't find a command to "close the currently active window").
The "Instrument" and "Master" buttons are assigned to the handy MixConsole History Undo and Redo commands, respectively. In the default MCU mapping, they would activate instrument and main insert effects encoder assignments. However, these can already be reached via the "Inst" and "Plug-In" encoder assign buttons, so I decided to use the buttons differently.
For the same reason, the "Sends" button doesn't activate a send effects encoder assignment. Instead, it 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.
Pressing "Shift + Display Name/Value" flips the scribble strip display rows

Miscellaneous

The main fader controls the Control Room volume unless the mapMainFaderToControlRoom config option is set to false.
In zoom mode, the jog wheel zooms in and out instead of moving the locator

Setup

Make sure the firmware of your device(s) is up to date (iCON QCon Pro G2 >= 1.13, Behringer X-Touch >= v1.22 or scribble strip colors will not work)
If your devices have multiple operation modes, select Mackie Control mode (here's how to do it on the X-Touch).
Open up Cubase and ensure you are running version 12.0.52 or later
In the studio setup window, remove any Mackie Control remote devices (don't forget to take screenshots of your command assignments). If you don't feel comfortable removing the devices, it is also fine to select "Not Connected" for their ports.
Open the latest GitHub release page and in the "Assets" section, download the script (.js) that is named like your device.
Open C:\Users\<Username>\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local (Windows) or /Users/<Username>/Documents/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local (MacOS).
The filename of the script you downloaded has the form <Device>_<Vendor>.js. Cubase expects scripts to be nested in subdirectories named precisely after the script's vendor and device. So within the Local folder, create the subdirectories <Device>/<Vendor> according to the device and vendor portions of the script's filename. For instance, if you downloaded behringer_xtouch.js, the subdirectories would need to be behringer\xtouch.

Note Directory names matter. Make sure your subdirectory names precisely match the device and vendor components of the script filename, or Cubase might not recognize the script.
Finally, move the script file into the newly created subdirectory and restart Cubase to pick up the script.

Cubase should automatically detect your device and enable it as a MIDI Remote. If it doesn't, you can manually configure the MIDI Remote by clicking the "+" button in the lower zone's MIDI Remote pane.

Setup with multiple devices

To use a combination of standalone and extender devices, follow the same steps as above, but edit the script file before restarting Cubase: For instance, to use a main unit and an extender unit, open the script file with a text editor and in the configuration options at the top of the file, replace devices: ["main"] with devices: ["extender", "main"] (or devices: ["main", "extender"] if you have your extender on the right side of the main device).

Then restart Cubase. If you are using a standalone device (main or extender) or one main device and one extender, Cubase should automatically detect your devices' MIDI ports. Otherwise, manually configure the MIDI Remote by clicking the "+" button in the lower zone's MIDI Remote pane.

Note Cubase does not expect scripts to change their port definitions over time – which is what happens when you edit the devices config option. If you load a project in which you were previously using the script with a different devices configuration, Cubase might not properly detect your devices' MIDI ports and your devices might stay unresponsive. In that case, try disabling and re-enabling the controller script in the MIDI Remote Manager to make Cubase forget the previous port configuration.

Configuration Options

The very top of the MIDI Remote script file declares a number of configuration options. You can edit these options to match your preferences. Each option is documented in a comment above it. For an overview of all options, please refer to the source code on GitHub.

Drawbacks

Current limitations of the MIDI Remote API:

The "Track" encoder assignment is missing the "Input Bus" and "Output Bus" pages which are not exposed by the MIDI Remote API. I prefer to use the mouse for routing anyway, as opposed to a push encoder and a tiny single-row string on a scribble strip display.
The "Pan/Surround" encoder assignment is missing a second page for vertical panning which is not exposed by the MIDI Remote API.
The "Send" encoder assignment doesn't include a "Bus" page because send busses are not exposed by the MIDI Remote API.
The "Plug-In" encoder assignment doesn't display the number of the active parameter page because it is not exposed by the MIDI Remote API.
The "Inst" encoder assignment doesn't allow loading/switching channel strip plugins because the MIDI Remote API doesn't provide options for it.
The punch button doesn't light up when "Auto Punch In" is activated – no host value available
The global "Solo" LED and the "Solo Defeat" button don't light up when a channel is in solo mode – no host value available
Channel visibility presets do not yet affect channel assignments since the MixerBankZone of the MIDI Remote API doesn't respect channel visibility presets (".setFollowVisibility() is a teaser for future updates").
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)
When controlling under-the-cursor values, the encoder's LED ring is not updated to single-dot mode but remains in whatever mode the currently active encoder assignment demands (blocked by https://forums.steinberg.net/t/831123).

Troubleshooting

Having issues with the scripts? Here are some common problems and potential solutions you should try before reporting an issue:

Some buttons do not work as expected

You can re-map most surface elements (buttons, faders, encoders) using the MIDI Remote Mapping Assistant in Cubase. Those mappings are stored as JSON files in a User Settings folder at Documents/Steinberg/Cubase/MIDI Remote/User Settings, next to the MIDI Remote Driver Scripts folder. If some button/fader/encoder isn't working as expected – especially after an update to the script – it is always worth a try to remove the user setting files (those starting with your script's name) to make sure they don't interfere with the script's default functionality. Afterwards, restart Cubase to reload the MIDI Remote scripts and settings.

The SMPTE/Beats button doesn't change the time format

The SMPTE/Beats button is mapped to the "Exchange Time Formats" command which switches between the primary and secondary time format. The button has no effect when both time formats are identical, so make sure you have selected different primary and secondary time formats.

One or multiple devices are unresponsive

Try disabling and re-enabling the controller script in the MIDI Remote Manager to make Cubase re-detect the script's MIDI ports.

cubase-mcu-midiremote's People

Contributors

Stargazers

Watchers

Forkers

djaychela perivar obandi synthkeywizard fleondelarosa chgros zheksa

cubase-mcu-midiremote's Issues

Icon V1-M/V1-X version

Discussed in #22

^{Originally posted by Hiddentalentpro December 27, 2023}
I've had my Icon V1-M for a little less than a month now and was wondering if anybody out there has attempted to work on a MIDI remote patch to get all of the features working with Cubase. Mackie protocol works fine, just no channel colors, no master out meters and second display screen only shows CH01, CH02 CH03...

Great news @Hiddentalentpro! iCON is providing me with a V1-M for this, so it is happening! 🎉

X-Touch scribble strip backlights not deactivated when loading an empty project

Something I noticed only yesterday when creating a project from scratch (using Cubase 12.0.70). Typically not an issue for existing projects, but annoying enough to look for a fix.

Double tap STOP button to RTZ?

Hi! Brilliant stuff. I am using an X-Touch One with MusicTechTuiton's modifications to your script. I was wondering if it's possible to implement double pressing the Stop button to Return to Zero on the timeline in a future version? Or perhaps if Rewind and Stop were pressed simultaneously it would RTZ it would be easier to implement? Just kicking out ideas

déplacement de pistes cubase 12.0.70

Bonjour, J'ai remarqué un bug qui fige cubase dès qu'on veut déplacer une piste.

Lights only come on and never go off?

I'm new to this so apologies if this is naivety on my part.

I've set up the script as documented and my x-touch is working... in a fashion. It seems that every button I press that illuminates an LED results in the correct operation but that LED never goes out.

As an illustrative example if I load a project, hit "play" and then select each of the current 8 tracks, I am left with all 8 track select LEDs on. This makes my x-touch pretty unusable since after a small amount of work so many lights are lit I have no idea what I'm doing. As another example if I tap the "cycle" key, cycling is correctly turned on or off but the lights remains on.

Is this a configuration option I've got wrong? A bug in the script? My x-touch is on the latest firmware and is set to MCU mode.

Push Encoders not working for buttons in plugins/inserts

I'm working with Cubase 13.0.21 and the icon qcon pro g2, firmware is 1.15

In some plugins are toggleable parameters like "Auto Release" in the compressor. I can't modify the state with the encoders of my controller, regardless if I turn or push them. Is this a limitation or am I doing something wrong?

Output Fader only updates in one direction?

Hey. Firstly THANK YOU!!!! You are an absolute superstar for doing this, and making a lot of people very happy to get channel colours working on the X-Touch (& others) with Cubase - something we've wanted for years, and Behringer/Steinberg should have done long before now!

I may have gotten something wrong in my configuration (or accidently edited something somehow) / maybe it's intentional / or maybe I have found a minor bug.
So thought I'd flag it - so you can correct (if possible/desired), or if it's actually intended behaviour maybe you could add a comment in the release notes to guide others.

cubase-mcu-midiremote: V1.9.0
Cubase Pro: V12.0.70.
X-Touch - Standard (No Extenders).

I switched the "mapMainFaderToControlRoom" flag to false in the .js file as directed in the release notes - I generally use the 'master' output rather than ControlRoom (which I really must learn to use!).

I noticed that all my channel faders behaved as expected, but my Master Output Fader (Fader-9 = "Main" on the X-Touch) DOES correctly control the mixer master channel. BUT, if I update the master channel volume using the mouse inside Cubase, the fader on the X-Touch does not move to reflect the change.

A bit of investigating, in the Remote Mapping Assistant, and I spotted the Output Fader is configured differently to the other faders - it is marked as Project instead of Global - and Value Mod also set to "Scaled" rather than "Jump."

Updated and saved these values and bingo, everything working perfectly - two-way-mirroring restored :o)

Cheers, Keep up the amazing work!!
Keith

Cubase don't recognize the file

Cubase can't load the file, on mac os x Catalina, it is greyed.
Cheers, Eriberto

Behringer BCF2000 version

Is it possible to add a Behringer BCF2000 to a list of supported models? It has a MCU mode also.

Encoder button issues

Hi,
I noticed that the encoder assign buttons (pan, EQ, send etc.) only work when i press them together with SHIFT. Also, the assignment display doesn’t shows the sub page the numbering.
I experimented and found the following about the “encoder buttons” problem:

Basically the problem is project dependent. The encoder buttons work fine when opening a new project or an existing project.
However, when opening certain projects, the operation stops. And when this happens, projects that were already working don’t work anymore.
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.
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.
I noticed: for OK 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.

pédale de controle branchée sur xtouch

bjr, la pédale de contrôle qui me permet de lancer l'enregistrement ne veut plus être reconnue par cubase 13, sous cubase 12 c'est bon.

Hello, the control pedal which allows me to start recording no longer wants to be recognized by Cubase 13, under Cubase 12 it's good.

Presonus FaderPort 8

Discussed in #33

^{Originally posted by noremorze March 24, 2024}
Hello,

is it possible to make this script for the FaderPort 8?

Hi @noremorze,
looks doable – could you test whether the X-Touch script works with the FaderPort 8 (when manually adding the control surface and selecting the MIDI ports)?
I can't promise I'll get to this anytime soon, but I'll get back to you here then.

Script is sending the wrong Velocity Value (which is being covered by C12, but may not be by future versions).

I don't want to break an NDA, but let's just say I know that this will not work in a future version of Cubase (I think that C12 is masking this error, and a later version will not).

I understand Python well, but don't have any typescript skills, so couldn't do a PR, however, I think in this file:

src/midi/PortPair.ts

There is an issue which is a simple fix:

output.sendMidi(context, [0x90, pitch, +Boolean(velocity) * 0xff]);

Should read

output.sendMidi(context, [0x90, pitch, +Boolean(velocity) * 0x7f]);

So that the script tries to send 127 as the maximum value, not 255. Then it will work.

Support adaptive jogwheel speed

I'm a Qcon Pro G2 user, and surprisingly the Behringer Xtouch script works like a charm on my surface. The only thing I miss compared to the Mackiecontrol is the adaptive jogwhell speed. When you scroll fast, it scrolls fast, when you scroll slowly it is more precise. In your script the jog is locked at the grid settings. Is there on option that could change that behaviour ? (sorry if I am on the wrong place to ask this)

Originally posted by @toto-polo in #7 (comment)

bouton smpte/beat cubase 13

Bonjour, j'ai effectivement un problème avec la touche smpte/beat qui ne fonctionne pas. J'ai regardé vos préconisations, mais je ne comprends pas la notion de temps primaire et secondaire que je n'ai jamais utilisé. D'autant qu'avec cubase 12 ça fonctionne.
merci de vos conseils
Daniel

Hello, I actually have a problem with the smpte/beat button which does not work. I looked at your recommendations, but I don't understand the concept of primary and secondary time which I have never used. Especially since it works with Cubase 12.
Thank you for your advice
Daniel

MIDI communication issues with rtpMIDI

Configuration:

Cubase 13.020
Main Device with two extenders connected via ethernet using rtpMIDI
Device: {"extender", "extender", "main"}

Everything seems to be connected very well, parameter are set correctly on all controllers (rarely a fader is wrong) but one of the three controllers cannot send any parameter to the DAW (no Fader, buttons nor pan)

In most of the cases it is the first extender, which cannot send parameter but it is always reflecting the correct status, e.g. if I click "Solo" on another controller the mute state appears on all controllers correctly.

The reload of the script in the MIDI Remote Manager doesn't help.

X-touch stops sending.

I've noticed periodically that the x-touch stops sending to Cubase. It still receives commands (faders move, transport lights, etc) but fader movements and other commands stops sending. I'm not sure if it's a hardware issue, script issue, or cubase issue.

Windows 10 Pro 22H2
X-Touch Universal firmware 1.22
Cubase Pro 13.0.30
I downloaded and installed newest script 1-24-24

Cubase 12.0.60.

Bjr, j'avais constaté un bug sur cubase 12.0.60 qui le figeait dès que je bougeais les pistes. J'ai donc mis à jour avec la version 1.5. C'est toujours pareil. J'ai essayé cubase 11, il n'y a pas de problème mais bien sûr, pas de prise en charge de contrôle midi. Ce qui pourrait expliquer le lien.

premier test avec cubase 13.0.20

Hi, I just installed cubase 13 yesterday. Suddenly I had lost all my button configuration that I had programmed, I had to redo them. The smpte display change problem does not work when the cubase project is launched. As soon as you stop it, you can change the display (by measure, seconds, timecode or samples).
The “save” button is capricious, one time it lights up when you don’t press it, another time nothing. The way of programming functions has changed, since you can no longer select and apply them through the Cubase interface. You have to do it with the mouse on the xtouch interface. Before I pressed the desired function, on xtouch,
I selected this function from the drop-down menu and applied it. You have to do it differently: now press the xtouch button, directly on the screen which draws the xtouch, choose the function from the drop-down menu and finally apply. So, I see another problem with this function: I use a foot pedal to control the audio or midi recording with my feet, this pedal is plugged into the xtouch 1. With Cubase 12 it works because the operating mode is functional. Now I can't do it anymore.I continue to test.

Feature Suggestion: Invert EQ Gain Action

The CC121 has a handy feature, quote from documentation:

"EQ gain inverse: You can invert the gain curve(s) of individual or entire EQ band(s) on Cubase by using the [ON] button."

Maybe you could add this to one of the encoder press actions (pressing the "gain" encoder might be a logical choice).

problems with Skrip 1.5 in Cubase 12.0.60 Pro

Hello,
I have 2 problems with Skrip 1.5.

under the encoder assign "Dyn/Fx/Aux or Inst I can not edit the "VST Quick Controls". It only shows the track names and that there are 6 subpages.
I have then installed the version 1.42 again, there it works.
I then installed the version 1.5 again and wanted to take over the setting of 1.42. This did not work at all.

Now we come to the 2. problem.
I wanted to reset everything again, which did not work at first. No matter what I did, whether deleting the script and copying it back in, disconnecting the x-Touch from the USB, deleting the script in Midi-Remote. Nothing deletes the wrong script. When I restarted, the old script that I had edited was always displayed.
Only when I completely uninstalled Cubase and reinstalled also worked that the 1.5 script, as it should be.
I think that this is not useful and wanted.

I work with
Win 11 Pro version 22H2 operating system build 22621.1848
Cubase Pro 12.0.60

Many greetings
Lothar Berg

cubase 13

Hello, my first feedback:

No more colors on the control panel, forward, backward, play, record, stop. finally everywhere.

Changed the way to configure the f1 to F8 and master keys. Before you could do it easily by choosing the desired key on the xtouch and then the corresponding function in Cubase and applying it. Now everything can be done via the xtouch with the mouse on the Cubase xtouch. as I have a control pedal that I plug into the xtouch I can no longer affect it

Bonjour, mes premiers retours :

Les couleurs sur panneau de contrôle vont et viennent : avance, retour, jouer, enregistrement, stop. enfin partout .

Modification de la façon de paramétrer les touches f1 à F8 et master. Avant on pouvait le faire facilement en choisissant sur la xtouch la touche voulue et ensuite la fonction correspondante dans Cubase et en appliquant. Maintenant tout de se faire via la xtouch avec la souris sur la xtouch de Cubase. comme j'ai une pédale de contrôle que je branche sur la xtouch je ne peux plus l'affecter.

Daniel

AutoSelect disabled -> Tracks names not updated

Hi
Thanks a lot for the option to disable "enableAutoSelect". But when I use this, the track names in the xtouch displays are not updated anymore when swtching the fader banks or channels. I hope you can reproduce this?

Cubase randomly swaps MIDI ports

Hi,

New issue...it seems like the script or cubase api "lost" the midi ports defined at the set up !

the midi ports were in and out in the same order at set up ... xtouch ext, xtouch, and Desktop....
but at the next start up of cubase project...the midi out ports seem to be unordered and, at this moment, the first extender ( called stouch-ext ) doesn't work properly anymore....it show the tarcks names but not colors....

Originally posted by @limageurpublic in #1 (comment)

choisir temps écoulé version 1.70 et 1.80

Bonjour, quand j'appuis sur la xtouch pour avoir la durée du morceau, on voit l'information dans cubase 12.0.70, mais pas sur la xtouch, çà n'inscrit pas la même chose que cubase.
cdt

Hello, when I press the xtouch to get the duration of the song, we see the information in cubase 12.0.70, but not on the xtouch, it does not register the same thing as cubase.
cdt

Issues with Cubase 12.0.60 and 12.0.70

First off. Thank you for your work on this script. (I love it). With that I have a scribble script issue that is only present in Cubase 12.0.60 and the new 12.0.70. (Cubase 12.0.52 Worked great)

Scribble strips will have the wrong track names. ex: I have a track named "Bass" and the scribble strip shows "toms". It isn't with just one track, but many. When I revert to Cubase 12.0.52 the problem is solved.

Any input you can provide to help solve this problem is greatly appreciated.

Thanks again for your hard work.