Not sure if anyone can help with this, or maybe confirm that it’s not just me…
Cubase 13 Pro is crashing when using Audio Warp on multiple tracks within a folder with Group Editing and Phase-Coherant AudioWarp selected. It is happening often and occasionally the crashed project will not load again. I have had to re-create projects in a new file using ‘File > Import > Tracks from Project…’. However it just happens again on the new project.
This does not happen if I open the project in Cubase Pro 12.
If I AudioWarp edit the grouped files in Cubase 12 (which doesn’t crash) and then re-open in 13, I cannot render the grouped AudioWarped tracks with ‘Bounce Selection’. It stalls after 5 or 6 seconds then a dialogue box pops up saying:
There was a file error during bounce!
The function had to be canceled!
When I click OK, Cubase just hangs indefinitley and I have to force quit - no crash report is generated. Again, this does not happen in Cubase 12.
In one project I did manage to get a small section of audio (2 tracks, 20 seconds) to render with ‘Bounce Selection’ without crashing. However, there was a fade at the end which does not get rendered - the audio within the file is truncated to the start of the fade.
This whole Phase-Coherant AudioWarp feature seems broken in 13. I have an open ticket with Steinberg about this, but last time I made a support request it took 21 days to get a basic reply, so I don’t hold out much hope.
I use an Apple Silicon Mac with Ventura OS, all plugins updated regularly and it happens both natively and under Rosetta 2. I have tried with my Prefs on, off and deleted.
1 Like
OK, so I have had a reply from Steinberg Support (it took 18 days) and, so far, things seem fixed. If it helps anyone else here’s a copy of their reply…
If you have not already done it, I suggest downloading the latest Cubase Pro 13.0.20 update, which is available by opening the Steinberg Download Assistant
(I already had 13.0.20 installed so this can’t be the solution)
You should also try to change the hard disc location where the project is saved.
(I was working from a reliable external TB3 drive that had not given me any trouble previously)
You should reset your program preferences by generating a new preferences folder.
In order to do so you must rename the folder mentioned below. Note that since Mac OS X 10.7.x the user library is hidden. To access it, please click on the “Go” menu in the menu bar of the Finder. When the “Go” drop down menu appears, you need to press and hold the key “alt” on your keyboard which adds the “Library” entry to the menu.
Now please rename
“/Users//Library/Preferences/Cubase 13”
to
“/Users//Library/Preferences/x_Cubase 13”
Important: If you find folders of previous program versions, make sure to hide or remove them too.
Preferences that have taken a lot of time to configure - the key commands for instance - can be copied from the inactive folder to the newly created active preferences folder at a later point.
More details on the preferences can be found here:
https://helpcenter.steinberg.de/hc/en-us/articles/115000245510-Preferences-of-Cubase-and-Nuendo
Please let me know if you need Steinberg Technical Support’s assistance again.
Best Regards
Steinberg Technical Support Representative
Now I can’t be sure which of the above fixed the problems, but one thing I should have guessed was that my previous Cubase installs (pro 11 and pro 12) were being accessed for preferences when I removed the Cubase 13 folder. So maybe it was that all along.
I have to say though that I was having no problems doing the same things in Cubase pro 12. Could it be that simply allowing new installs to access older version prefs files is a bad idea? Moving forward I will create new, clean prefs on upgrade installs and then manually copy my key commands etc. back into the appropriate folders.
Following on from my last post, I have had further communication with Steinberg Tech Support where I asked about the changing of hard drive location.
It would appear that there are some issues with exFAT formatted drives and audio…
Concerning of the hard drive, the problem is still being investigated. It seems there are some troubles when audio is exported directly to exFAT-formatted disks.
This seems to be the case with macOS 14 in particular. Was it your case?
If your hard drive is not exFAT-formatted, it probably was a preference’s conflict.
The external TB drive I use is APFS formatted, so, for me at least, it’s looking more like it was corrupted pref files. For what it’s worth I am using Mac OS Ventura 13.6.3 (on Apple Silicon).
I remember many years ago (pre Big Sur) using an app designed to zap prefs for various programs like Final Cut, Logic, Premier etc. if things started to go sideways. Moving forward, I’ll probably refresh Cubase’s prefs once in a while and save backups of my key commands and customisations as it’s a simple 5 minute job to do.
On a side note: Since deleting and re-creating my prefs the whole application seems more responsive and solid. My custom colour scheme inherited from generations of Cubase installs, that frankly looked horrendous in 13, is also gone. Cubase 13 with the default settings is now easier in the eyes and I’m starting to like it.