From 0ccbdae555c953d068df78f5ca223168ee822875 Mon Sep 17 00:00:00 2001 From: David Trattnig <david.trattnig@o94.at> Date: Thu, 4 Jun 2020 10:50:29 +0200 Subject: [PATCH] Updated schedul config. --- configuration/sample-development.engine.ini | 20 ++++++++++++-------- configuration/sample-docker.engine.ini | 20 ++++++++++++-------- configuration/sample-production.engine.ini | 20 ++++++++++++-------- 3 files changed, 36 insertions(+), 24 deletions(-) diff --git a/configuration/sample-development.engine.ini b/configuration/sample-development.engine.ini index cd4fe862..3808b251 100644 --- a/configuration/sample-development.engine.ini +++ b/configuration/sample-development.engine.ini @@ -63,16 +63,20 @@ api_port=3333 [scheduling] # How often should the calendar be fetched in seconds. This determines the time of the last changes applied, before a specific show aired -fetching_frequency=3600 -# How many seconds before the actual schedule time the entry should be pre-loaded. Note to provide enough timeout for +fetching_frequency=300 +# How many seconds before the actual schedule time the entry should be pre-rolled. Note to provide enough timeout for # contents which take longer to load (big files, bad connectivity to streams etc.) -preload_offset=60 - -# Sometimes it might take longer to get a stream connect. Here you can define a viable length. -# But note, that this may affect the preload time (see `preload_offset`), hence affecting the +preroll_offset=15 +# Max seconds before an new/updated/removed schedule is accepted. Its important that this value +# is considerable higher than the `preroll_offset` plus any additional time for pro-active fallback +# handling, being able to avoid issues with concurrent changes or timings. +scheduling_window_offset=120 + +# Sometimes it might take longer to get a stream connected. Here you can define a viable length. +# But note, that this may affect the preroll time (see `preroll_offset`), hence affecting the # overall playout, it's delays and possible fallbacks -stream_connect_retry_delay=1 -stream_connect_max_retries=10 +input_stream_retry_delay=1 +input_stream_max_retries=10 input_stream_buffer=3.0 # sets the time how long we have to fade in and out, when we select another mixer input diff --git a/configuration/sample-docker.engine.ini b/configuration/sample-docker.engine.ini index 5456727d..3eea6c06 100644 --- a/configuration/sample-docker.engine.ini +++ b/configuration/sample-docker.engine.ini @@ -63,16 +63,20 @@ api_port=3333 [scheduling] # How often should the calendar be fetched in seconds. This determines the time of the last changes applied, before a specific show aired -fetching_frequency=3600 -# How many seconds before the actual schedule time the entry should be pre-loaded. Note to provide enough timeout for +fetching_frequency=300 +# How many seconds before the actual schedule time the entry should be pre-rolled. Note to provide enough timeout for # contents which take longer to load (big files, bad connectivity to streams etc.) -preload_offset=60 - -# Sometimes it might take longer to get a stream connect. Here you can define a viable length. -# But note, that this may affect the preload time (see `preload_offset`), hence affecting the +preroll_offset=15 +# Max seconds before an new/updated/removed schedule is accepted. Its important that this value +# is considerable higher than the `preroll_offset` plus any additional time for pro-active fallback +# handling, being able to avoid issues with concurrent changes or timings. +scheduling_window_offset=180 + +# Sometimes it might take longer to get a stream connected. Here you can define a viable length. +# But note, that this may affect the preroll time (see `preroll_offset`), hence affecting the # overall playout, it's delays and possible fallbacks -stream_connect_retry_delay=1 -stream_connect_max_retries=10 +input_stream_retry_delay=1 +input_stream_max_retries=10 input_stream_buffer=3.0 # sets the time how long we have to fade in and out, when we select another mixer input diff --git a/configuration/sample-production.engine.ini b/configuration/sample-production.engine.ini index d2d7be2c..a6a93454 100644 --- a/configuration/sample-production.engine.ini +++ b/configuration/sample-production.engine.ini @@ -63,16 +63,20 @@ api_port=3333 [scheduling] # How often should the calendar be fetched in seconds. This determines the time of the last changes applied, before a specific show aired -fetching_frequency=3600 -# How many seconds before the actual schedule time the entry should be pre-loaded. Note to provide enough timeout for +fetching_frequency=300 +# How many seconds before the actual schedule time the entry should be pre-rolled. Note to provide enough timeout for # contents which take longer to load (big files, bad connectivity to streams etc.) -preload_offset=60 - -# Sometimes it might take longer to get a stream connect. Here you can define a viable length. -# But note, that this may affect the preload time (see `preload_offset`), hence affecting the +preroll_offset=15 +# Max seconds before an new/updated/removed schedule is accepted. Its important that this value +# is considerable higher than the `preroll_offset` plus any additional time for pro-active fallback +# handling, being able to avoid issues with concurrent changes or timings. +scheduling_window_offset=180 + +# Sometimes it might take longer to get a stream connected. Here you can define a viable length. +# But note, that this may affect the preroll time (see `preroll_offset`), hence affecting the # overall playout, it's delays and possible fallbacks -stream_connect_retry_delay=1 -stream_connect_max_retries=10 +input_stream_retry_delay=1 +input_stream_max_retries=10 input_stream_buffer=3.0 # sets the time how long we have to fade in and out, when we select another mixer input -- GitLab