Update AirPlay 2 service options in release notes [skip ci]
Enhanced AirPlay 2 build options and improved input format change delivery.
This commit is contained in:
@@ -15,7 +15,7 @@ Version 5.1-dev
|
||||
**Enhancements**
|
||||
1. Enable the AirPlay 2 build to provide pure classic AirPlay either optionally or automatically if NQPTP is not running, as follows:
|
||||
* Add a new command-line option `-—service-type=<type>` and an equivalent configuration entry `service_type = "<type>";` in the `general` section of the configuration file, where `<type>` can be `"auto"`, `"classic"` or `"airplay2"`:
|
||||
1. `"auto"` (default) means that the service will be AirPlay 2 if NQPTP is running and classic AirPlay otherwise. If NQPTP is not running, classic AirPlay service will be provided and `(Classic)` will be appended to the default AirPlay service name visible to AirPlay clients like Apple Music, for example `RaspberryPi3B (Classic)`.
|
||||
1. `"auto"` (default) means that the service will be AirPlay 2 if NQPTP is running. If NQPTP is not running, classic AirPlay service will be provided and `(Classic)` will be appended to the default AirPlay service name visible to AirPlay clients like Apple Music, for example `RaspberryPi3B (Classic)`.
|
||||
2. `"classic"` means the service will be classic AirPlay (aka AirPlay 1).
|
||||
3. `"airplay2"` means the service will be the modern AirPlay 2. In this case, as distinct from `"auto"`, if NQPTP is not running, Shairport Sync will log an error and terminate.
|
||||
* In the `systemd` service file, NQPTP is now a `Want` rather than a `Require`. If it's present, it will be launched before Shairport Sync.
|
||||
|
||||
Reference in New Issue
Block a user