alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Piers O'Hanlon" <p.ohanlon@cs.ucl.ac.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Getting XRUN after writei in RUNNING state?
Date: Sat, 10 Nov 2007 11:46:40 +0000	[thread overview]
Message-ID: <abe39f780711100346r2b71c664u777c96f60f1db0e8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0711091746060.8935@tm8103-a.perex-int.cz>

Hi Jaroslav,

Just to let you know I'm running this on Ubuntu 7.10
(alsa-lib-1.0.14), though I've been seeing this underrun problem for a
while on a few systems (Ubuntu 7.04/6.10, and Gentoo 2006.1). It
hasn't been clear to me what the key parameters are that control
underrun behaviour. (It would be great if someone wrote a
comprehensive book/article on ALSA....)

BTW you mentioned doing the rate resampling in RAT - which it can do -
how does one discover if rate conversion is occurring in ALSA and
obtain that 'base' rate? (Though I has assumed that ALSA would do the
better job of rate resampling if it was necessary...).

Thanks,

Piers.

On 09/11/2007, Jaroslav Kysela <perex@perex.cz> wrote:
> On Fri, 9 Nov 2007, Piers O'Hanlon wrote:
>
> > ===snd_pcm_dump_setup:===============
> >   stream       : PLAYBACK
> >   access       : RW_INTERLEAVED
> >   format       : S16_LE
> >   subformat    : STD
> >   channels     : 1
> >   rate         : 16000
> >   exact rate   : 16000 (16000/1)
> >   msbits       : 16
> >   buffer_size  : 2048
> >   period_size  : 341
> >   period_time  : 21333
> >   tick_time    : 0
> >   tstamp_mode  : NONE
> >   period_step  : 1
> >   sleep_min    : 0
> >   avail_min    : 341
> >   xfer_align   : 1
> >   start_threshold  : 341
> >   stop_threshold   : 2048
> >   silence_threshold: 0
> >   silence_size : 0
> >   boundary     : 536870912
>
> Could you do whole dump (snd_pcm_dump()) to see all plugins in chain?
> I judge from period_size that we have another problem with rate plugin.
> It would be better to do rate resampling in RAT.
>
>                                                 Jaroslav
>
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project
>

      parent reply	other threads:[~2007-11-10 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 16:34 Getting XRUN after writei in RUNNING state? Piers O'Hanlon
2007-11-09 16:49 ` Jaroslav Kysela
2007-11-09 17:07   ` Piers O'Hanlon
2007-11-10 11:46   ` Piers O'Hanlon [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=abe39f780711100346r2b71c664u777c96f60f1db0e8@mail.gmail.com \
    --to=p.ohanlon@cs.ucl.ac.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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).