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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #16 from Arun Raghavan <arun at accosted.net> ---
(In reply to comment #15)
> >You could probably eliminate the client buffering (or at least make it >deterministic) by just opening the HTTP stream directly (look at >http://localhost:4714/).
> >
> 
> Yes, absolutely, so in my experiment described in Commend 13, I was
> accessing directly the sound cards as exposed by PA over HTTP, without
> Rygel. However, by setting the client buffering to 0 or as low as 2 seconds,
> I wasn't able to play the sound perfectly.
> Moreover I found that my client (Windows Media Player), was playing the
> stream at 1411 Kbps, which is the bitrate for uncompressed sound.
> 
> Does this suggest that we should apply compression at PulseAudio..?

Your localhost network should easily cope with the 1.4 Mbps, so this is
unlikely to be the culprit.

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.

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