Skip to content

Commit 9ce753e

Browse files
committed
FAQ.md: Added "What can I do if some files or a remote playlist simply _don’t play?_"
1 parent a66489b commit 9ce753e

File tree

1 file changed

+32
-1
lines changed

1 file changed

+32
-1
lines changed

FAQ.md

+32-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
date: 2024-06-23
2+
date: 2024-06-26
33
author: Matthias C. Hormann (Moonbase59)
44
---
55
# FAQ – Frequently Asked Questions
@@ -25,6 +25,7 @@ author: Matthias C. Hormann (Moonbase59)
2525
- [Why should I use `check_autocue_setup`, and what does it do?](#why-should-i-use-check_autocue_setup-and-what-does-it-do)
2626
- [What are good first steps to use Autocue in my own Liquidsoap script?](#what-are-good-first-steps-to-use-autocue-in-my-own-liquidsoap-script)
2727
- [What will happen when I switch to the upcoming Liquidsoap 2.3.0?](#what-will-happen-when-i-switch-to-the-upcoming-liquidsoap-230)
28+
- [What can I do if some files or a remote playlist simply _don’t play?_](#what-can-i-do-if-some-files-or-a-remote-playlist-simply-dont-play)
2829
<!-- Generated by gh-toc, https://moonbase59.github.io/gh-toc/ -->
2930
<!-- ToC end -->
3031

@@ -322,3 +323,33 @@ Most certainly, as of 2024-06-23…
322323
See also:
323324

324325
- https://github.com/savonet/liquidsoap/pull/3931#issuecomment-2184937173
326+
327+
328+
## <a name="what-can-i-do-if-some-files-or-a-remote-playlist-simply-dont-play"></a>What can I do if some files or a remote playlist simply _don’t play?_ <a href="#toc" class="goToc">⇧</a>
329+
330+
This most often happens with _large files_, _large remote files_, and files that are _hard to analyse_ because they’re already clipping (too loud).
331+
332+
Check your Liquidsoap log for entries like
333+
334+
```
335+
2024/06/26 10:01:43 [request:2] Time limit exceeded by 16.00 secs!
336+
```
337+
338+
This can happen if the _downloading/preparing is slow_, or the _files are large_ (recordings, prerecorded shows, DJ sets, podcasts) or _hard to analyse_. These factors are out of our control. If a request timeout happens, the file will simply _not be played_, and the _next available used_.
339+
340+
In such cases, I suggest to _pre-tag_ files using the `cue_file` tool, but this might not always be possible.
341+
342+
In the above case, I’d suggest _increasing the Autocue timeout slightly_ from the default `60.0` seconds to `60` + timeout shown (`16.0`) + a small "safety margin", say another `10` seconds, making for `86` seconds. Let’s round that up to `90` seconds.
343+
344+
In AzuraCast’s _Edit Liquidsoap Configuration_, in the _second input box_, add this parameter:
345+
```
346+
settings.autocue.cue_file.timeout := 90.0
347+
```
348+
349+
**Note:** Please do _not_ use arbitrary large values like `480` "just to prevent it happening"! Doing so could well have adverse side effects.
350+
351+
_Save Changes_ and _Restart Broadcasting_.
352+
353+
Keep watching your logs for timeouts, just in case even larger files arrive. You can search for `Time limit exceeded` to quickly find such entries in the log.
354+
355+
If the above should _not_ help, you should look for a _faster/higher bandwidth connection_ to the source you download the files from. To be able to _work_ with a file, Liquidsoap has to download a complete copy first, before autocueing and playout can begin.

0 commit comments

Comments
 (0)