Would it be possible in the near future to implement a VariAudio function that allows not to detect consonants? Cause the way it is now one has to split segments in order to avoid consonant related artifacts when changing (even slightly) the pitch of a given note.
Thanks!
Maurizio
Quick sanity check into the room, because Iām genuinely curious whether this is just bad luck on my end or a more common Windows 11 experience.
Iāve been using Cubase for a long time, and honestly, I canāt remember the last time I had a version that felt this unstable. On my system (Windows 11, 64-bit), Iām repeatedly running into situations where Cubase freezes the UI when opening certain VST user interfaces, while playback happily continues in the background. At that point, thereās no recovery - Task Manager is the only way out.
On top of that, crashes when closing a project and returning to the Hub have become almost routine. Not every single time, but often enough to be genuinely disruptive. What makes it more frustrating is that this behavior is still present in the latest update (15.0.10).
Donāt get me wrong: I do appreciate new features, and itās great to see Cubase adopting ideas that other DAWs like Bitwig or Ableton Live have had for years. But for me, stability is still the absolute baseline requirement for a DAW - and right now, that feels shaky at best.
So Iām honestly wondering: is anyone else on Windows 11 seeing similar issues? Or did I somehow end up with the one cursed configuration that Cubase 15 really doesnāt like?
BTW: āDealsā is probably the one thing I need least in the Hub. When Iām in production mode, I really donāt want to go shopping. Whatās next - banner ads for plugins in the MixConsole or sample pack promos in the Media Bay? 
Mine crashes on startup frequently. Iāve put Cubase to one side for now, Iām investing my time in Dorico.
Of course it would be possible.
It was done years ago by Celemony, in the plugin Melodyne.
For Steinberg/VariAudio, this would be a matter of feature priorities and the return-on-invest.
Well. Also bad experience with 15.0.10
After project load, UI hangs for one minute, then it works a while, and stutters again after while.
Also, when i zoom in, waveforms shows letās say tom hits on places where they are not supposed to be, and when zoomed out everything in on itās placeā¦
I see that Omnivocal is up to version 1.1.3 in this update but after updating, my version, in Cubase 15.0.10 is still 1.0.6.
Tahoe 26.2 on a MBP.
Any ideas?
Just go into Steinberg Download Assistant, select your Cubase 15 (Pro) product under āMy productionsā in the left pane, expand āToolsā and update from there.
1.1.3 is still āBeta,ā so maybe thatās why itās not automatically showing up in āUpdates.ā
The update works well for me. The midi controllers seem to work fluently now.
One problem that still knocks out Cubase and freezes everything is the occasional Waves plugin freeze that started with Cubase 15 for me. And Kontakt 8 is still super slow to close. I donāt know if itās a Cubase problem or the plugins that are messed up. I tried reinstalling them (Kontakt and Waves), did many batch resaves with Kontakt, nothing helped so far.
I noticed that Cubase was hanging when checking VST3s on startup. When I checked the log it turns out that it didnāt like any of the Pre V14 Waves plugins. I did the WUP on the plugs I wanted and unistalled the rest and all is well. Canāt say for absolutley sure, but I donāt think I had this issue with CB14.
Hope that helps.
I seem to be having issues with routing. I was working on 8 projects until yesterday, some of them created in Cubase 14 and the rest in 15, and it seems that every time I open a project 1-2 midi channels/clips will be routed to the wrong instrument. I think this started happening after the latest update. Anyone else notice this?
Yeah, something similar. Sometimes I need to recreate an effect in order to route it to the correct bus.
What?
Yeah, so when I create a send effect sometimes it does not get routed to the correct bus and itās not even possible to route it to that bus because it does not show up in the direct routing menu. Hope that explains it.
Thatās most likely due to Cubase preventing the creation of feedback loops. So check for any of those.
So, when I recreate the effect, it does allow me to send it to that particular bus, so Iām thinking itās a bug. Maybe Iām missing something though. I donāt really know about the feedback loop issue. Sounds like something I should look into.
Yes, you should. Sometimes what seems to be a bug actually is a lack of knowledge of the operator.
Yeah but sometimes itās also a bug in Cubase right? I also have noticed odd behavior since I have installed C15 Proā¦ Thatās why I always wait when a maintenance update is released.
Canāt imagine getting my work ruined because of an update as I have already seen here
And will there be an increase in physical inputs? Thanks.
When I hold āCtrlā in Cubase editors, I can move an event or a clip freely without snapping or magnetism. Thatās ok.
HOWEVER, it doesnāt work when moving slices in the sampler, it always moves in a snap way, even if I have turned off the Zero-Cross button.
This āCtrl + Move Slice freelyā function is also absent in Groove Agent, please make it work just like I would expect in Cubase editor.
Another request:
Add āAmp Velocityā knob in Sample sounds for the Beat Machine, because it is only available for the Oscillator-based sounds:
Itās annoying because I am trying to use the Filter Velocity knob but since there is not an Amp Velocity knob then the volume is also being affected besides of the Filter Vel.
