From: jfm3 <jfm3@ouroboros-complex.org>
To: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: vxpocket v2 full duplex latency with ALSA driver?
Date: 07 Mar 2003 15:43:55 -0500 [thread overview]
Message-ID: <1047069836.3627.42.camel@localhost.localdomain> (raw)
The ALi M5451 sound card in my laptop blows chunks in full duplex. I
have a question for vxpocket v2 + ALSA users.
Reports are that the windows driver for the vxpocket v2 yeilds high
latency when used full duplex. Is there a similar problem with the ALSA
driver? Is it really a driver problem or is it a hardware problem? What
kind of card latency is there?
--
(jfm3 2838 BCBA 93BA 3058 ED95 A42C 37DB 66D1 B43C 9FD0)
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next reply other threads:[~2003-03-07 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 20:43 jfm3 [this message]
2003-03-10 13:31 ` vxpocket v2 full duplex latency with ALSA driver? Takashi Iwai
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=1047069836.3627.42.camel@localhost.localdomain \
--to=jfm3@ouroboros-complex.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox