diff options
author | Mike Brady <mikebrady@eircom.net> | 2019-09-20 15:07:10 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-09-20 15:07:10 +0100 |
commit | 6f0e471bd4dd3adf9baa6f32c7bedeccd8b677d0 (patch) | |
tree | bc6381b4b8036d7ba0077edf25baf6c729090dcd /README.md | |
parent | 480464df87536a1bc884794e672c76fee9f22185 (diff) |
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -95,6 +95,8 @@ You should check to see if `shairport-sync` is already installed – you can use You should also remove the startup script files `/etc/systemd/system/shairport-sync.service` and `/etc/init.d/shairport-sync` if they exist – new ones will be installed in necessary. +If you removed any installations of Shairport Sync or any of its startup script files, you should reboot. + **Determine The Configuration Needed** Shairport Sync has a number of different "backends" that connnect it to the system's audio handling infrastructure. Most recent Linux distributions that have a GUI – including Ubuntu, Debian and others – use PulseAudio to handle sound. In such cases, it is inadvisable to attempt to disable or remove PulseAudio. Thus, if your system uses PulseAudio, you should build Shairport Sync with the PulseAudio backend. You can check to see if PulseAudio is running by opening a Terminal window and entering the command `$ pactl info`. Here is an example of what you'll get if PulseAudio is installed, though the exact details may vary: |