nils/shairport-sync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update AIRPLAY2.md

Browse Source
This commit is contained in:
Mike Brady
2021-07-07 08:45:51 +01:00
committed by GitHub
parent c9da658fe1
commit 1f8999522f
1 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AIRPLAY2.md
+14 -7
View File
@@ -2,27 +2,34 @@ AirPlay 2
===
## General
* **AirPlay 2 support is experimental and incomplete.** The focus of the development effort has been on getting the best possible audio performance. Many features outside that focus are missing or broken. So, for example, integration with Apple's Home app is missing; remote control doesn't work.
* For AirPlay 2, Shairport Sync requires the services of another application called [`nqptp`](https://github.com/mikebrady/nqptp) ("Not Quite PTP") for timing and synchronisation. `nqptp` must run as `root` and must have exclusive access to ports `319` and `320`.
* AirPlay 2 support is only available on recent Linux and FreeBSD builds. The FreeBSD implementation has not been extensively tested. OpenBSD and Cygwin are not supported. AirPlay 2 support will definitely not work on Mac OS X. The reason is that Shairport Sync needs to use [`nqptp`](https://github.com/mikebrady/nqptp), which uses ports `319` and `320`. These ports are already used by Mac OS X to support its implementation of AirPlay 2.
* The AirPlay 2 build requires a good deal of extra library support and may not fit into smaller devices. It also requires more CPU power and more RAM.
Shairport Sync offers limited AirPlay 2 support for audio sources on iOS devices and Macs. In addition, it partly works if the sources is a HomePod mini or an Apple TV. It does not work for iTunes on Windows. Unfortunately, it does not work with the Home app or with Siri.
The focus of the development effort has been on getting good audio performance for iOS and Mac. Features outside this focus may be missing or broken. So, for example, integration with Apple's Home app is missing; remote control doesn't work.
For AirPlay 2, Shairport Sync uses another application called [`nqptp`](https://github.com/mikebrady/nqptp) ("Not Quite PTP") for timing and synchronisation. `nqptp` must run as `root` and must have exclusive access to ports `319` and `320`.
AirPlay 2 functionality is available on recent Linux and FreeBSD builds. The FreeBSD implementation has not been extensively tested. OpenBSD and Cygwin are not supported.
AirPlay 2 support definitely does not work on macOS. This is because Shairport Sync needs to use [`nqptp`](https://github.com/mikebrady/nqptp), which uses ports `319` and `320`. These ports are already used by macOS to support its implementation of AirPlay 2.
The AirPlay 2 build requires a good deal of extra library support and may not fit into smaller devices. It also requires more CPU power and more RAM.
### What Works
- AirPlay 2 for iOS and Mac players.
### What Does Not Work
- No AirPlay 2 for Windows iTunes
- No integration with Siri or HomeKit
- Lossless or High Definition Lossless material seems to be transcoded to AAC before transmission over AirPlay 2.
- No Remote Control
- No Artwork in the Metadata
- No AirPlay 2 for Windows iTunes
### What Partly Works
- Incomplete functionality using AppleTV or HomePod as player.
A Shairport Sync player will work -- i.e. it will play, but the selection button won't persist and the volume can't be set.
### Limitations
- You can only run a single instance of Shairport Sync on a device.
- Only a single instance of Shairport Sync can run on a device.
- The AirPlay 2 version of Shairport Sync will not run on macOS, since `nqptp` can not be installed on it.
### Known Issues
@@ -32,7 +39,7 @@ AirPlay 2 -- What You Need
---
AirPlay 2 support needs a more powerful CPU for decoding and synchronisation and more memory for bigger buffers and larger libraries. Raspberry Pi OS, Ubuntu 20.04 on a VM and Ubuntu 20.04.2 64-bit Server Edition have been used extensively in development, with Alpine Linux and FreeBSD 12.2 being used to a lesser extent.
Here are some suggestions:
So, here are some guideline requirements:
* Full access, including `root` privileges, to a system at least as powerful as a Raspberry Pi 3.
* A fully up-to-date Linux. This is important, as some of the libraries must be the latest available.
* An audio output, for example an `alsa` device (or `sndio` in FreeBSD). The `stdout` and `pipe` backends continue to work as before. Other backends have not been tested.