Thank you for bringing recent developments with Airplay2 to my attention!
Before I found the XML settings for Airplay in version 5.0 and long before 5.35, I had an Airplay engine running on my MPS4.
I implemented the Shairport-sync solution found on Github and ran it on the Linux emulator Cygwin on my MPS4s V1 & V2 with Win7.
All of this sounds very advanced, but it was actually not. I had no prior experience of Github projects, Linux or Cygwin.
I got metadata running nicely in the same way as with a CCA, but had some problems using command and control with Cygwin. The developer helped me out, but he never really cracked it. Shairport does however support this on most other Linux platforms as well as full multi-speaker support. My guess is that it would work well on Windows Subsystem for Linux.
The shairport solution had better buffer handling than the 5.0 implementation of Airplay, hence fewer (no) occasional scratching sounds.
With 5.35, we again got a better Airplay implementation, so I paused the shairport solution.
From my experience, Airplay with 5.35 is now working according to Airplay specs and the intial 2 second buffering is standard. This might be what you call latency?
- if you have any audio problems I would recommend tuning the buffer size in the Autonomic Controls Remote Configuration settings (Telnet port 23).
However, and this might be what you refer to, there are some quirks when using Airplay and Spotify Connect to directly address individual speakers.
Mostly it works fine, but at times I notice a few irritating problems with Spotify Connect:
- on my iPhone 7, I cannot discover all zones, only the latest one. Works fine for other members of the family (newer iPhones).
- the problem above might have something to do with which wifi AP I am using. I have three different brands in my network...
- sometimes I need to do the operation twice. The first time the zone is fired up, but the connection is not transfered = no music
- seldomly, when I choose 1 zone, they ALL fire up. This can be very stressful. Especially when testing in the middle of the night!
The latter problem may happen more often after a reboot, but my statistics are weak.
I imagine that these problems are due to timing of instructions on the MCS and might therefore be similar for Airplay?
I have made a few attempts to trace the logs, but have not been able to find the core problem.
Maybe more memory or CPU could solve the issues?
In any case, the problems are not major and I find these features fantastic!