In the past 4 days i have had over two dozen crashes in cubase. I am working on a project where I have to apply tempo mappings to hundreds of wave files and stems. Cubase crashes a LOT when I delete files from the pool, when I delete tracks, when I disable tracks, it’s driving me up the wall. Latest few crash logs are included.
I think I found something that relates to this problem - i have disconnected all input busses from my hardware interface (in the Audio connections window). Seems like I can now disable and enable tracks without crashing. I remember seeing a similar issue on the forum a while back so I tried it, and it seems to work.
Kind of a crappy workaround, especially since I’m working with a Steinberg interface, it really should just work - but for this project I don’t need to use inputs. Still, would love for this to be fixed though.
Wow it’s crazy that disabling inputs would solve your issue …
Since I’ve also had lots of crashes with Cubase 14 Pro I will try that too…
Also bear in mind if you use a dual screen setup there are possible issues too, I just posted a solution for that.
Good luck on your side !
I have two monitors. The crashes described in your posts don’t seem to be related to my issue. My crashes are not a ‘hang’ with a spinning wheel but an instant closing of the application. (although it’s good to know that issues can be caused by a dual monitor setup, so thanks for bringing that to light!)
It seems like the input bus workaround has solved the issue. I have a macro that disables all tracks in a selected folder, this was a 100% guaranteed crash before I unassigned the input busses.
I suspect the integration of the UR44C interface with Cubase has something to do with it - it adds some basic hardware controls to the MixConsole.
By the way, the crash seems to only occur when I’m disabling/deleting an audio track that is connected to a hardware-connected input bus. If it’s connected to a group, for example, it doesn’t cause a crash when I disable or delete it.
For now I have a workaround, haven’t had a single crash since - obviously it’s not workable long-term, so I hope steinberg can get around to squashing the bug.
Glad you have a workaround for now. Cubase has areas for improvement with dual monitors and with inputs, as well as zoom, I posted this, check it out :
Hi Martin regarding the multiple monitor issue leading to plugin opening white and freezing Cubase, I just had another new case this morning with Waves Electric200.
After Cubase crashed I unplugged my 2nd monitor, opened the song on Cubase, plugin opened fine on the main (and only) screen, then saved the song to let it remember the plugin location. Closed Cubase and replugged my screen, upon reloading the song with 2 monitors again the plugin opens fine in the first monitor.
I didn’t have this issue about a month ago, no idea which update or install changed that. If you could help that would be great. Danke. Cubase 14.0.10 64bit 2025.2.18 10.55.06.428-freezedump.dmp (1.8 MB)
It has nothing to do with Amplitube actually.
I made a short video on a new empty project for you, what you will see is my second monitor capture :
I open a new Waves piano by first bringing the open window DOWN to my first monitor which is under the captured one. Otherwise it would go straight to white.
Then bring the plugin UP, and that works, but if I close it on the second monitor and reopen it there, freeze.
And if I have existing projects where Cubase remembers the position of the offending plugins (Waves, Arturia…) are on the second screen then I cannot open their GUI.
My only fix would be to unplug my second monitor, then open the project so Cubase could bring back all windows to the main monitor.
Really hoping for a fix, this is damaging my workflow.
Thanks
I have tried 6-7 times but didn’t manage to get a dump file with the Waves Electric200 going white and freezing Cubase.
But on first try I got one with the Arturia Lab, which does exactly the same. Cubase 14.0.10 64bit 2025.2.18 17.32.40.836-freezedump.dmp (1.4 MB)