When I start Cubase and load a project (scoring session - large one with video files) for the first time, it takes over 11 minutes to load. I close the project and exit Cubase. Then, even after a longer time and doing other things on the computer, I start Cubase again and load the same project, it loads in about 1 minute (as it should all the time in my opinion).
Do you also experience such differences between the first and subsequent project openings?
Any thoughts on what is wrong and how to improv project’s first loading time?
I am using Cubase 12 pro running on Windows 10 OS, but it was the same with Cubase 11 pro.
Windows virus and threat protection is disabled, but just in case, as a precaution, I also have protection exclusions on the Cubase folder, as well as on the instrument library folders.
This computer is used only for audio work, so there are only Cubase and plugins/instruments installed and almost nothing else. I keep it clean.
AMD Ryzen 9 (12 cores), 128GB RAM, 2 NVMe Gen4 up to 5000 MB/s - overall a very fast machine that allows me to work on huge and complex projects.
Hi and welcome to the forum,
You can maybe try to make a DMP file during the 1st start.
Generate a DMP file and share it via Dropbox or similar service, please.
Use 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 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.
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:
procdump64 -e -h -t Cubase12
procdump64 -e -h -t Nuendo12
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 exeptions 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 similar service, please.
This is very normal if lots of samples are used with for example Kontakt. The first load is from disk, the second from the windows cache which is stored in ram, which can be 100 times faster.
To be sure have a look how much ram this project uses.
If you load it the first time, see the speed of how cubase ram rises and a second time it would be faster.
Windows will use all free ram for disk cache so with 128gb you potentially have a very large cache which will only be fully emptied on a reboot