I’m now getting repetitive hangs when exporting audio - regardless of project, format (.wav or .mp3) or destination drive. It doesn’t happen every time - for some projects, say 1 in 3 times it will hang on the same project.
One project won’t export at all.
Windows is fully up to date as are audio and video drivers - nothing has changed in my system other than the Cubase 14.0.20 update - all the projects exported fine on Cubase 14.0.10.
The NVMe disk has 1TB free space.
Full spec in my bio.
If I disable preferences on start up - it still hangs.
No Crash dump files are created.
It does create a new audio file with correct name in the correct folder but of 0Mb file size.
I’ve screengrabbed the audio export dialogue box - you can see it doesn’t load correctly. I also included the Task manager window, which shows that Cubase is active and still using CPU. I have tried leaving the export for longer than it would take to export the track - just in case the track was exporting and it was just an error with the UI. But it just stays as shown in the screen shot.
Any ideas on what else I can do to troubleshoot this?
I haven’t had any issues of this sort to date (I’m on Windows 10, though, and with a lesser-spec’d system built back in 2014 and have rendered both CD quality WAV files and MP3 files at 320 kbps and 192 kbps). To narrow this down, I think you’ll need to use the stock instructions Martin Jirsak gives for generating a DMP file for analysis (guessing they are still the same for Windows 11) when it is in that hung state:
Use Microsoft ProcDump utility to generate a DMP file, please.
Please download ProcDump64 1 from Microsoft (~650kB) and extract the archive to a local folder on your harddisk.
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users\Downloads\Procdump
Note: the dmp file will be written into that folder.
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behavior (see next step).
Launch procdump64 via Command Prompt:
Cubase 14:
procdump64 -e -h -t Cubase14
One thing I’d also wonder about is if you’re using the real time export or not. (I don’t use that, but I wonder what happens in the case where it can’t keep up in real time. I’d guess just artifacts in the audio file rather than a hang, though.)
So…the project that won’t export at all without hanging…I tried it in Cubase 13 and it exports fine…every time.
Only problem is that the project uses the new Drum Machine and lot’s of Modulators, and a touch of Autofilter - which obviously didn’t exist in C13.
This makes me think that the problem isn’t in any VSTi or VST FX plugins that I’m using as they are all identical for C13 as they are in C14.0.20? (I’m using a lot of UAD and Arturia plug-ins)
Nope - I thought that was the problem initially but I have the same issue going direct into a regular folder on my C: or D: drives which are normal drives with normal folders and aren’t cloud synced.
If I leave any of these running the export hangs.
The first one is modulating an Arturia FX called EFx FRAGMENTS which is a granular delay.
The second group of three are modulating 2 macros and one filter envelope on an Arturia instrument called Augmented Brass.
Handily you can’t Freeze tracks with Modulators so for now I will just Render in Place.
Would be good to know if there is a fix/workaround for this?
I’m surprised rendering in place would not have the same issue as I’d think it would use the same underlying functions.
FWIW, I haven’t even tried using modulators to date, so, if this is the cause, that could explain why I haven’t seen any issues in exporting. But this also comes back to what I suggested above about trying to capture the DMP file when the problem is happening in order to help Steinberg locate and fix the problem (assuming it is actually with the modulators, as opposed to how some specific plugin reacts to how the modulators are manipulating that plugin – but the DMP file should give a clue to that since the hang would either be in the plugin or in Cubase itself).
Hi - yes, sorry, I wasn’t ignoring your advice, just kind of had a hunch that it was something above and beyond plug-ins or OS, as it had all worked fine in Cubase 14.0.10.
If I have a mo, I’ll try procdump. In the meantime, hopefully someone at Steinberg reads these threads and might be able to do their own testing to re-create the problem?
Thanks
No worries on that. The reason I mentioned it, though, is because it could still be plugin-related, in particular if it is something in the way the modulators are driving one of the Arturia plugins. So it could be something that Steinberg wouldn’t be able to recreate without further information, which the DMP file could provide. And it’s not like Cubase itself has any equivalents for those two plugins, with the Fragments one being especially unique. (I’ve only played with that one a little, though I’ve used Augmented Brass in at least one of my recordings.)
Hi, same thing happening here (and totally unseen before). Cubase 14.0.20, windows update, no new plugins installed. Project that I exported normally before are now causing cubase to hang.
Did anybody found some solution / root cause to this?
Same issue. Massive use of the modulators seems to be the culprit. Thought I might be the only one as some of the things I try to do are absolutely NUTS, but alas I am not the only one.
Hi, my project only has 4 modulators (can’t really say it’s a massive use). Using Real time export seems to work. I’m doing some other tests (this may become painful in large stems export, quite usual to me)
Cubase 14.0.20
Windows 11 Pro 24H2
Ryzen 9600X
Motu M4 Audio Interface
32GB DDR5 6000MTs Cl30 RAM
4TB Cubase 990 Pro NVME
Asus B650-I MoBo
Radeon RX 9070 XT
Honestly, wondering if will be fixed or if I should attempt a refund. 2 modulators total on the file, both pointed at two different samples in GA SE5 just panning according to a stepper.
Hello and welcome.
This bug is on Steinberg’s to do list. See if you can do the real time workaround for now.
I think asking for a refund would be a somewhat hastily decision.
Thank you so much guys - have the same bug with .20 and it was driving me nuts. Had completely messed up my ability to collaborate with other producers.
