Buying new computer, few short questions
Home > Home Recording Forum > Gear Gab > Buying new computer, few short questions
Posted on Dec 18, 2009 10:11 am
Fragile
Member Since: Sep 30, 2009
Alright, so which system resources should i be most concerned about here? Occasionally on my lappy (2 gigs RAM, 2ghz dual core AMD) there's some VERY aggravating constant clicking. usually i can just turn the ASIO to the highest latency and it fixes it. But then if i need to record another part its a pain in the butt. I don't wanna open a second project just to record one little guitar track you know?
Also with my recent addition to the family, QL Goliath, and S2.0 i'm killing my lappy with those VSTi's.
I'm building my own pc. So far i'm thinking a 2.3 ghz quad core AMD. 4 gigs RAM. Anything i should be concerned about there? Any other recommendations?
[ Back to Top ]
Dematrixhttp://www.reverbnation.com/2ndgMember
Since: Nov 27, 2007
Dec 18, 2009 10:26 am try this. when you record dont have any FX on anything and that'll save you heaps of memory. by this i mean just wait till youve recorded everything so you can then wack the Buffers down.
also, when your happy with your drum tracks bounce them to audio. your using SD2 yeah? use the bounce function and then import them into your project.
im using similar specs to you computer wise, in fact i upgraded to 4 gig ram and that dint do a hell of alot to be honest.
what you need if and when you get another compy is a kick aarse cpu. ram doesnt do much more if your cpu cant handle it.
Dec 18, 2009 12:47 pm Ya, i've been doing that. It deffinately helps. But its hard to record a song with pod farm guitars and turning pod farm off :[ major pain.
What i ran into last project i did was i'd record it and keep the effects as low as i could while tracking. Then once i started mixing i started adding delay into the signal, reverbs, chorus etc. I also froze S2.0 which took most of the load off.
Which worked fine, had to move the latency up at some point but it was all good. Then i decided i wanted to mix the drums (hadn't really done that, just sorta bounced it right away). Well when i did that everything went crazy. I guess my cpu maxed out or something. I had to just exit the program and come back to my last save point b.c. i had to unload way more stuff than just freezing the drums again. It was like once it maxed out i had to bring it back down to 50% to get the noises to stop.
And to make things worse, even later i decided to track one more guitar part. I decided to keep the latency high and just play the guitar without monitering it, just used the unpluged sound to keep me in time lol.
But anyway, thanks for the advice. My ASIO time usage bar is always the one thats full. The disk catch usage rarely even gets a spike of activity. I didn't really know what that meant but I'll make sure i get a kick butt CPU to handle it.
CptTrippsCzar of Turd PolishMember
Since: Jun 20, 2006
Dec 18, 2009 01:05 pm Lock em down (Freeze tracks) so your DAW does not have to process the effects.
Once you start using PODFarm, SVTi, Reverbs and Delays any computer will start poppin and clicking once the track count gets high enough.
I'm not saying a new PC won't help immensely, but freezing tracks is pretty common stuff in any DAW to save resources.
Dec 18, 2009 01:58 pm Gotcha. I'll deffinately do that more from now on. I'm gonna try geting a pretty kick butt processor though. I want this puppy to LAST. I do not wanna be in the market for a new PC for a long, long time.
