<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - High latency in HTTP streaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=65703#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - High latency in HTTP streaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=65703">bug 65703</a> from <a class="email" href="mailto:arun@accosted.net" title="Arun Raghavan <arun@accosted.net>"> Arun Raghavan</a> <pre>(In reply to <a href="show_bug.cgi?id=65703#c15">comment #15</a>) > >You could probably eliminate the client buffering (or at least make it >deterministic) by just opening the HTTP stream directly (look at ><a href="http://localhost:4714/">http://localhost:4714/</a>). > > > > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>