my Cubase rescans the plug-ins every freaking time I load it, and no, I haven't added any new ones..
judging from the forums though, it only seems to be affecting some of us
Same here, and on an Athlon XP+ 1600 w. 1Gb ram it takes about 45 seconds for Cubase to check aboutbduffy wrote: Good point; I didn't mention that. Cubase SX 2.2
When did you first notice the slowdown? Try unloading any new plugins that you got just before the slowdown. Move them to another folder. Then see if SX speeds up again. If it does, move the plugs back into the vsti folder one by one. That might help isolate the problem.The plugs are to blame largely,
I'm afraid I couldn't use "No Common VST Folder" as I would have only my stock plugins on relaunch (it was MUCH faster though) - BUT - I did discover that I had "C:\Program Files\Steinberg\VstPlugins" listed twice in Pug-In Information, and now that I only have the one VSTPlugins directory, lauching has sped up to about 10 sec.Improv wrote:Same here, and on an Athlon XP+ 1600 w. 1Gb ram it takes about 45 seconds for Cubase to check aboutbduffy wrote: Good point; I didn't mention that. Cubase SX 2.2
200 plugs (approx.)
When did you first notice the slowdown? Try unloading any new plugins that you got just before the slowdown. Move them to another folder. Then see if SX speeds up again. If it does, move the plugs back into the vsti folder one by one. That might help isolate the problem.The plugs are to blame largely,
Edit:
I just tried something that made a big difference in Cubase loading time. Go to Devices/Plug-in Information. In the 'Shared Plug-Ins Folders'
area, click on Remove so that there are no shared folder paths listed in the drop down menu. Restart SX2, and this should make a big difference in the time it takes to check for plugins. When you start a new project, all the plugs are still listed in the F11 Vst Instruments list.
Instead of a 45 second load time as before, I now get SX2 loading in 26 seconds. Quite an improvement!
Have you actually tried this or are you just assuming that would happen? I actually did it and still have access to all plugins.bduffy wrote: I'm afraid I couldn't use "No Common VST Folder" as I would have only my stock plugins on relaunch
BUT[/b] - I did discover that I had "C:\Program Files\Steinberg\VstPlugins" listed twice in Pug-In Information, and now that I only have the one VSTPlugins directory, lauching has sped up to about 10 sec.
It really depends which synthedit plugs and who developed them. I own a few very good plugins that just happen to be developed in synthedit and give absolutely no problems: Algo Music's M42, all the HG Fortune plugs, GreenMachine guitar amp, Krakli plugs such as Yava2, and NeuroSynthPack. People are often to quick to dismiss Synthedit plugs with a blanket condemnation.as soon as I installed v1.5.x, the weird mouse stuff happened. So who knows. I'm just thinking synthedit because some of them have more choppy playback.
Yes, I tried it, and I got only the stock plugins. They're back as soon as I put the path back in...that's odd that it works for you...?Improv wrote:Have you actually tried this or are you just assuming that would happen? I actually did it and still have access to all plugins.
Oh, I never dismiss a plugin becuase it's Synthedit - it's all in the coding, AFAIK. I've bought Spectralive and Adventus, only learning later that they are Synthedit. And I love some of the cheapest, cheesiest ones. The only reason I'm suspecting anything is becuase of weirdness with some specific plugs that seem fine for most others.Improv wrote:It really depends which synthedit plugs and who developed them. I own a few very good plugins that just happen to be developed in synthedit and give absolutely no problems: Algo Music's M42, all the HG Fortune plugs, GreenMachine guitar amp, Krakli plugs such as Yava2, and NeuroSynthPack. People are often to quick to dismiss Synthedit plugs with a blanket condemnation.
I agree that Cubase takes a long time to open. It's also a lot more resource hungry to get itself open than Sonar and doesn't feel nearly as snappy and crisp as Sonar. Every sequencer seems to be somewhat different in this regard. Some people have mentioned Tracktion. My experience with it was that getting around it's interface was very sluggish, moreso than Cubase. I found myself clicking once, waiting, then clicking again on the tab for the audio settings. It would have popped open eventually from the first click, but that's how sluggish it is. The only application I have that is in the neighborhood of Cubase's resource hunger and slow loading time is Stylus RMX. The latest update has improved the CPU requirements for simply getting it open, but it still eats about 400 Megs of Ram instantly, and it still rivals Cubase with the incredibly long load time.bduffy wrote:OK, I knew some of you would take me to task for complaining about 30 seconds. You might want to open your desktop clocks and stare at the screen for 30 seconds to get a sense for it. I agree it sounds silly (like needing an abbreviation for "at"?), but when you consider that Sonar can load a fully stocked audio engine instantly, that seems more in line with the promise of immediacy of digital technology. And I think we all experience a little agitation when you just want to sit down right away, like with analog gear/instruments, and start banging out a bed - but you have to wait 30 seconds while the splash screen mocks you.
And to be even more clear: my templates don't take long to load at all, just the Audio Engine.
My only experience is with Cubase, Sonar and I've tried Logic 5.5. Wondering how long other apps' GUI's take to open, cos I like it to open FAST. Doesn't seem like to much too ask in 2005. But then again, I'm not switching from Cubase anytime soon.
Oh, and I do have roughly 540 dlls in my VSTplugin folder.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026