I have recently upgraded from 12 Pro to 15 Pro but I’m finding the loading and unloading times very slow (particularly unloading). I am working on a reasonably large orchestral project (BBC SO, mostly MIDI but some audio tracks) and when I close the project it can take up to five minutes between closing the project and the wretched Hub being displayed (you might have deduced that I find the Hub about as much use as an ashtray on a motorcycle).
Is there anything I can do to speed up the closing process? To my tiny brain (I was a software developer for 30 years before recent retirement), once the project is saved why is there extra housekeeping to do? I haven’t experienced this nonsense with any other program.
Hi Zwa,
I also use BBC SO pro and Steinebrg Iconica Opus.
Loaded files can be 50/60 gb and that takes some time to load and unload.
Depending on how fast your drives and memory are.
one thing you can do to diagnose this is to install Process Monitor Process Monitor - Sysinternals | Microsoft Learn and set the filter to: Process name contains cubase. This will show you all the file access during this time. Also if it’s caused by a plugin then you can see which plugin in the Stack context menu
Thank you both. I’ve installed and am running Process Monitor with the filter as suggested. However, the window is showing about 800,000 events (and counting) so I can’t see any way to figure out where, if anything, the bottleneck is occurring.
I had exactly the same problem – until half an hour ago! The big difference was that I only had four stems of audio and three of MIDI (programmed drums). Even so, it took at least five minutes to close down this and similar projects. It turned out that one stem had a send containing an outdated and no longer existing Izotope plugin – I’d bought and installed the upgrade on the other stems but forgotten to remove the old version from this particular send. Once I’d deleted it, the shutdown time was reduced to two or three seconds. The clue was a warning when I loaded the project – I was just a bit slow to find the culprit. Hope this helps you or someone else! Good luck!
How exactly did you find out? Did you open the vstscannermaster file to check the time it takes to load each plugin?
In case somebody is asking themselves where to find this file:
On windows go to C:\Users\Username\AppData\Roaming\Steinberg and use a search with the keyword „VSTScannermaster“. You can also watch them load in realtime, no need to wait. This way you’ll be a live witness. This feature was first introduced with Cubase 14 if I am not mistaken (maybe Cubase 15, it’s not in Cubase 13 and earlier versions).
No, Reco29, I didn’t use vstscannermaster. The original iZotope plugin had slowed up loading and unloading considerably, and “a little bird” recently informed me that some iZotope apps are notorious for this. I use some iZotope apps (!), so it was just a matter of carefully examining each stem visually and looking out for any irregularities.
This will give you some different views of the data. Try sorting by Total Events to see the files being read or written to the most, or switch to the folder view, which will show if there are many files in a subdirectory that are being read or written
