From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Problems with snd_pcm_status_get_delay()
Date: Tue, 08 Oct 2002 18:44:57 +0200 [thread overview]
Message-ID: <s5h8z183mnq.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DA30704.3050000@superbug.demon.co.uk>
At Wed, 09 Oct 2002 02:25:40 +1000,
James Courtier-Dutton wrote:
>
> Hello
>
> Can someone please explain to me the use of snd_pcm_status_get_delay()
>
> If a buffer size is 16384, and avail=6384, should delay therefore equil
> 10000 ? In all cases ?
no, the current implementation is the state-sensitive, as you
mentioned below :
> I have found that in SND_PCM_STATE_RUNNING, delay = buffer_size - avail.
> I have found that in SND_PCM_STATE_PREPARED, delay = 0
delay=0 gets back at all states except RUNNING (and DRAINING on
playback).
> This causes problems. As one fills the buffer in SND_PCM_STATE_PREPARED
> , delay stays at 0, but when the buffer fills enough and moves to state
> SND_PCM_STATE_RUNNING, the delay value suddenly jumps to delay =
> buffer_size - avail.
>
> This causes problems with applications that need "delay" to be as
> accurate as possible at all times.
> Is this a bug in alsa09, or should I ignore "delay" and just use the
> "buffer_size - avail" value.
snd_pcm_status_get_avail() returns the available space at any state.
so you can use this and calcuate "buffer_size - avail" manually
instead of get_delay().
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-08 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 16:25 Problems with snd_pcm_status_get_delay() James Courtier-Dutton
2002-10-08 16:44 ` Takashi Iwai [this message]
2002-10-09 6:45 ` Jaroslav Kysela
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=s5h8z183mnq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@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 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.