<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - raop module does not work with shairport" href="https://bugs.freedesktop.org/show_bug.cgi?id=42804#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - raop module does not work with shairport" href="https://bugs.freedesktop.org/show_bug.cgi?id=42804">bug 42804</a> from <a class="email" href="mailto:pulseaudio@niafc.de" title="Matthias <pulseaudio@niafc.de>"> Matthias</a> <pre>Hi Hajime, > I think the fundamental issue is that a client (movie/music player) thinks > that the audio device (PulseAudio) is ready and starts playing the picture, > while atcually it is not ready yet. That sounds reasonable. > I guess there should be some way to tell the application that "we are not > ready yet", or at least tell some latency. I think we need to understand > more about PulseAudio internals. I had a quick look through the developer documentation but did not find anything. However, if you look at module-raop-sink.c, function sink_process_msg, it looks to me as if the connect sequence is called when a PA_SINK_RUNNING state is set. Perhaps we could do the connect (and only this) when PA_SINK_INIT state is set. Setting PA_SINK_RUNNING (in my understanding) is set when the sink is connected and should play audio - this is were audio playback (i.e. sending sync and audio packets) should happen. Btw.: I just tested your latest patch (with the memchunk offset) and kindly ask you to put "Cambridge Audio Minx Air 200" on your supported device list. Works like a charm :). Greetings, Matthias</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>