From: "Robert Brückmann" <robert.brueckmann@stud.tu-ilmenau.de>
To: alsa-devel@lists.sourceforge.net
Subject: latency timer
Date: Tue, 26 Feb 2002 23:06:38 +0100 [thread overview]
Message-ID: <002601c1bf11$e23a37e0$0300a8c0@wgilmenau> (raw)
Hi!
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 --device="rme9652_dual32" --format=S_32LE --rate=44100 --channels=48
rme9652_dual_32 is a device defined in ~/.asoundrc.
I found out that increasing the latency timer in my BIOS helped out (I
increased it from 0x20 to 0x30), but if the computer gets too much xruns
after another, it locks.
Does anyone know, what the latency timer actually does? It affected the
performance of the cards rapdily. But what is the disadvantage of increasing
that value? Should I set it to maximum (0x80)?
Thanks,
Robert
BTW: Might the low latency check help with my problem?
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2002-02-26 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 22:06 Robert Brückmann [this message]
2002-02-26 22:27 ` latency timer Paul Davis
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='002601c1bf11$e23a37e0$0300a8c0@wgilmenau' \
--to=robert.brueckmann@stud.tu-ilmenau.de \
--cc=alsa-devel@lists.sourceforge.net \
/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.