From: Tobias Schneider <tobsnyder@gmx.de>
To: Tobias Schneider <tobsnyder@gmx.de>
Cc: Alsa-devel@alsa-project.org
Subject: Re: overrun in second capture device after stopping first capture device
Date: Fri, 29 Jan 2010 19:12:46 +0100 [thread overview]
Message-ID: <4B63251E.7080403@gmx.de> (raw)
In-Reply-To: <4B5EFAC7.6050402@gmx.de>
I am still searching what causes the problem, I now figured out that the
underruns occur because appl_ptr = hw_ptr - so this is because appl_ptr
is not moved forward. Are there any reasons for this?
<7>DEBUG: p1 hw_ptr=0x3cdd43 (3988803) appl_ptr=0x3cebbc (3992508)
jiffie=21775142
<7>DEBUG: p1 hw_ptr=0x3ce028 (3989544) appl_ptr=0x3ceea1 (3993249)
jiffie=21775165
<7>DEBUG: p1 hw_ptr=0x3ce30d (3990285) appl_ptr=0x3cf186 (3993990)
jiffie=21775188
<7>DEBUG: p1 hw_ptr=0x3ce5f2 (3991026) appl_ptr=0x3cf46b (3994731)
jiffie=21775212
<7>DEBUG: p1 hw_ptr=0x3ce8d7 (3991767) appl_ptr=0x3cf750 (3995472)
jiffie=21775235
<7>DEBUG: p1 hw_ptr=0x3cebbc (3992508) appl_ptr=0x3cf750 (3995472)
jiffie=21775258
<7>DEBUG: p1 hw_ptr=0x3ceea1 (3993249) appl_ptr=0x3cf750 (3995472)
jiffie=21775281
<7>DEBUG: p1 hw_ptr=0x3cf186 (3993990) appl_ptr=0x3cf750 (3995472)
jiffie=21775304
<7>DEBUG: p1 hw_ptr=0x3cf46b (3994731) appl_ptr=0x3cf750 (3995472)
jiffie=21775328
<7>DEBUG: p1 hw_ptr=0x3cf750 (3995472) appl_ptr=0x3cf750 (3995472)
jiffie=21775351
<3>ERROR: p1 XRUN B! avail = 4446 stop_threshold = 4446 jiffie_diff=23
<7>DEBUG: playback trigger (1): cmd=stop
<7>DEBUG: trigger stop jiffies=21775351
<7>DEBUG: trigger stop jiffies difference =124742
<7>DEBUG: - pcm_timer_stop
<7>DEBUG: pcm prepare
I will go on searching for the reason, but I am thankful for any hint...
prev parent reply other threads:[~2010-01-29 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:40 overrun in second capture device after stopping first capture device Tobias Schneider
2010-01-26 14:23 ` Tobias Schneider
2010-01-29 18:12 ` Tobias Schneider [this message]
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=4B63251E.7080403@gmx.de \
--to=tobsnyder@gmx.de \
--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 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.