[pulseaudio-tickets] [Bug 65703] High latency in HTTP streaming

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=65703

--- Comment #19 from Wang Xingchao <wangxingchao2011 at gmail.com> ---
(In reply to comment #17)
> > 
> > That's not to say comrpession is not desirable (although doing that in PA
> > itself is not ideal), but the bandwidth problem should be orthogonal to the
> > latency being this large.
> 
> However, the buffering is definitely at client end. Because I did the
> following.
> 
> a) Exposed sound cards using rygel, and also directly through http.
> b) Connected from my Android device and started streaming, with around 16
> second latency.
> c) Simply power-offed the system, removing any trace of PA and rygel,
> however my Android device kept playing the sound, until 16 seconds, and then
> the stream just died.
> 
> So, the client essentially has the stream buffered for 16 seconds.

what's the expected behavior here after step c) ?
After power-offed, the connection died so if no buffering at client end user
could hear nothing, right?
And now android device continue sending left buffering stream out for default
device(andoird itself) until all buffering data empty.

So the issue is maybe PA blocked the transferring and caused the high latency.
I mean if PA is fast enough or ready to accept any buffering stream from client
end, the buffering stream length in client end should be always 0. 

thanks
--xingchao

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20130702/130e3ca5/attachment-0001.html>