Hi Arun, Just wanted to let you know that I got the latest AppleTV and confirmed the issue. https://github.com/hfujita/pulseaudio-raop2/issues/53 Looks like there's some minor update in the protocol or validation has become stricter than before. Thanks, Hajime Arun Raghavan wrote: > On 12 February 2016 at 12:03, Hajime Fujita <crisp.fujita at nifty.com> wrote: >> Hi Arun, >> >> Arun Raghavan wrote: >>> Hi Hajime, >>> I'm still working on this, it's slow going since I have other things to >>> do in parallel. >> >> Thank you for your reply. Yeah that's totally fine. Just wanted make sure if it was appropriate to submit a new series. >> >>> It's a bit hard to review this work properly per-commit, so I'm going >>> to try to summarise the issues I've found at one go. >>> >>> * There are some style issues that I'm fixing up as I find, and I'll >>> just have that as a commit on top of your tree. >>> >>> * While testing, I see there are two instances loaded every time (one >>> for IPv4 and one for IPv6) -- wouldn't it be more user friendly to make >>> sure we load only one? This doesn't appear to be a new issue, so not a >>> blocker on this series >> >> I've been aware of this for a while. I think my thought was that some user might want to explicitly choose IPv4 or v6 address. I'm not sure if it is a real need though. >> >>> >>> * I tried this against Airserver on a Mac (worked) and a current >>> generation Apple TV (did not work) -- just got stuck trying to start >>> playback >> >> Hmm you mean the latest Apple TV which came out last year? I currently don't have that one so it'll be a bit hard to debug... let me check the price :) > > That's the one. I might be able to try again and get you a packet > capture if that helps. > > -- Arun > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss >
