<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve managed to get raop working with the devices I have on hand (I’m using Sayonara Player for playback), and I can even play on multiple sinks using the pulseaudio module module-combine-sink.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>However, unsurprisingly this fails to sync between the local sink and the raop sink. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I noticed this bit in the release notes:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>Much more accurate latency reporting for AirPlay devices</p><p class=MsoNormal style='margin-left:.5in'>The AirPlay protocol has a large latency, but PulseAudio didn't previously report that latency to applications. Now it reports it, or at least something much closer to the reality than before.</p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>The AirPlay protocol doesn't provide a mechanism for getting the exact latency (or if it does, we're not aware of that). PulseAudio makes an educated guess, and a significant part of that guess is a latency constant that is added to each latency report. The default value for that constant is exactly 2 seconds, but that's not optimal for all devices. PulseAudio uses a different constant for some known devices, and we'd like to expand the set of known devices. If you find that audio-video synchronization is bad with your AirPlay device, you can experiment with different latency constants by passing argument "latency_msec=2000" to module-raop-discover in /etc/pulse/default.pa. Change the number 2000 to something that works better. Once you find a better latency value, we'd be happy hear from you so that we can add your device to the list of known devices.</p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal>Which makes me think there has been some attempt to make sync possible. Yet it seems pulseaudio is ignoring its own latency reporting! When I press play/pause in my player, the output immediately ceases on the local sync, and I have to wait the 2 seconds for it to propagate to the raop device (as expected). </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is there a way to get what I want? Am I going about it complety wrong?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Marshall Eubanks</p></div></body></html>