systemcrash
commented
2 years ago At last - a coherent bug report :)
I would hazard a guess that your WiFi channel is very noisy. real-time playback is most sensitive and susceptible to packet loss, which the log messages requesting resend indicate. If it's possible to have your receiver device on a wired connection, many problems should disappear. People with noisy WiFi areas (built up residential blocks) might suffer, here.
What's weird is the trace-back indicates that you are in a code-path unreachable if you are not using a flag for audio redundancy, which is off by default. This suggests a corrupted packet arrived...? I will put packet handling within a try..except clause to improve things there.
You might also look in audio around line 520 for
audioDevicelatency = \
self.pa.get_default_output_device_info()['defaultLowOutputLatency']and change to defaultHighOutputLatency if any problems persist.
Neustradamus
The problem
Hello openairplay community,
I'm trying to run airplay2-receiver on macOS 12.2.1. Installed it like this:
Managed to get it running, name shows up as "none" on my iPhone which seems weird but works. Audio playback is distorted and jagged and breaks down after around 30s.
Any Ideas?
Thank you very much
Tiziano
What commit exhibits the issue?
master
Was there a last known working commit?
No response
What type of installation are you running?
virtualenv
With which python3 version do you run Receiver?
python3
OS the receiver runs on
macOS 12.2.1
OS the sender runs
iPhone iOS 13
Which sender client was used
Spotify
Command invocation
python ap2-receiver.py -m myap2 --netiface=en0
Please include --debug output which helps to illustrate the problem
No response
Additional information
No response