From: Mike Brady Date: Thu, 28 Feb 2019 17:33:51 +0000 (+0000) Subject: set active state timeout to 10 seconds. Enough for a YouTube movie switch -- 3 or... X-Git-Tag: 3.3RC0~5^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d2e1910fbaad060d27d6cd4b192ef158af68a3db;p=thirdparty%2Fshairport-sync.git set active state timeout to 10 seconds. Enough for a YouTube movie switch -- 3 or 5 seconds doesn't seem to be enough. --- diff --git a/scripts/shairport-sync.conf b/scripts/shairport-sync.conf index 213fd2b0..e2ffeba4 100644 --- a/scripts/shairport-sync.conf +++ b/scripts/shairport-sync.conf @@ -59,7 +59,7 @@ sessioncontrol = // "active" state starts when play begins and ends when the active_state_timeout has elapsed after play ends, unless another play session starts before the timeout has fully elapsed. // run_this_before_entering_active_state = "/full/path/to/application and args"; // make sure the application has executable permission. If it's a script, include the shebang (#!/bin/...) on the first line // run_this_after_exiting_active_state = "/full/path/to/application and args"; // make sure the application has executable permission. If it's a script, include the shebang (#!/bin/...) on the first line -// active_state_timeout = 3; // wait for this number of seconds after play ends before leaving the active state, unless another play session begins. +// active_state_timeout = 10.0; // wait for this number of seconds after play ends before leaving the active state, unless another play session begins. // run_this_if_an_unfixable_error_is_detected = "/full/path/to/application and args"; // if a problem occurs that can't be cleared by Shairport Sync itself, hook a program on here to deal with it. An error code-string is passed as the last argument. // Many of these "unfixable" problems are caused by malfunctioning output devices, and sometimes it is necessary to restart the whole device to clear the problem. diff --git a/shairport.c b/shairport.c index b65db5ef..3a0502ca 100644 --- a/shairport.c +++ b/shairport.c @@ -342,7 +342,7 @@ int parse_options(int argc, char **argv) { // nothing else comes in first. config.fixedLatencyOffset = 11025; // this sounds like it works properly. config.diagnostic_drop_packet_fraction = 0.0; - config.active_state_timeout = 3.0; + config.active_state_timeout = 10.0; config.volume_range_hw_priority = 0; // if combining software and hardware volume control, give the software priority // i.e. when reducing volume, reduce the sw first before reducing the software.