Version 2.4 – New Stable Release

Version 2.4

Stable release

This stable release is the culmination of the 2.3.X sequence of development releases.

Change Summary

Changes from the previous stable version -- 2.2.5 -- are summarised here:

• Settings are now read from a configuration file. Command-line settings are supported but discouraged.
• Metadata is now supported -- it can be delivered to a unix pipe for processing by a helper application. See https://github.com/mikebrady/shairport-sync-metadata-reader for a sample metadata reader.
• Raw PCM audio can be delivered to standard output ("stdout") or to a unix pipe. The internal architecture has changed considerably to support this.
• Support for compilation on OpenWrt back to Attitude Adjustment.
• Support for unencrypted audio streams -- compatible with, e.g. Whaale.
• Uses the libconfig library.
• Runs on a wider range of platforms, including Arch Linux and Fedora.
• Bug fixes.

Please note that building instructions have changed slightly from the previous version.
Also, the -t hardware/software option has been deprecated in the alsa back end.

Version 2.3.13.1 – Development: Fedora build script updates

More of the same.

Version 2.3.13 – Development: Fedora build script updates

Version 2.3.13

Note

• We're getting ready to release the development branch as the new, stable, master branch at 2.4. If you're packaging Shairport Sync, you might prefer to wait a short while as we add a little polish before the release.

Changes

• Harmonise version numbers on the release and on the shairport.spec file used in Fedora.

Version 2.3.12 – Development. Stronger interpolation, more…

Note

• We're getting ready to release the development branch as the new, stable, master branch at 2.4. If you're packaging Shairport Sync, you might prefer to wait a short while as we add a little polish before the release.

Changes

• update-rc.d has been removed from the installation script for System V because it causes problems for package makers. It's now noted in the user installation instructions.
• The alsa group mixer_type setting is deprecated and you should stop using it. Its functionality has been subsumed into mixer_name – when you specify a mixer_name it automatically chooses the hardware mixer type.

Enhancements

• Larger range of interpolation. Shairport Sync has previously constrained not to make interpolations ("corrections") of more than about 1 per 1000 real frames. This contraint has been relaxed, and it is now able to make corrections of up to 1 in 352 real frames. This might result in a faster and undesirably sudden correction early during a play session, so a number of further changes have been made. The full set of these changes is as follows:
  • No corrections happen for the first five seconds.
  • Corrections of up to about 1 in 1000 for the next 25 seconds.
  • Corrections of up to 1 in 352 thereafter.

Documentation Update

• Nearly there with updates concerning the configuration file.

Version 2.3.11 – Development

Documentation Update

• Beginning to update the man document to include information about the configuration file. It's pretty sparse, but it's a start.

Version 2.3.10 – Development

Bug fix

• The "pipe" backend used output code that would block if the pipe didn't have a reader. This has been replaced by non-blocking code. Here are some implications:
  • When the pipe is created, Shairport Sync will not block if a reader isn't present.
  • If the pipe doesn't have a reader when Shairport Sync wants to output to it, the output will be discarded.
  • If a reader disappears while writing is occuring, the write will time out after five seconds.
  • Shairport Sync will only close the pipe on termination.

Version 2.3.9 – Development

Bug fixes

• Specifying the configuration file using a relative file path now works properly.
• The debug verbosity requested with -v, -vv, etc. is now honoured before the configuration file is read. It is read and honoured from when the command line arguments are scanned the first time to get a possible configuration file path.

Version 2.3.8 – Development

Version 2.3.8

• Annoying changes you must make
  • You probably need to change your ./configure arguments. The flag with-initscript has changed to with-systemv. It was previously enabled by default; now you must enable it explicitly.
• Changes
  • Added limited support for installing into systemd and Fedora systems. For systemd support, use the configuration flag --with-systemd in place of --with-systemv. The installation does not do everything needed, such as defining special users and groups.
  • Renamed with-initscript configuration flag to with-systemv to describe its role more accurately.
  • A System V startup script is no longer installed by default; if you want it, ask for it with the --with-systemv configuration flag.
  • Added limited support for FreeBSD. You must specify LDFLAGS='-I/usr/local/lib' and CPPFLAGS='-L/usr/local/include' before running ./configure --with-foo etc.
  • Removed the -configfile annotation from the version string because it's no longer optional; it's always there.
  • Removed the dummy, pipe and stdout backends from the standard build – they are now optional and are no longer automatically included in the build.
• Bug fixes
  • Allow more stack space to prevent a segfault in certain configurations (thanks to https://github.com/joerg-krause).
  • Add missing header files(thanks to https://github.com/joerg-krause).
  • Removed some (hopefully) mostly silent bugs from the configure.ac file.

Version 2.2.5 – Stable Version, Minor Bugfixes

Version 2.2.5

This is a minor bug fix in the stable branch of Shairport Sync. An updated version of Shairport Sync, Version 2.4, which will have significant changes, should be available soon. For a preview, switch to the development branch, versions 2.3.X.

• Bugfixes
  • Fix a segfault error that can occur in certain cases (thanks again to https://github.com/joerg-krause).
  • Include header files in common.c (thanks again to https://github.com/joerg-krause).

Version 2.3.7 – Development

• Changes
  • Removed the two different buffer lengths for the alsa back end that made a brief appearance in 2.3.5.
• Enhancements
  • Command line arguments are now given precedence over config file settings. This conforms to standard unix practice.
  • A –without-pkg-config configuration argument now allows for build systems, e.g. for older OpenWrt builds, that haven't fully implemented it. There is still some unhappiness in arch linux builds.
• More
  • Quite a bit of extra diagnostic code was written to investigate clock drift, DAC timings and so on. It was useful but has been commented out. If might be useful in the future.