I understand that Martin, it is not ideal, but the crashes are hangs and do not produce dumps. Cubase doesn’t seem to realise anything is wrong.
There are multiple issues here. I have conformed with all of the troubleshooting advice gleaned from this and many other sources over the years. To no avail. The problems still occur intermittently and are not consistently reproducible. To break them down by category if that helps.
- Loop issues and crashes. (the initial reason for this thread)
On one particular project, when I defined a loop (using the Left and Right Locators and Transport Cycle) and hit play the program crashed on reaching the Right Locator. That happened irrespective of where the loop was placed in the song.
I have since loaded several projects where a loop was in effect when the project was saved. It is therefore loaded as predefined. The program completely ignores these loops on playback and will not play a loop until the original (saved) one is switched off and a new one defined. The program then operates normally.
That maybe points to data associated with the project being misinterpreted on load or run maybe?
- Project load issues and hangs
Yet another incident has occured as I am responding to this thread. I have just tried to load a project which I was using quite successfully this morning at 2:00 AM. There are no out of date plugins in use with this project. The only non-Cubase plugin is a couple of instances of ReValver4 x64 running impulses. The project uses HALion6 (although it was originally stored with HALion5). The project was working fine and I saved a new version of the program before closing down Cubase for the night. I have just loaded the project and it hung on the mixconsole. The only way to regain control was to use the Windows TaskMaster, kill the Cubase program and then I had to remove and reinsert the eLicenser before it would reload Cubase again. The only way I have found to reload this project (and others under the exact same circumstances) is to load a different (small) project, Have that run. And then load the problem project without Activiation. Once that is loaded and stable, Activiation will (sometimes) allow the program to load. I can then close the original small project and continue. There are occasions however when this procedure still hangs.
Again project data? Loading a sacrificial project is initialising something that is missing from the problem project?
- Sudden spike in CPU and dropout from recording.
There have been a number of instances where the CPU has spiked without warning during recording resulting in drop out of the recording function and a ‘problem’ message. This never occurred for me with Cubase before Pro 9.5, and is now worse under Cubase Pro 9.5.2 than previous versions. I have not changed my workflow or process with upgrades to the later versions other than ditching non-compatible plugins.
Data buffering or some such issue?
I am at a loss as to where to go from here. I do not believe I am alone in this judging from the internet chatter. The situation is very problematic and I am seriously considering changing platforms completely to one of your competitors. I can no longer afford the time and the hassle and there doesn’t seem to be a massive amount of help forthcoming from Steinberg. Cubase used to be bomb-proof for me. It isn’t now.