All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: underrun!!! (at least 1786051083.613 ms long)
Date: Mon, 28 Jul 2008 11:26:35 -0500	[thread overview]
Message-ID: <488DF33B.4050606@freescale.com> (raw)

I have a driver that supports simultaneous playback and capture, but only if the
same size and sample rate are the same.

I use these commands to play and capture audio:

aplay -D hw:0,0 -t raw -f S24_BE -r 48000 -c 2 test2.raw
arecord -D hw:0,0 -t raw -f S24_BE -r 48000 -c 2 test.raw

If I start capture first and playback second, then everything works.  If I start
playback first and capture second, I get this:

underrun!!! (at least 1786051083.587 ms long)
underrun!!! (at least 1786051083.586 ms long)
underrun!!! (at least 1786051083.585 ms long)
underrun!!! (at least 1786051083.585 ms long)
...

This repeats indefinitely.

Can someone explain how this is even possible?  1786051083.585ms is longer than
20 days!  How could ALSA be so wrong about the extend of the underrun?

-- 
Timur Tabi
Linux kernel developer at Freescale

                 reply	other threads:[~2008-07-28 16:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=488DF33B.4050606@freescale.com \
    --to=timur@freescale.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 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.