I’ve installed a few plugins and I hadn’t any blacklist errors. Now I got back to an old project I was working on few days ago and I constantly have crashes every 1-2 minutes with no reason. I don’t even use any plugins. I did few channel presets transfer and making a new version in an old folder. How do I debug my issues?
I think something are with the sample tracks or track presets recalls. Cuz crash started as I decided to transfer some ideas from an old version to a new one. I saved track presets and copy\pasted MIDI. Then I switched back to a new version, started add tracks presets and Cubase start crashing like cursed.
Guys, support, please help me, Cubase really behaves strange, I can’t work! I started over the project, everything from scratch, only stock plugins (only a few, compressor, delay, reverb). The only thing is I use old folder to not duplicate files, so few projects use the same Audio folder. Cubase constantly crashes. Here’s a new dump. And that was not an issue few days ago! Cubase 10.0.20.187 64bit 2019.7.14 15.53.28.846.dmp (621 KB)
I guess it’s something wrong with the audio files, if I copy, render in place or import audio - there is big chance it will crash. I’ve updated to 10.0.3 just now. I repeat, no 3rd party plugins, Cubase still crashes. Cubase 10.0.30.236 64bit 2019.7.14 21.43.17.829.dmp (671 KB)
Note:
Corrupted program preference files can bring your Steinberg program into all kinds of troubles, particularly after installing an update.
Fortunately, refreshing the preferences is quite easy:
Close all programs.
Open the ‘Run’ command prompt by pressing the Windows logo key and R on the keyboard simultaneously. The Windows key is located between the keys Ctrl and alt.
(To open the command prompt on Windows XP select ‘Run’ from the Start menu.)
In the command line of the ‘Run’ window, enter this path: %appdata%/Steinberg
Locate the folder which is named the same as your Steinberg program, for example ‘Cubase 8.5’.
Rename it (for example, from ‘Cubase 8.5’ to ‘xCubase 8.5’) in order to hide it from your Steinberg software. The folder will only be hidden safely, if the change will be done before the original folder name.
If you find folders of previous versions of your program, make sure to hide or remove them, too.
Next time you start your Steinberg program it will create a new folder with fresh preferences and default settings - which hopefully fixes the problem you’ve experienced.
Please note: Make sure to hide or remove preferences folders of all installations of your Steinberg program. Otherwise the program would try to comply with them when creating fresh preferences. And exactly this could be the source of errors.
Initialising the program’s preferences does not necessarily mean that you lose all settings. For example if you have defined your own set of key commands that you want to keep you can replace the corresponding file (Key Commands.xml) in the freshly created folder by a copy of the same file taken from the folder you’ve disabled by renaming.
Alternative ways: Instead of renaming it, you also can move the preferences folder of your program from Steinberg’s application data folder to another place, for example the Desktop. You even can simply trash it if you are sure that your user settings are not that hard to rebuild. Another approach: Since in many cases the file ‘Defaults.xml’ will be the trouble maker you also could try if renaming or deleting only this particular file already solves the problem.
This Knowledge Base article provides further information on Cubase’s preferences and their location: Preferences of Cubase and Nuendo
Making a backup of the preferences obviously is a good idea, especially when you customize a lot. And it’s easy: Simply keep a copy of the preferences folder that you can fall back on whenever you need to reset the preferences to your preferred settings.
I really knew about this way and I didn’t try it because I thought this had low possibility. I didn’t have some accidents that could damage my preferences. But I did reset and it’s stable now And I have remembered how one plugin crashed it, that might be the case preferences were damaged.
And I have remembered how one plugin crashed it, that might be the case preferences were damaged.