Using Windows 10, Cubase 14(0.32). Curious if others are having hang on project load issues - if I disable 3rd party plugins, it does open successfully, but it is not the same channel or plugin where the hang happens (ie. will sometimes make it past a third party plugin, but other times it hangs on one). It happens on a simple project as well. It leads me to believe either one of the recent Cubase 14 updates has introduced something inconsistent with loading 3rd party plug ins or a recent Windows 10 update has influenced things in some way. This is a relatively recent problem for me (have been successfully using C14 since it came out).
Others encountering this? Workarounds? Revert back a couple updates safely? Fix in the works?
Thanks
Thomas
Hi,
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
-
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
-
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 behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase:
procdump64 -e -h -t Cubase
Nuendo:
procdump64 -e -h -t Nuendo
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
Thank you Martin - here is the link to the dump file - I received a number of dialog boxes, however, that various plug ins can’t run in the presence of a debugger, so I am not sure the behaviour we are trying to replicate is the same: https://www.dropbox.com/scl/fi/1t4l29450at4rw6awiami/Cubase14.exe_250630_094331.dmp?rlkey=pt4s3mhh0mstsv6e813h3kme8&st=lohk1qe1&dl=0
Curious if any updates on this or workarounds?
This appears to be hanging in MelodyneCore-5.4.2.006.dll
Thanks Paul - interesting - that is still the latest version of Melodyne and I haven’t updated it in some time. Perhaps a recent Cubase 14 change or Windows Update influencing it (?)
It seems to not be consistent with which channel / 3rd party plug-in either - it sometimes makes it past this channel.
The hang appears to be entirely within Melodyne
STACK_TEXT:
ntdll!NtWaitForSingleObject+0x14
KERNELBASE!WaitForSingleObjectEx+0x8e
MelodyneCore_5_4_2_006+0x16f41bf
<Unloaded_wwfCD76.tmp>+0x17e3bc0
<Unloaded_wwfCD76.tmp>+0x2675420
There are lots of wwXYZ.tmp dlls listed in the .dmp file but with no information about what they are. You’ve mentioned that some of the plugins complain about being debugged, which usually means that they are protected by an obfuscation layer such as Themida. This may be causing problems here.
You may be able to get a more accurate .dmp file if you launch Cubase first, and then when you get a hang, run the procdump script. If the process is hanging then it probably won’t be able to warn about not being able to be debugged.
I will give it a go this weekend - thank you. As mentioned before - this issue is very recent - the changes were updating to the most recent C14 and potentially some windows updates. I am tempted to roll back C14 to the previous update, but apprehensive about causing other issues.