Sorry I started a thread on this issue,
Martin has already reported this issue to me.
But I dare to post it here because I expect that Steinberg is probably not going to fix this problem at all in the future.
What I find strange is that this is a bug in a really basic operation (which is not possible with any other DAW) and that there are so few voices about it.
I’ve heard very little outcry about this.
I find this quite frustrating, but I’m wondering if you guys don’t see this as a problem?
Especially when I’m on deadline and have to do a last minute mix, and I’m messing with the left spectra and I’m like, “Oh, I’m messing with another track…” and then I have to go to the trouble of fixing the settings.
Is there by any chance a good workaround?
If so, I’d like someone to tell me.
I am not writing this because I want to start a negative campaign against Steinberg.
If Steinberg doesn’t fix it, I’d like to find a workaround on my own.
If anyone knows a better way, I would really appreciate it if you could let me know.
is there any more info in the dump file? I have been using that plugin with every version of CUBASE I have, and all the three previous versions gave me no issue whatsoever. Can I temporary disable it and see if the problem persists? Could you direct me in how to do it?
You can hide it from the plug-in list. But the plug-in would remain in already existing projects. Or you can move the *.vst3 file temporarily out of its folder. Cubase will not see it anymore.
Dear Developers Pls take a look at my recent finding in regards to Cubase 14 pro 14.0.32 performance issues which are also the case for all Cubase 13 pro versions.
Nividia default drivers for 4000x and 5000x cards and the latest functions of Nvidia could be the main reason in combination with the GUI of Cubase or Program Structure that might cause the issue in Cubase 13 and 14.
(Cubase version 14.0.32 (Apple Silicon))
(Mac OSX: Sonoma 14.7.4)
(Device: Mac Studio M2 Ultra)
When using the Divide Track List feature to split the tracks into upper and lower sections on the main page, sometimes when I drag a track from the lower section to the upper section, the track automatically disappears. It doesn’t show up in the Visibility menu either — it just completely vanishes.
After using the Quantize MIDI Event Ends and Quantize MIDI Event Length functions, the MIDI notes affected by Quantize Length cannot be undone with Cmd+Z. When I try to undo, it jumps back to an earlier step instead — sometimes even deleting the MIDI notes entirely.
I tried using the Edit History to see what happened. In the MIDI Quantize process, Cubase indeed didn’t record the MIDI Length Quantize step, and when I performed an undo, the original Quantize action got replaced by another command.
To clarify: You moved a Folder track. But even then, I can’t replicate it.
If the Notes are Quantized already and you Quantize them again, the function doesn’t appear in the History. The same applies for the Length Quantize. So your case:
Quantize: Has not been Quantized and the function appears in the History.
Quantize: Has been quantized already, therefore the functions doesn’t appear in the History.
Or even to rename/remove all Cubase versions preferences folder to get the factory setting.
Cubase Preferences folders are: Mac: ~/Library/Preferences/Cubase X Win: %appData% \Steinberg\Cubase X_64
Where the X is the Cubase version (for example 14).
Hi,
Just wanted to add a bit more info:
in the Quantize Panel, I’ve set Soft Quantize to 76%.
In theory, both (two)Quantize actions should still show up in the Edit History. (Is that correct?)
As for resetting and Safe Mode, I’ll give those a try when I have some downtime between projects! Thanks so much for your help!
I just tried removing the Cubase 14 Preferences folder as mentioned above, then launched in Safe Mode and ran with Disabled Preferences — but the issue still happens.
I noticed this usually happens when I quickly run Quantize Notes and then immediately Quantize Length — that’s when the issue occurs.
When I move a Folder Track or Instrument Track to the upper section, it doesn’t cause any issues in a brand new (empty) project. But when I create a new project and then import the 2000 tracks from my template into it, the same problem still happens.
I’m not sure if this only happens in projects with a high track count. In my template, all the tracks are in a disabled state, so they’re not using much CPU or RAM — it’s just that there are a lot of them. But whether it’s a Folder Track, Group Track, Instrument Track, or MIDI Track, dragging them up into the upper section still makes them disappear.
However, if I drag them over more slowly, sometimes the issue doesn’t occur.
Thanks again for your help — I hope this issue can be resolved.
I haven’t tried with 2000 tracks. But I tried in a simple project, just to ensure that the Import from Project function isn’t the culprit. And it works on my side.
Btw, why do you import all tracks from a template? Why don’t you create a project from the template instead?
Since the same issue happens when opening from the template, I thought the template project file itself might be the problem.
So I tried importing the tracks into a new project to see if that would fix it — but it didn’t. In daily work, I usually open new project directly from the template menu.
I see. Would you mind sharing the template project? You can do so via the Private Message. I would like to try it with the given project and slim it down, to be able to report it as a bug.
I am encountering the same problem I had before with Cubase 14: I open a project, and Cubase keeps hanging on the same loading window for ages for no apparent reason.
Last time you mentioned it was caused by a plug in, but on this machine the plugin is not even installed.
