[alsa-devel] [PATCH] Wrong latency in pulseaudio plugin breaks Adobe Flash Player
david.henningsson at canonical.com
Fri Feb 17 10:12:36 CET 2012
On 02/17/2012 05:25 AM, Philip Spencer wrote:
> Thanks for the reply!
>>> In our case, the IO buffer is 500ms long, the IO period length is 20ms
>>> (for 16KHz Speex soud packets), and the application requests that
>>> start immediately (by setting the start_threshold software parameter
>> Hmm, if you want ~20 ms of latency, why have a 500 ms long buffer in the
>> first place?
> It seems to be hardcoded into Flash Player, not under control of the
> Flash Player app, and Flash Player is closed source so I can't say why
> for sure (I'm merely observing what it does).
So this is the usual problem with closed source applications: no
application is bug free, but when the closed source application is
broken, it's much harder to fix it. The sad reality is that by depending
on a closed source application, you're putting yourself in this situation.
> However, I imagine the intent is to be reslient against a wide variety
> of network conditions.
> If audio arrives in uniformly spaced 20ms packets, then it should be
> rendered with only 20ms latency. But if there's a lot of network
> congestion and high jitter, several hundred ms could arrive at once.
> If Flash Player used a short buffer, these audio samples would get lost.
> By using a 500ms buffer, playback is smooth, with only as much latency
> as is necessitated by the network jitter.
> So: short buffer, short latency request --> samples get lost if they
> arrive with high jitter
> long buffer, long latency request --> long undesired latency
> long buffer, short latency request --> smooth playback always, with
> short latency when possible,
> longer latency only when
> necessitated by high jitter
The way most applications (should) work with ALSA is that they fill the
buffer up completely, when it's full they start playback, and at every
period interrupt they fill up yet another period. So when you have a
large number of periods (like in your case, 500/20 = 25 periods), the
buffer is almost full all the time.
Now; if an application start playback with an empty buffer (either by
calling "trigger" or by setting a low start threshold), should we assume
that 1) the application is going to stay almost empty all the time, like
it seems Flash does in this scenario, or 2) fill it up completely and
stay there (IIRC, mpg123 did this)?
Lowering tlength might be reasonable in scenario 1, but scenario 2 will
cause the client to block (trying to fill an already filled buffer) in
ways that differs from the expected behaviour.
>>> but this does not work: playback STARTS sooner, but when dropouts and
>>> underruns occur pulseaudio increases the latency to match the target
>>> buffer length.
>> Just a quick question: Are you saying there is an immediate change from
>> 20 to 500 ms at the first underrun, or that things gradually adapts up
>> to a stable level?
> It's fairly immediate (within the first half-second, anyway).
>>> It is necessary to lower the target buffer length too.
>> I think this part requires more investigation though. First, I'm
>> assuming you are talking about underruns between the client and
>> PulseAudio, rather than underruns between PulseAudio and the hardware.
> I'm actually not entirely sure which is happening. But whichever one it
> is, pulseaudio very quickly adjusts things and pauses playback until the
> buffer fills up to its target length. Perhaps a pulseaudio developer
> could comment on whether that is indeed pulseaudio's intended behaviour.
That's a good question. For investigation, maybe you could compile a
version without the tlength adjustment (only the prebuf adjustment), and
then make a PulseAudio log  and pastebin it (it's probably too large
to make it as an attachment to this list) where we can see how
PulseAudio changes the buffers when underruns happen?
>> Setting a tlength of 500 ms will have PulseAudio believe you intend to
>> have latency in the range of 250 - 500 ms, so you're starting with the
>> buffer almost empty, and if I understand it correctly, things continue
>> that way? This is usually bad and a recipe for underruns. Anyway, this
>> is probably why lowering the tlength works for your particular use case.
> Yes, it does not seem to be right to set PulseAudio's tlength to 500ms
> just because ALSA's IO buffer is 500ms -- I think ALSA's IO buffer
> length corresponds better to PulseAudio's *maxlength* than to tlength.
> And the PulseAudio docs, though being a little ambiguous on the exact
> working of tlength and prebuf, do recommend setting prebuf to be the
> same as tlength.
As you probably already have discovered, PulseAudio's buffering does not
work exactly the way ALSA's buffering does. Most applications try to
keep their buffers as full as they can, so that's the case we're
optimising for. In that case, setting tlength to the IO buffer length is
the correct way to do it.
As for maxlength, that's an interesting question. But if maxlength is
set to -1 or to 500 ms I don't think matters for your particular case.
>> Note though that I'm sceptic to the tlength part of the patch not mainly
>> for philosophical reasons (hey, I want things to just work too!) but
>> because I'm afraid it will fix some applications and break others.
>> Emulating ALSA over PulseAudio is not easy due to the asynchronous
>> nature of PulseAudio (among other things), and applications use and
>> expect ALSA to do different things.
> The patch will only affect applications which
> (a) Set an explicit start threshold requesting playback to begin
> before the buffer is filled, AND
> (b) Specify a low value for IO period
> If an app specifically requests both an early playback start and a small
> IO period, then I think it's reasonable to honour that request and ask
> pulseaudio to maintain low latency.
I think the root cause of this problem is that PulseAudio does not
handle almost-empty buffers very well, and this is the problem we need
to fix, rather than to work around it in the ALSA plugin layer.
> Your comment, though, about "500 ms tlength means pulseaudio thinks you
> want a latency between 250ms and 500ms" --
E g, it tends to send out underrun reports although there might still be
audio left to play back (it's just in another buffer), with tlength=500
ms this might happen when there is still up to 250 ms left. (One
difference though; ALSA Plugins do not seem to run in adjust latency
mode though - maybe they should? - so the figures might not apply
directly.) I think this is bad, but not everyone agrees. If you're
interested, you can read about a similar thread with VLC which starts
here , in particular read  for why some think this is correct to
> if that really is the case, and
> tlength=n means pulseaudio thinks latency should be between n/2 and n,
> then perhaps it would be safer to only lower tlength to
> 2 * (larger of start threshold, IO period)
> instead of 1 * (larger of start threshold, IO period) as in my patch.
Yes, also because minreq should be a lot lower than tlength.
David Henningsson, Canonical Ltd.
More information about the Alsa-devel