<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Pulse audio NOT USED multithreading" href="https://bugs.freedesktop.org/show_bug.cgi?id=90210#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Pulse audio NOT USED multithreading" href="https://bugs.freedesktop.org/show_bug.cgi?id=90210">bug 90210</a> from <a class="email" href="mailto:mikebrady@eircom.net" title="Mike Brady <mikebrady@eircom.net>"> Mike Brady</a> <pre>(In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=90210#c19">comment #19</a>) > (In reply to Alessandro Ferri from <a href="show_bug.cgi?id=90210#c18">comment #18</a>) > > When shairport-sync play music without pulseaudio, > > (iPad ---> Shaiport-sync ---> speakers) > > it remains in sync with other Airplay devices, such as the Apple Airport > > Express. But when shairport-sync plays music through pulseaudio, > > > > (iPad ---> Shaiport-sync ---> Pulseaudio --->speakers) > > > > the audio is not in sync with the other Airport device. > > You always think it's a bug on shairport? or that there are parameters to > > work. > > shairport-sync gets latency information from PulseAudio, and that should be > sufficient to keep the outputs in sync. If that doesn't happen, I believe > it's either a bug in shairport-sync, or the latency information from > PulseAudio is wrong, in which case it's of course PulseAudio's fault (or the > alsa driver's, but if it works with plain alsa, that seems unlikely). Hi there. I’m the developer of Shairport Sync and I just want to clear up a misunderstanding. Shairport Sync was developed from shairport specifically for use with the alsa back end. I realise that it works with the pulseaudio backend from the original shairport, but that’s just good fortune, to be honest. It does not use latency information coming back from pulseaudio. Maybe someday :) Kind regards Mike</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>