Firing up Cubase on this day, and it is so nice to be reminded that daylight savings are on. Every 6 months Cubase reminds me, without a fail. I guess I should be thankful, it is an undocumented, hidden feature - daylight savings reminder.
So I fired it up today… scan, scan, crash, restart, scan, scan, crash, restart, scan…
Would be nice if Cubase didn’t crash while scanning plugins. If it really must rescan them all every six months, at least make it so that it scans from beginning to end without the need to babysit it, and restart it again and again. It is really frustrating to let it do the scan unatended, and then come back to see that it didn’t do much, because it crashed.
Glad (?) to know it’s not just my Cubase that crashes during rescan. It could be worse, about 20% of my NI patches are missing which rescanning doesn’t find (not clockchange related) I just can’t be bothered to reinstall 300Gb of content to fix it!
was ready too,
started cubase last night as soon as i got back from a gig and by this morning - all done
one plugin stalled though, one of those melda ones. i think i read somewhere that this scanning business is more of a windows thing?
Well, Reaper rescanned all plugins too, so it seems Cubase is not the only DAW rescanning. But, guess what, Reaper didn’t crash, although scanning exactly the same plugins. So maybe plugins are buggy, what do I know, but Reaper seems to deal with them just fine, while Cubase crashes again and again. I wonder how a Reaper developer can code better VST scanning than the inventors of VST… it is truly a wonder.
Reaper crashed so many times on me, that I gave up.
Cubase took additional 15 seconds to start up, without any issue’s
If Cubase would crash, I would definitely try to find the problematic plugin, and update.
Or find a later stable version, plugin alliance comes to mind.
After starting to rescan, Cubase stopped on a number of plug ins, noting that they are up to date software such as BFD. I had to crash out several times until the “bad” plugs got blacklisted, then Cubase opened.
However, my projects wouldn’t load, all seizing on loading mix console. I ran a system restore to 23rd March, then tried again, now all is fine.
Why do we have to suffer such stress twice a year, is there a compelling reason?
If Cubase wants to scan, why can’t it complete the scan and then present us with a list and tickboxes, or something similar. Success, Retry, Fail, Blacklist and so on. having to resort to task Manager to sort the software crashes is horrible.
Thanks Peakae, I have turned daylight saving and to manual clock. The clock had failed to update correctly anyway! Let’s see what happens next time.
Nonsense. Why would windows care about the state of VSTs? Clock change is clearly used by Cubase and Protools as a convenient trigger to perform a plugin scan. It also means we as consumers know when its going to happen. I suspect the enforced scan was some anti-piracy measure way back when.
The same thing happened to me. I couldn’t figure out why Cubase was re-scanning my plugins given that I didn’t install anything new. Thanks for posting – you saved me from wasting a lot of diagnosis time.
Are you sure this will prevent the problem? The implication is that it’s not the changing of the time in the Windows clock, but rather the automatic process of changing it. Why would that matter? It seems bizare.