Thank you for the warm welcome, directly diving into a hot conversation
I understand you. The value lays in the âusingâ Of course, how could it not. Buying the license and wait with the activation of course is also possible, if one does not need the newest version right away. It is an effective sales model, not gonna lie. Make a sale, wait about a month after, and release the new version with a grace period for the people who missed the sale (which I highly adore, not gonna lie). I just have to admit that I am one of the annually upgrading persons, trying to hold Cubase up to date (therefore also looking for a sale period), so its just the innner anger of having bought an upgrade, and shortly after, there is the next upgrade already, although there has not even been a Cubase 14.5 version.
Letâs just say: I know for upcoming events now. And I still respect steinberg for offering a grace period anyhow.
I stille have them everytime I close a project. Cubase always crashes. Especially when I have a Splice plugin in the project. Deleting tracks, is crash, deleting plugins, is crash, farting, is crash. This program is far from stable. Even when I reinstalled my whole PC with just windows, cubase and plugins (Waves, Splice, Serum, Sylenth, NR Kick and kickstart). It worked for 2 projects and then it started again. This is my life nowâŚ
Hello, a few questions about the hub: why was the âquitâ button removed?Next, I noticed that the close button for Cubase no longer displayed a message; I had the performance window open, and when I closed my project and quit, the window was still open.
Good evening! I have several questions. Iâve searched everywhere and havenât found any answers.
1- How can I make the selected MIDI (and audio) event brighter than the unselected ones? Itâs the other way around right now, and itâs incredibly inconvenient. Itâs bearable with audio, but completely inconvenient with MIDI.
2- How can I remove the white letters on the buttons? So, how can I make them black instead of white? Or maybe not as bright?
3- How can I reduce the overall intensity of the white color? Itâs really hard on the eyes.
4- The L (Listen) button on a track doesnât work, even though Control Room is enabled. Well, itâs active, but the other tracks donât get any quieter when I press it.
5- How can I hear the sound of the selected sample in the browser when Control Room is enabled?
But did you try clean installing and using Cubase WITHOUT any 3rd party plugins? Then adding the plugins one by one to determine which one is causing problems, be it Splice or something else.
Is it really fair to call Cubase a professional DAW if it still canât handle MIDI properly?!
For the last 20 years nothing has changed â every update leaves me disappointed . Cubase still has no reliable way of working with MIDI devices. If you accidentally touch the cable of your MIDI controller orâGod forbidâdisconnect it for a moment, your whole day is ruined. This is unacceptable in 2025 for a âproâ workflow .
The MIDI Remote Manager is another pain point. One wrong move â and a device entry disappears forever . The device info window is filled with irrelevant data, yet there isnât a single button to reconnect the device or reassign ports. Hitting âAdd Surfaceâ throws you into another dialog where you must again search for your device name and even manually select the manufacturer . This shouldnât be the experience of a modern DAW.
And the worst part â the Combined Panner.
It has existed for over 20 years, and it STILL canât be assigned to a MIDI controller fader . I can write automation, I can assign it to Quick Controls â but assigning it to MIDI? Still impossible. Why?! This feature is essential for real mixing workflows.
Please, Iâm asking with full respect â these issues are not new, not niche, and not minor. Theyâve been blocking real-world, professional use for decades.
We need Cubase to finally treat MIDI with the stability and flexibility expected from a top-tier DAW .
Iâm afraid thatâs a Windows thing. Itâs kinda bad on Windows with everything.
Microsoft is supposedly going to give MIDI a complete overhaul in the not so distant future. Theyâve been working pretty hard at it (and some preview versions are out there). Itâs supposed to catch up to MIDI 2.0, allow users to rename devices/ports, do wireless stuff better, provide virtual routing, make better drivers possible, fix the age old issue with multi-client USB<>MIDI drivers, maybe even include RTP via IP, and moreâŚyet maintain compatibility with the decades worth of stuff thatâs already out there. I suppose weâll just have to wait and see how good or bad itâll be.
Itâs in the pipeline for a public release in Q1 CY 2026. (The bits are in the right branches and builds.)
It wonât immediately help add/remove detection for apps that donât use the new SDK, however. Itâs up to app developers to use the new APIs to be able to more easily detect that. (There are ways to do it today, but they are not well-known by folks, and tend to only work reliably for USB).
Itâs a shame because it is an easy fun DAW to use. I will always have a soft spot for it.
As for Cubase. Since making that post I have had a hard think on things. I refunded Cubase 15 and have decided to go fully to Reaper. Financial and stability are the main factors plus I can customise what I wish and everything works. There are plenty of good things about Cubase though and I may return later down the road.
Good luck to everyone with Cubase and take care for now
The key command to open the Sampler no longer works in Cubase 15 on macOS. Specifically, the âEdit VST Instrumentâ key command has stopped working for the Sampler in this version.
. Cubase still has no reliable way of working with MIDI devices. If you accidentally touch the cable of your MIDI controller orâGod forbidâdisconnect it for a moment, your whole day is ruined. This is unacceptable in 2025 for a âproâ workflow 
.
. The device info window is filled with irrelevant data, yet there isnât a single button to reconnect the device or reassign ports. Hitting âAdd Surfaceâ throws you into another dialog where you must again search for your device name and even manually select the manufacturer 
. This shouldnât be the experience of a modern DAW.
. I can write automation, I can assign it to Quick Controls â but assigning it to MIDI? Still impossible. Why?! This feature is essential for real mixing workflows.
â these issues are not new, not niche, and not minor. Theyâve been blocking real-world, professional use for decades.
.
