Closed systemcrash closed 2 years ago
If I team it up with e.g. Sonos speakers, there's a bit of delay/difference from this receiver, i.e. the receiver is ~100msec behind Sonos speakers. I guess synch leaves a little something to be desired.
Audio Sync isn't implemented at all, so that's totally to be expected.
See https://github.com/ckdo/airplay2-receiver/pull/16 - this PR cleans up lots of weird startup/connect behaviour (for me, at least).
See here for IPv6 problems.... https://github.com/prometheus/client_python/issues/567
Mac (also running the local copy of receiver):
iOS:
Summary: perhaps macOS requires a different feature bitmask?
When the first device connecting after startup is my mac I get all kinds of weird hangups and even:
Sometimes it makes it all the way to
and just sits there. No error message from macos, but macos has no connection to airplay device either. Remains on speaker output.
Still occasionally gets stuck at the below, on successive connect attempts, even with PR https://github.com/ckdo/airplay2-receiver/pull/11
My iOS Music player will connect, often fine. Only after my iOS device has connected and disconnected, then my local mac has no problem connecting. Seems some object state left over from the previous connection helps. Could not get any supported audio media types to play from my mac, however. Logs just repeat this:
I do note that after iOS has connected (remote device) - when my local mac connects, I no longer see the loopback IP so much in the logs - only its 192.168 IP. I propose a fix for this, will make a PR.
Tried playing some 5.1 media via VLC, which played (tho output was silent), but nothing was in the logs. VLC hung on exit XD
iOS plays fine. If I team it up with e.g. Sonos speakers, there's a bit of delay/difference from this receiver, i.e. the receiver is ~100msec behind Sonos speakers. I guess synch leaves a little something to be desired.
Anyway, good work 👍