recording wavs
Tim Wunder
tim
Mon May 17 11:54:14 PDT 2004
On Monday 29 September 2003 6:41 am, someone claiming to be Squabsy wrote:
> On Sat, 27 Sep 2003 00:20:08 +0100, "Squabsy" <squabsy at lycos.co.uk> said:
> > OK with ulimit -a I get
> > Rich at linux:~> ulimit -a
> > core file size (blocks, -c) 0
> > data seg size (kbytes, -d) unlimited
> > file size (blocks, -f) unlimited
> > max locked memory (kbytes, -l) unlimited
> > max memory size (kbytes, -m) unlimited
> > open files (-n) 1024
> > pipe size (512 bytes, -p) 8
> > stack size (kbytes, -s) unlimited
> > cpu time (seconds, -t) unlimited
> > max user processes (-u) 2047
> > virtual memory (kbytes, -v) unlimited
> > Rich at linux:~>
>
> In a cynical attempt to get back to the top of the list I'm replying too
> my own post.
>
> I still don't understand why any of the above limits would create a
> problem when I'm trying to record a wav file that would be 500k at most.
>
> I have updated to a newer Kernal but it doesn't seem to have made any
> differance.
>
> How would I go about increasing the file size limit ?
> Why does it need so much space to create a wav in linux.
>
> Appolgies for my persistance.
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 3071
virtual memory (kbytes, -v) unlimited
You're limits don't look all that different from mine, 'cept you have
unlimited stack size (lucky devil), so I don't think limits is your problem.
I'd lean toward sound card driver issues. Do you have another sound card you
could try?
Regards,
Tim
--
RedHat 8.0 Kernel 2.4.20-20.8, KDE 3.1.3, Xfree86 4.2.1
7:05am up 1 day, 23:29, 1 user, load average: 0.25, 0.24, 0.10
It's what you learn after you know it all that counts
More information about the Linux-users
mailing list