From: Mike Brady Date: Sun, 17 Feb 2019 14:41:21 +0000 (+0000) Subject: Update RELEASENOTES.md X-Git-Tag: 3.3RC0~54 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=55001a2ab91fcdf6856d0a310ad69d14de7dad42;p=thirdparty%2Fshairport-sync.git Update RELEASENOTES.md --- diff --git a/RELEASENOTES.md b/RELEASENOTES.md index 2b67c5ad..ede9b9cd 100644 --- a/RELEASENOTES.md +++ b/RELEASENOTES.md @@ -1,11 +1,13 @@ -Version 3.3d52 to Version 3.3d40 +Version 3.3d53 to Version 3.3d40 ==== **New Features** * Two new external program/script hooks – `run_this_before_entering_active_state` and `run_this_after_exiting_active_state` are provided for when the system becomes active and when it becomes inactive. Background: Many users use the `run_this_before_play_begins` program hook to turn on an amplifier and the `run_this_after_play_ends` hook to turn it off. A big problem is when another play session starts immediately afterwards. This happens, for example, when a YouTube clip ends and the next one begins, and the time interval can be very short. All this switching can stress electronics and speakers. To get around this, the concept of an *active state* covering a sequence of play sessions is introduced. An active state begins when a play session starts. When the play session ends, the system stays in the active state for a period called the `active_state_timeout`, 10 seconds by default. If another play session starts before that timeout elapses, the system remains in the active state; otherwise the system leaves the active state. * A new `alsa`-only `disable_standby_mode` setting, for controlling the Disable Standby feature, can be set to: `always`, `while_active` or `never`. The `always` setting is recommended for systems where the output device is dedicated to Shairport Sync. The "Disable Standby" state iself can be set or cleared via the D-Bus interface `DisableStandby` property. +* A new command-line option `-u` to direct logging to STDERR as opposed to the system log. Useful when you compile shairport sync without libdaemon, using the `--without-libdaemon` configuration option. +* Use CLOCK_RUNTIME in place of CLOCK_MONOTONIC when doing synchronisation timing using the alsa library prior to 1.0.28. Necessary for compabibility with OpenWRT Barrier Breaker. **Enhancements** -* The volume-control software has been completely rewritten. From a user's point of view, the result should be a much smoother response to volume contol changes, free from artefacts. It is now also possible to combine the hardware mixer and the software attenuator in two ways -- giving priority to the software mixer or giving priority to the hardware mixer. +* The volume-control software has been completely rewritten. From a user's point of view, the result should be a much smoother response to volume contol changes, free from artefacts. It is now also possible to combine the hardware mixer and the software attenuator in two ways -- giving priority to the software mixer or giving priority to the hardware mixer. see the new `volume_range_combined_hardware_priority` setting in the `general` section opf the configuration file. * The muting/unmuting code has been rewritten to be simpler and more consistent. * In the `alsa` backend, new `play()` and `delay()` functions minimise the use of `snd_pcm_recover()` to prevent unnecessary resets of the output DACs. * In the `alsa` backend driver, hardware isn't accessed until the first time it is needed. That is, when Shairport Sync starts up, it no longer needs to access the device momentarily. Instead, it waits for the first use.