From: Paul Davis <pbd@Op.Net>
To: Robert Br ckmann <robert.brueckmann@stud.tu-ilmenau.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: latency timer
Date: Tue, 26 Feb 2002 17:27:01 -0500 [thread overview]
Message-ID: <200202262227.RAA00414@renoir.op.net> (raw)
In-Reply-To: Your message of "Tue, 26 Feb 2002 23:06:38 +0100." <002601c1bf11$e23a37e0$0300a8c0@wgilmenau>
>I wanted to use two RME hammerfalls to record 48 channels of audio via adat,
>do some signal processing and play them back again. But I experienced a very
>poor performance of my computer (dual pentium III 1.3GHz, 512MB RAM). It
>wasn't even able to record 48 channels without xruns.
>
>I modified aplay/arecord that it plays/records more than 32 channels (btw:
>why did the developers insert such a silly check which didn't allow more
>than 32 channels???), but arecord gave many xruns while recording (aplay
>worked fine):
arecord *CANNOT* do this. it is not designed to do serious multitrack
recording. you will never get it to work unless you have a disk
subsystem with unbelievable seek and sustained i/o performance. if
arecord could do this, the work that i've put into ardour over the
last couple of years would be (partly) a waste of time. you can't
stream that much data to disk in real time without a multithreaded
design, which arecord does not have.
i doubt that arecord could go much above 12 channels with its
single-threaded design, certainly if using 32 bit samples.
>BTW: Might the low latency check help with my problem?
i presume you are referring to the low latency patch. it is only of
critical if you are using low period sizes, which for recording 48
tracks is not the optimal setting. however, it can help any audio
program, even xmms and the like.
--p
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-02-26 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 22:06 latency timer Robert Brückmann
2002-02-26 22:27 ` Paul Davis [this message]
2002-02-26 23:01 ` Robert Brückmann
2002-02-26 23:14 ` Paul Davis
2002-02-27 7:45 ` Robert Brückmann
2002-02-27 15:13 ` Paul Davis
2002-02-26 23:18 ` Paul Davis
2002-02-27 7:48 ` Robert Brückmann
2002-02-27 14:54 ` Paul Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202262227.RAA00414@renoir.op.net \
--to=pbd@op.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=robert.brueckmann@stud.tu-ilmenau.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.