recording wavs

[Squabsy]

On 18 Sep 2003 17:54:58 -0400, "burns" <linux at burnsmacdonald.com> said:
> On Thu, 2003-09-18 at 16:44, Net Llama! wrote:
> 
> > 
> > yes, that's the load at the instant that you ran the command.  were you
> > attempting to encode a wav when you ran that?  if so, then the load
> > appears to be fine.  you might want to just run 'top' the entire time to
> > see what is going on across the board (cpu, memory, load).
> 
> It is at all possible that this is a memory issue? With a file that big,
> if your audio application tries to fit it all in memory, and you only
> have 256MB and a correspondingly small swap file, then it may be running
> out and truncating the file. I know with graphics files this can
> happen... just a thought, YMMV
> 

Having spent the weekend playing around with it  and using TOP to see
what's going on I have come to the conclusion that all the Linux
softwares I have been trying are indeed storing the file up in RAM then
in my swap partition then hanging when it gets full.
The Windows software I use on the other hand (CDWAVE) writes the file
straight to disk with no temporary files.

I have 256k ram and a swap partition of 512mb I can't seem to be able to
(nor do I think it's a particularly good idea) increase the size of my
swap partition.

Is the only way I can have more success then increase the RAM ? or is
there a Linux program that writes straight to disk ?
Even if I click the straight to disk option in audacity it still fills my
ram/swap partition



-- 
Squabsy The List Crawler
Using Opera, The Bat, K-meleon, or Becky.
Right Now Using Fastmail when I should be working