++<<<<<<< HEAD
+name: Issue Report
+description: File an Issue
+title: "[Problem]: "
+labels: ["new issue"]
++=======
+ name: Bug Report
+ description: File a bug report
+ title: "[Bug]: "
+ labels: ["bug"]
++>>>>>>> origin/development
body:
- type: markdown
attributes:
value: |
++<<<<<<< HEAD
+ Thanks for taking the time to fill out this report!
++=======
+ Thanks for taking the time to fill out this bug report!
++>>>>>>> origin/development
- type: textarea
id: what-happened
attributes:
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: shell
- type: textarea
++<<<<<<< HEAD
+ id: os
+ attributes:
+ label: Operating System?
+ description: What Operating System are you running on ? (`uname -a`)
+ validations:
+ required: true
+ - type: textarea
++=======
++>>>>>>> origin/development
id: version
attributes:
label: Version?
description: What version of Shairport Sync are you running? (`shairport-sync -V`)
validations:
required: true
++<<<<<<< HEAD
+ - type: dropdown
+ id: install
+ attributes:
+ label: How did you install Shairport Sync?
+ options:
+ - Homebrew for Mac
+ - Docker
+ - A package manager (apt, yum, pkg, etc.)
+ - Built from source
+ validations:
+ required: true
++=======
++>>>>>>> origin/development
- type: checkboxes
id: checked-current-issues
attributes:
description: Please check previous issues (including closed ones) for duplicates.
options:
- label: Confirm
- required: true
++<<<<<<< HEAD
+ required: true
++=======
++ required: true
++>>>>>>> origin/development
1. Before starting, ensure that your software is up-to-date. This document always refers to the most recent version of Shairport Sync -- see [here](https://github.com/mikebrady/shairport-sync/releases) for information about the most recent release.
2. If you have set `interpolation` in the `general` section of the configuration file to to `soxr`, comment it out or set it to `auto` or `basic` as the `soxr` setting can cause lower-powered devices to bog down at critical times, e.g. see [this report](https://github.com/mikebrady/shairport-sync/issues/631#issuecomment-366305203).
- 3. Ensure the volume setting of your output device is set to some reasonable value and ensure it is not muted. For ALSA devices, the `alsamixer` command-line tool is very good for this. For other sound systems, please consult the relevant documentation.
+
+ ### No/Low Sound
+ Let's say you've just installed or updated Shairport Sync and you are testing it for the first time after installing or updating.
+ If you are using the default ALSA backend, don't forget to check two simple things:
+ 1. Check that the volume on the output device is turned up. If the output device has a "mixer" i.e. a volume control, Shairport Sync does not, by default, try to control it. Therefore, if it happens to be very low or even at zero, you might not hear audio that is actually coming through to the device. (You can get Shairport Sync to control a mixer -- see [here](https://github.com/mikebrady/spsdoc/blob/main/ADVANCED%20TOPICS/InitialConfiguration.md) for some hints.)
+ 2. Check that the output device is not muted. Some audio applications (including very old versions of Shairport Sync) leave the output device mixer in a muted state after use to minimise the possibility of noise. However, this is not generally compatible with other audio players using the same device, as they generally expect the device to be unmuted.
+
+ You can use `alsamixer` for both of theses checks. A muted output has the letter(s) `M` as its value. Select it and type `M` again to unmute.
+### Audio is Delayed!
+If the audio from your Shairport Sync device is delayed slightly by comparison with audio from other devices, it may be that the output device being fed by Shairport Sync is introducing a delay while it processes the audio. If your output device include any digital processing component, it probably delays the audio while it processing occurs.
+
+For instance, if your output device is a HDMI-connected device such as a TV or an AV Receiver, it will almost certainly delay audio by anything up to several hundred milliseconds.
+
+The fix for this is to ask Shairport Sync to provide the audio to the output device _slightly ahead of time_, so that by the time the output device has processed it, the audio emerges at exactly the right time. The setting to look for is in the `general` section of the Shairport Sync configuration file and is called `audio_backend_latency_offset_in_seconds`. By default it is `0.0` seconds.
+
+For example, if your output device is delaying audio by 100 milliseconds (0.1 seconds), set the `audio_backend_latency_offset_in_seconds` to `-0.1`, so that audio is provided to your output device 0.1 seconds early. Remember to uncomment the line by removing the initial `//` and then restart Shairport Sync (or reboot the device) for the changed setting to take effect.
+
### WiFi adapter running in power-saving / low-power mode
**Check Throughput**
projects / thirdparty / shairport-sync.git / commitdiff
