MC Nice Andrew Posted March 17, 2011 Report Share Posted March 17, 2011 Hi!Anyone know a fair bit about Cubase? Was working on a session; admittedly with a good number of plug ins and vsts, though it running smoothly. Now when i try to open the session it doesn'y get past the mixer and crashes. All my other CPU eating sessions open fine - any ideas?Ta! Quote Link to comment Share on other sites More sharing options...
James Broonbreed Posted March 20, 2011 Report Share Posted March 20, 2011 It's weird that you're other memory heavy projects work fine. If it weren't for this, It'd definiftely sound like a shortage of memory. Are all your reverbs etc. on aux channels rather than a different one for each track? I'm not sure of your ability with Cubase, but a lot of less experienced users tend to fill their sessions up with unnecessary reverbs and delays etc.That's probably no help whatsoever. Oh well. Quote Link to comment Share on other sites More sharing options...
MC Nice Andrew Posted March 25, 2011 Author Report Share Posted March 25, 2011 Thanks for the response; think im gonna try a reinstall. Quote Link to comment Share on other sites More sharing options...
Preid Posted March 27, 2011 Report Share Posted March 27, 2011 Im probably too late here but Ill put this out there.My DAW has a feature that if something like this happens, you can open a project back up with all the vst's, controllers and such alike disabled. I believe its simply a case of holding shift as you start the program. Im not sure if Cubase has this feature, probably does.Hope you get it sorted. Quote Link to comment Share on other sites More sharing options...
MC Nice Andrew Posted March 31, 2011 Author Report Share Posted March 31, 2011 Nice! I'll try that when I get in. Cheers fella. Quote Link to comment Share on other sites More sharing options...
emergency72 Posted April 3, 2011 Report Share Posted April 3, 2011 This feature isn't in Cubase...its always a good idea to save your projects with plug ins disabled for this reason. But you can get around it by opening the cubase log file (cubaseSX.log or something) and finding which plug in was causing the problem. Uninstall plug in, open file, disable the plug in, save it and then reinstall plug in. Should be able to get it back from there. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.