Cubase 14.0.40 Maintenance Update

Have a look in the Nuendo forum.

Mac Sequoia 15.5 - Kontakt 5 disappeared. Can’t do without it.

Took the update (despite reading this thread), midi remote scripts all happy, no issues to report.

Sorry, too boring?

Not boring at all, just bold! :smiley:

No issues here so far. Cubase has been calm for a while now :call_me_hand: :crossed_fingers:

That’s interesting…

Cubase 14.0.40 was released around the same time as the 25H2 version of Windows 11.

The problems with MIDI Remote discussed here were blamed on Steinberg,
but apparently only Microsoft made mistakes, if I read this correctly:

Windows 11 install 25H2 MIDI devices and the Registry problems

This implies that we should now ask the question: who are Microsoft’s beta testers? Are there any musicians among them?

4 Likes

Well I think the issues I had were when I installed the 24 version. I don’t remember C14 being so crashy before that. With a few tweaks and cubase update it’s calmed down. So I would think the 25 version no doubt has caused issue.

1 Like

I only installed 25H2 yesterday.
The other problem with the Korg drivers mentioned on the Microsoft website has been around for several years and is more likely to be attributed to Korg.
The Korg devices malfunction when installed higher than Midi 10.

All my assignments were gone after the Cubase update, and not for the first time. There was also no way to recover them from backups, as a new file with a new name had been created. Even after changing the name of my old file to match the new file, Cubase still wouldn’t recover all my pages and assignments. I’m not a programmer and can’t change the files internally, so maybe there was something else wrong.
It’s undisputed that Steinberg has made some changes to the MIDI remote, but the fact that everything has to be redone doesn’t really speak well for Steinberg. Especially because with every update, you have to worry that something has been changed again, which destroys the MIDI remote you set up yourself.
It may be that this problem does not occur with templates from manufacturers.
However, it should also work if you set up the controllers yourself. It was heavily advertised at the time, so it should run stably at some point.

I don’t earn money from making music, but time is still precious, especially because I don’t get to make music that often. I don’t feel like it, let alone have the time, to redo all the assignments.

Are you questioning Pete’s abilities as a musician? :slight_smile:. :slight_smile:

I’ve had to deal with the Korg USB drivers a few times with some of my hardware. The little app you show here is easy to use and sort out though.

1 Like

I just click and hold, anywhere on the track channels, and drag left or right ā€˜til what you want comes up. A trackpad is great for this type of thing too, just using 2 fingers to swipe right or left.

In terms of a mouse, I don’t see that behaviour here (on a Mac). Trackpad might make a difference, though…

Graphical Freezes in Cubase 14 on macOS Tahoe

System

  • Mac Mini M4 (2024)

  • OS: macOS Tahoe 26.0.1

  • Monitor: Huawei MateView GT34

    • Aspect ratio: 21:9

    • Resolution: 3440Ɨ1440

    • Refresh rate: 100 Hz (limited by HDMI or Mac, monitor supports up to 165 Hz)

Software

  • Cubase Pro 14.0.40

  • The issue occurs both in clean projects (no plugins) and with plugins loaded.

  • Everything worked fine on macOS Sequoia before upgrading to Tahoe.


Issue Description

When the Channel Settings Window (the one with inserts and EQ) is open, Cubase’s graphical performance drops drastically if this window is covered by any other window — for example, a plugin window or another macOS window.

A similar issue also appears if a plugin window with a graphical interface (e.g. FabFilter Pro-Q 4) is covered by another window.

  • Audio playback is unaffected — sound runs smoothly.

  • However, the entire Cubase GUI starts to lag and stutter severely.

If:

  • The Channel Settings window is closed — the problem disappears completely.

  • The window is only hidden behind the main Cubase window — the lag remains.

  • The issue does not occur on my MacBook with the same Cubase and macOS versions.


Tested Steps

I tried the following tests:

  1. Running Cubase in Safe Mode — no change.

  2. Lowering monitor refresh rate — no effect.

  3. Full macOS Tahoe reinstall — issue persists.

  4. Downgrade to macOS Sequoia — everything works normally.

  5. Testing Cubase without any plugins installed — issue still present.

Interesting detail:

  • When I launched OBS (screen recording), the lag temporarily disappeared — Cubase ran smoothly even when windows overlapped.

  • However, after restarting OBS, the issue came back, and I couldn’t reproduce that behavior again.


Request to Steinberg

I’d like the Steinberg team to:

  • Check Cubase 14 compatibility with macOS Tahoe, especially with ultrawide monitors;

  • Investigate how the Channel Settings window GUI is redrawn when it’s covered by other windows;

  • Possibly test with a Huawei MateView GT34 or similar displays.

  • In general, I’d really like this issue to be fixed, as it heavily affects workflow.

