From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Testing/forcing XRUN
Date: Fri, 08 Jun 2007 17:59:05 +1200 [thread overview]
Message-ID: <200706081759.06021.linux@audioscience.com> (raw)
Hi,
I want to test my driver behaviour when an xrun happens.
I have tried using aplay/arecord, and suspending (ctrl-Z) them while
playing/recording but this doesn't have the desired effect. (I don't see my
driver code detecting an xrun). Instead I see a trigger-stop command to the
driver.
The apps do report an overrun when they are restarted though.
Can anyone answer these:
1) Is this a valid way to simulate an xrun due to application not keeping up?
1.1) If not, what is? Do I have to write an app that deliberately starves the
streams?
2) Where is the xrun being detected if my driver doesnt see it? Where does
the trigger-stop command come from when I suspend the app?
thanks
Eliot Blennerhassett
AudioScience Inc.
next reply other threads:[~2007-06-08 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 5:59 Eliot Blennerhassett [this message]
2007-06-08 7:19 ` Testing/forcing XRUN Nobin Mathew
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=200706081759.06021.linux@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).