Jörg Krause [Mon, 23 May 2016 19:58:18 +0000 (21:58 +0200)]
Fix build without metadata support
Commit f36352dc4ece27fda24ef736183b8ff5729b8c96 introduced the parameter
pipe_timeout for the metadata config. If shairport-sync is now configured
without metadata support, the build fails with:
```
shairport.c: In function ‘main’:
shairport.c:766:9: error: ‘shairport_cfg {aka struct <anonymous>}’ has no member named ‘metadata_pipe_timeout’
config.metadata_pipe_timeout = 5000; //milliseconds
```
Fix this by opting-out the affected code with CONFIG_METADATA.
vru1 [Sat, 21 May 2016 20:56:25 +0000 (22:56 +0200)]
Update shairport-sync.spec
- Fixed Version: from 2.8.2 to 2.8.3.
- Fixed Release: special characters were reported as non-compliant by checkinstall
- Replaced all occurrences of character Horizontal Tab, ASCII Dec #9, that was used everywhere between a colon and tag value, with a Blank Space ASCII Dec #32. Horizontal Tab caused problems when creating a .deb package, tag values were reported as non-compliant by checkinstall.
- Fixed Requires: popt
If a .deb package was created with Requires: popt, the .deb package could not be installed due to a missing Package popt:
venca@cubox-i:~/shairport-sync$ sudo dpkg -i shairport-sync_2.8.3-1_armhf.deb
Selecting previously unselected package shairport-sync.
(Reading database ... 52746 files and directories currently installed.)
Preparing to unpack shairport-sync_2.8.3-1_armhf.deb ...
Unpacking shairport-sync (2.8.3-1) ...
dpkg: dependency problems prevent configuration of shairport-sync:
shairport-sync depends on popt; however:
Package popt is not installed.
dpkg: error processing package shairport-sync (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.0.2-5) ...
Errors were encountered while processing:
shairport-sync
After Requires: popt was changed to Requires: libpopt-dev and a new .deb package was created, the new .deb package could be installed.
vru1 [Sat, 21 May 2016 20:21:43 +0000 (22:21 +0200)]
Update README.md
If xmltoman is not installed, ./configure complains:
...
checking for xmltoman... no
configure: WARNING: >>xmltoman not found - not rebuilding man pages
...
After xmltoman is installed, no more complains:
...
checking for xmltoman... xmltoman
...
Afterwards when launching make, the man pages are processed ok:
...
xmltoman shairport-sync.7.xml > shairport-sync.7
Mike Brady [Fri, 20 May 2016 14:41:19 +0000 (15:41 +0100)]
Change password authentication to the same as an AirPort Express running 7.6.4. Only look for authentication once per session, to suit AllStream/Streambels
Jörg Krause [Fri, 6 May 2016 20:03:44 +0000 (22:03 +0200)]
Add support for ALSA softvol plugin
The ALSA softvol plugin allows the user to add a new volume control and control
the sound volume by software. This is necessary if the sound card can't control
the volume by hardware.
An example configuration in the `~/.asoundrc` file might look like this:
```
pcm.softvol {
type softvol
slave {
pcm "hw:0"
}
control {
name "Master"
card 0
}
min_dB -57.2
max_dB -6.2
}
ctl.softvol {
type hw
card 0
}
```
The corresponding entries in the shairport-sync would be:
```
alsa =
{
output_device = "softvol";
mixer_control_name = "Master";
}
```
Please check the (ALSA documentation)[http://alsa.opensrc.org/Softvol] and the
(ALSA PCM library reference)[http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html]
If shairport-syncs alsa backend does not have success in getting the dB volume
information from the hardware device it tries to get these information from a
software volume control with the name mixer device name as for the hardware
mixer.