<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - a2dp skips terribly" href="https://bugs.freedesktop.org/show_bug.cgi?id=88827#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - a2dp skips terribly" href="https://bugs.freedesktop.org/show_bug.cgi?id=88827">bug 88827</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>(In reply to R Schultz from <a href="show_bug.cgi?id=88827#c6">comment #6</a>) > What needs to be done to continue troubleshooting the issue? I think it would be good to gather detailed timestamped data about the various events that are related to bluetooth streaming. The "Skipping NNN us (= MMM bytes) in audio stream" log message that is mentioned in the Ubuntu bug title suggests that the buffer behind the bluetooth socket stays full for prolonged periods, so PulseAudio is simply unable to write any data. It would be good to verify this with hard data. Someone could try changing the A2DP writing logic so that PulseAudio would always write immediately when the socket becomes writable. That would eliminate the possibility that PulseAudio doesn't write fast enough. module-sine could be used for testing, because that module should be able to provide data no matter how weird the sink timing is (I'm worried that regular applications might have trouble keeping their buffers filled if the bluetooth writes happen in big bursts). If it turns out that there are drop-outs no matter how quickly PulseAudio writes data, then the next step would be to investigate at the kernel side.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>