<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#c23">Comment # 23</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:amar.akshat@gmail.com" title="Amar Akshat <amar.akshat@gmail.com>"> Amar Akshat</a> <pre>(In reply to <a href="show_bug.cgi?id=65703#c19">comment #19</a>) > (In reply to <a href="show_bug.cgi?id=65703#c17">comment #17</a>) > > > > > > 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) ? If client had no buffering, and given the delay in PA, the sound would have immediately stopped at the client side (or maximum in 1-2 seconds). The sound keeps playing for 16 seconds in the Client, suggests without reasonable doubt that client is buffering.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>