From: Clemens Ladisch <clemens@ladisch.de>
To: Paul Dugas <paul@dugasenterprises.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Timing Info
Date: Thu, 17 Jun 2010 17:36:59 +0200 [thread overview]
Message-ID: <4C1A411B.2060301@ladisch.de> (raw)
In-Reply-To: <AANLkTinrDq0Mx-5uf00vOqHt5YAXZ7N3BNQz5NlJB7UB@mail.gmail.com>
Paul Dugas wrote:
> On Sun, Jun 13, 2010 at 10:10 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Set SND_PCM_TSTAMP_ENABLE to generate a timestamp whenever the hardware
> > position is updated. Call snd_pcm_status to read the position and the
> > corresponding timestamp.
>
> I've re-read this a number of times and have been fiddling with code
> that dumps the status at various points but I'm still not grasping the
> concept here. Can comeone point me to an explanation of the delay,
> avail, and avail_max values?
The avail value tells you how many frames are available, i.e., can be
written, in the output buffer. The largest value that this had since
the last snd_pcm_status call is avail_max.
The delay value is the time that will elapse before the next frame that
you write into the buffer will actually be output by the hardware. This
is not only the time until the hardware reads this frame out of the
buffer (which could be computed from avail) but also any processing
after that.
HTH
Clemens
prev parent reply other threads:[~2010-06-17 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 22:00 Timing Info Paul Dugas
2010-06-12 21:59 ` Paul Dugas
2010-06-13 14:10 ` Clemens Ladisch
2010-06-13 19:47 ` Paul Dugas
2010-06-14 22:54 ` Paul Dugas
2010-06-15 17:00 ` Paul Dugas
2010-06-17 15:36 ` Clemens Ladisch [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=4C1A411B.2060301@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=paul@dugasenterprises.com \
/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.