Below are video examples of the situation. By the way, for some reason, in one of the examples, at one point, the sound simply stopped recording. I do not know why.

p.s. You can not post links here, but I can not fill in the whole video, so I will put spaces, I hope you will understand me.

https :// youtu.be / axzwvwVZQzg

https :// youtu.be / Beqs8xpqqFE

1 Like

Same Problems - very bad update! THX to Steinberg!

1 Like

Same here — I’m also experiencing that bug with the sends. Additionally, fader volume changes aren’t being registered in the history when values are typed manually..

1 Like

Hey and Jeep,

I’m having the same problem. With a lot of effort, I integrated my Novation 61SL MKII MIDI keyboard into my DAW using Remote MIDI Script. For several VST3 synthesizers, I assigned the faders, sliders, switches, etc., to the control panels of my Novation Remote Controller, using the 32 templates. That made a total of seven interfaces, which I created using the Remote Assignment Wizard. The assignments on the respective interfaces were all saved globally and, according to Steinberg, should be available in all projects.

This worked perfectly until Cubase 14.0.32.

Then came the update to 14.0.40.

The update description states under ā€œWe have improved the following functions and features: ā€˜MIDI Remote now saves and recalls previously configured devices as expected.ā€™ā€ Yeah, right.

Unfortunately, that’s not the case. All my settings, including the assignments on the respective interfaces, are gone. I only see an empty ā€œDefaultā€ interface, nothing else. The same thing happens in Cubase 15. Just to be safe, I backed up the MIDI Remote script files located in ā€œ\\My Documents\Documents\Steinberg\Cubaseā€ (Dir: MIDI Remote, Dir: User Presets). That didn’t help either. I restored the scripts to their respective directories, and the same thing happened.

Wow! It’s understandable that a feature might not work perfectly after an update. But for painstakingly created settings to simply disappear is unacceptable. I’m not writing any more because I’m getting really angry.

Addendum:

The issue I described with the MIDI Remote scripts seems to be a fundamental problem with the 14.0.40 Maintenance Update.

I’ve taken a closer look at it. The MIDI remote scripts are located at:

XXX:\My Documents\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts

For example, the Novation script is located here:

XXX:\My Documents\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\Novation\61SLMKII\Novation_61SLMKII.json

ā€œNovation_61SLMKII.jsonā€ is the template (controller interface) with the empty, unassigned controls for the Novation keyboard.

Also located here:

XXX:\My Documents\Documents\Steinberg\Cubase\MIDI Remote\User Settings

The file:

Novation_61SLMKII_DB6312101867131AEF9B499C3DE58BBE_globalmappings.json

currently 68KB in size.

This file is generated via the mapping wizard, and for each configured mapping (there can be multiple mappings, added via mapping pages), the corresponding mappings are saved in JSON format. The default mapping is always present at the beginning, serving as a template.

So: In version 14.0.32, everything was fine. After updating to 14.0.40, the following happens: After starting Cubase, only the default mapping is available in the MIDI Remote. The controller interface is still there, but only with empty, unassigned controls.

The file ā€œNovation_61SLMKII_DB6312101867131AEF9B499C3DE58BBE_globalmappings.jsonā€ still exists in the directory XXX:\My Documents\Documents\Steinberg\Cubase\MIDI Remote\User Settings\, but it is now significantly smaller (6KB) and only contains the settings for the default mapping. The rest, for whatever reason, no longer exists.

I had created a folder called ā€œSaveā€ under XXX:\My Documents\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\Novation\61SLMKII\ and i always backed up the files there. Not a good idea.

After the first launch of Cubase 14.0.40 and opening the MIDI Remote Manager and the MIDI Remote Assignment Wizard, the backup directory, along with the backup copies, was gone. Luckily, I always have a second backup connection and thus a second access to the backup copies. However, importing the backed-up script files, e.g., ā€œNovation_61SLMKII.midiremote,ā€ via the MIDI Remote Manager failed with an error message and therefore didn’t work.

I don’t need to understand any of this anymore. As it currently stands, the Cubase 14.0.40 MIDI Remote API is, to put it mildly, suboptimal.

Be that as it may.

2 Likes

Update (Cubase 15)

I’ve just tested this issue in Cubase 15, and it seems that the problem has been partially fixed.

The graphical lag no longer appears when a single plugin or Channel Settings window is covered — which is great progress.
However, after some testing, I noticed that the issue still occurs when multiple plugin windows overlap.

When around five or more plugin windows are stacked on top of each other, the same graphical stuttering and sluggish GUI performance start to appear again.
Audio playback remains smooth, but the user interface becomes noticeably less responsive, just like before.

So the problem is not completely gone, but it now takes multiple overlapping plugin windows to trigger it instead of just one.