5 tracks =????RAM

  • Thread starter Thread starter sae
  • Start date Start date
S

sae

New member
How much ram would I need to record 4 tracks simulaniously and play back one track?

I have a duron 600 running windows 2000 and ntrack 2.3 (latest version of 2.x)

I have an sb live and an sb 128

Please don't mock my soundcards...I just want to know how much ram I would need to do this. I have 160mb ram...is that enough, or is that pushing it?

thanks in advance for your answers
 
n-Track, like all multitrackers, is a direct-to-disk application. It does not load tracks into memory (other than buffering).

You only need enough memory to run n-Track, which isn't that much.

On a Windows95,98,98SE,ME, or NT4 machine, 128MB is doable.

On a Windows 2000/XP, 128 is a bare minimum with 160-256MB being more realistic.

On your system, assuming you have a decent motherboard and hard drive, you should be able to do 20+ 16bit tracks.

Slackmaster 2000
 
If it is direct to disk....why does it some times studder even if the hard drive is not working for any other application?
 
There are thousands of reasons!

1) Your n-Track buffer settings are not high enough.

2) It could be an IRQ sharing issue.

3) Your CPU could be choking (unlikely).

4) You could have other applications either accessing the disk, even for brief moments, or they're accessing the bus or stealing CPU cycles.

5) You could have a naughty device driver. The SBLive can be difficult to setup with another soundcard in the same system.

You just asked *the* question :) Your problem is not a lack of memory. Make sure you're not starting up any unnecessary processes at startup. Increase your n-Track buffers. Update your device drivers. Use device manager to determine the resources your various devices are using, and look for potential problems, like both of your soundcards on the same IRQ. Decrease the number of DX/VST effects you're using.

Slackmaster 2000
 
What does the buffer buffer than? and where does it buffer if it doesn't buffer in ram?
 
Of course it's in RAM. The size of the buffer is very small.

Slackmaster 2000
 
You must log in or register to reply here.
Back
Top