2.1.12 statistics option and tinysvcmdns bug fixes

• A new command line option has been added: --statistics, so you don't have to put the program into verbose (-v) mode to get the stats.
• tinysvcmdns is a zero configuration (zeroconf) service you can use if you don't have a system-wide zeroconf service, such as Avahi, already running on your system. This release fixes a few bugs in the tinysvcmdns implementation. You should not use tinysvcmdns if your system has a zeroconf service already running.

2.1.11 Man Page

A man page is now installed. You can see a web version of is here: http://htmlpreview.github.io/?https://github.com/mikebrady/shairport-sync/blob/2.1/man/shairport-sync.html

2.1.10 Bug Fix

• Bugfix
  • A bug that caused the -t timeout value to be incorrectly assigned has been fixed. (Cause: config.timeout defined as int64_t instead on int.)

2.1.9 Bug Fixes

1. A bug that sometimes caused the initial volume setting to be ignored has been fixed. (Cause: setting volume before opening device.)
2. A bug that caused shairport-sync to become unresponsive or unavailable has been fixed. (Cause: draining rather than flushing the alsa device before stopping.)

2.1.8 Add disconnect/reconnect, clean up some –with-... options

1. Adds the facility to disconnect and reconnect shairport-sync from the output device without interrupting audio streaming from the source.
2. Simplifies the –with-openssl and with-polarssl to –with-ssl=openssl or polarssl.
3. Replace –with-localstatedir with –with-piddir
4. Fixes a small bug

2.1.7 Bug Fix

Fix a race condition on the universal timer.

2.1.6 Toggle connection with ALSA device

This is an attempt to make Shairport Sync interwork better with other audio programs. If you send a SIGUSR2 to Shairport Sync, it will disconnect from and release the ALSA device it's using, allowing other audio programs to take the device. Shairport Sync will continue to work normally is all other respects. Send it another SIGUSR2 and it will try to regain the ALSA device, but won't complain if it can't. Thus, to be exact, a SIGUSR2 signal toggles its connection with the ALSA device.

You can send a SIGUSR2 signal to a properly-launched shairport-sync daemon by executing shairport-sync -P (you might need to have root privileges). This will launch another copy of shairport-sync which will send the SIGUSR2 signal to the daemon process and then exit.

This is very experimental.

2.1.5 Add --with-localstatedir configure option

When Shairport Sync is running as a daemon, it writes its process ID (PID) to a file. The file must be stored in part of the file system that is writable. Most build systems choose an appropriate 'local state directory' location automatically, but some, notably buildroot, don't always get it right for an embedded system. This compilation option allows you to specify the local state directory. Supersedes 2.1.4, which tried to do the same thing.

[Update] This has been superseded. Do not use.

V2.5.0.3 – Development – making more palatable for FreeBSD

Fixing some configuration issues and quietening some compiler warnings in FreeBSD 10.2

Bugfix

Fixes a bug which stopped Shairport Sync starting on an IPv4-only system. Thanks Ted Hess.