RAM Question....
Home > Home Recording Forum > Computers & Software > RAM Question....
Posted on Jun 21, 2008 06:32 pm
CynicEidolon
I tune down down...
Member Since: Jun 11, 2007
It's been awhile. :(
Do you guys think that 2gb 533hz of RAM would be enough for 16 simultaneous inputs @88.2khz? It's on a Pent. M 1.8ghz processor in a laptop.
[ Back to Top ]
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jun 21, 2008 06:52 pm At that sample rate it might not be. If you drop down to 48khz it might be. Recording at that high of a sample rate is probably not needed in most cases.
But you don't say what interface you are going to try using 16 inputs from, that might help to know that as well.
CptTrippsCzar of Turd PolishMember
Since: Jun 20, 2006
Jun 22, 2008 01:01 am I think the processor and Ram would both be limiting factors honestly.
I'm running a core 2 at 2.13Ghz with 3GB 667Mhz ram, I tracked 8 simultaneous inputs at 96 and would say I was near the max. I even had to start raising my buffers when adding in all the guitars\bass\vox due to clicks n pops. They were low enough to not have any audible latency, but when applying effects and locking tracks became a requirement it was somewhat painfull and much slower progress.
I will not do that again and stick with 48Khz because honestly, I could not tell the difference when it was mixed down to CD.
mclir9www.witchsmark.comMember
Since: Aug 13, 2006
Jun 23, 2008 07:57 am The PC I use for recording is a 2.5Gig Athlon with 2Gb Ram, and I have problems at around 8-10 tracks where Sonar will Dropout, but this is only when Mixing and I start adding effects to my individual tracks. Someone in these forums taught me how to Freeze my tracks that are not being worked with, and that remedied my problem completely.
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jun 23, 2008 09:24 pm That was probably me. And yes, if you can freeze some tracks, especially those with heavy DSP processor's on them that will really help things out.
Jun 24, 2008 11:34 am I see. I'm using a FireStudio and a DigiMax FS.
We are going to mix in 88.2 so we can have a DVD audio mix of our EP. And if we are needing to mix to 44.1 it's an even division. I read somewhere that it's better to down sample with a rate that is divisible and it's not near as lossy(?).
I've seen that Freeze track option but never learned how or why to use it. I will look into it. I do have my PC stripped down. Windows running at minimum. Processes down to 15 or 16 I believe. So, I am getting the most out of PC just scared cause I'm having a RAM issue right now that's causing audio drops. That's why I'm upgrading to 2gb.
Also, I'll be using external effect mostly so, I will be saving some DSP there.
CptTrippsCzar of Turd PolishMember
Since: Jun 20, 2006
Jun 24, 2008 01:04 pm Freezing is a way to free up your CPU. On my snare I will run EQ, gate it, comp it and then run a little verb. This can get CPU intensive especially when you apply this same process to the toms and kick. Freezing it basically writes a new wav file with the FX applied and then uses that for playback. It does not touch the original wav and is necessity once you start getting into high track counts with lots of plugins.
Also, even with 2GB ram I think that 1.8Ghz Pentium M might start struggling with 16 tracks at once. Never know until you try though :)
I have never heard of this cut in half rule being applied to audio. I would be curious to read on it if you have some links.
BeerHunterwww.TheLondonProject.caMember
Since: Feb 07, 2005
Jun 24, 2008 01:11 pm For me freezing is an absolute *must* otherwise my machine will run like crap during high track counts.
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jun 24, 2008 09:07 pm Even with my new box I will still use the freeze function. Even if it is a small project, if it includes software synthes I will still use it.
Jun 26, 2008 11:48 am I'll see if I can find it for you, Tripps. Or it might have been in one of my books. But, it has to do with the re graphing of the samples. It's easier to cut them in half than, trying to figure which ones to take and not take. So, in essence, there are less word errors and less Noize(:P). Also, I think it allows for the same headroom of that higher sample rate, once it's converted down as well.
I COULD BE WRONG. This is just from memory.
CptTrippsCzar of Turd PolishMember
Since: Jun 20, 2006
Jun 26, 2008 12:43 pm Very interesting, I guess it makes sense in the same way you get interpolation when trying to make an LCD screen do less than it's native resolution as pixels overlap.
Less Noize, I see what you did there :) When you accomplish this, I would be curious to see if you actually notice the difference. I may have to try just for giggles.
Jun 26, 2008 04:58 pm It is in one of my books. I imagine it is here on the net somewhere but, I can't find a link or site.
Jul 05, 2008 06:17 am Just a bit of a noob question...what is freezing and how is it done?
Jul 05, 2008 06:19 am Also what the hell is buffer size and whats so good about sample rates? Mine is just at 44100 or something like that
SFX_NXMember
Since: Jan 17, 2008
Jul 05, 2008 02:14 pm Freezing makes a mixdown of the audio track with the effects so that it lowers your CPU usage. In Sonar, I just right-click the track and click freeze track. What software are you using?
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jul 05, 2008 02:25 pm Freezing is when you have a lot of audio tracks built up. Especially software synth tracks. It simply converts the software synth tracks to an audio track and stops the software synths engine from having to run, which frees up a lot of system resources. It was designed by Cakewalk because a lot of the software synths had gotten to be such resource hogs they needed to find a way to make things run smoother.
The audio streaming buffers allow a certain amount of data to be processed ahead of time eliminate latency in the audio. Too little and you can get pops and crackles if your system is under powered. Too much and it will cause a ot of latency when recording tracks. But using a higher buffer during mix down is good since there is no latency noticed if you are not recording new tracks.
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jul 05, 2008 02:27 pm OH ya, and sample rate is the amount of data that is recorded into the track itself.
Just for reference standard CD audio is 16 bit and 44100 khz. So you will be fine unless you need the higher sample rate for very precise audio cutting and such.
Jul 07, 2008 11:17 am Noize.
You're a good man!
Jul 07, 2008 06:47 pm Yeah Noize youve answered so many of my questions, keep up the good work...but heres another. How do I freeze a track in Cubase SX3?
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jul 07, 2008 10:52 pm I'm not a Cubase user but I believe in Cubase you simply right click on the track itself and a menu should come up with the freeze option in it. I think there are a few Cubase users here that can confirm that or steer you in the right direction. But I know in Sonar it is a simple right click as well as being in the normal tools menu.
