From: James Courtier-Dutton <james.dutton@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Latency of mixer reconfiguration
Date: Wed, 17 Feb 2010 20:34:17 +0000 [thread overview]
Message-ID: <ad2655cb1002171234g4f73edd4j19c2f89bfc7bf567@mail.gmail.com> (raw)
In-Reply-To: <20100217181530.GA23152@tango.0pointer.de>
On 17 February 2010 18:15, Lennart Poettering <mznyfn@0pointer.de> wrote:
> Heya!
>
> So, as some of you might know in PA we extend the abilities of the
> hardware volume control in software. Meaning that if a hw mixer
> control only allows a limited range or granularity of a volume scale
> or does not distuingish between channels then PA will configure the
> hardware to the next higher available setting of the real
> volume it wants to achieve, and then attenuates the PCM stream to
> compensate for the rest.
>
> This actually works quite well but there is a certain probelm with
> latency: i.e. the mixer setting will be applied at a slightly
> different time than the PCM attenuation.
>
> Now the question I have is, how should I best deal with this? I
> currently assume that mixer volume changes are basically instantaneous
> when I call the respective function of ALSA. But are they really? How
> big is the latency at max? Do we need an API to query it?
>
> Lennart
>
The latency is non-deterministic.
latency of the PCM stream is more predictable.
I am not sure how you might get around this problem.
next prev parent reply other threads:[~2010-02-17 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 18:15 Latency of mixer reconfiguration Lennart Poettering
2010-02-17 20:34 ` James Courtier-Dutton [this message]
2010-02-18 10:01 ` Mark Brown
2010-02-18 18:04 ` Lennart Poettering
2010-02-19 9:01 ` Jaroslav Kysela
2010-02-19 9:43 ` Mark Brown
2010-02-19 9:54 ` Mark Brown
2010-02-19 15:03 ` Lennart Poettering
2010-02-20 3:59 ` Raymond Yau
[not found] ` <20100221192621.GC30380@tango.0pointer.de>
2010-02-22 8:50 ` Raymond Yau
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=ad2655cb1002171234g4f73edd4j19c2f89bfc7bf567@mail.gmail.com \
--to=james.dutton@gmail.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 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).