Skip to content

Commit

Permalink
FAQ.md: Added "What can I do if some files or a remote playlist simpl…
Browse files Browse the repository at this point in the history
…y _don’t play?_"
  • Loading branch information
Moonbase59 committed Jun 26, 2024
1 parent a66489b commit 9ce753e
Showing 1 changed file with 32 additions and 1 deletion.
33 changes: 32 additions & 1 deletion FAQ.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
date: 2024-06-23
date: 2024-06-26
author: Matthias C. Hormann (Moonbase59)
---
# FAQ – Frequently Asked Questions
Expand All @@ -25,6 +25,7 @@ author: Matthias C. Hormann (Moonbase59)
- [Why should I use `check_autocue_setup`, and what does it do?](#why-should-i-use-check_autocue_setup-and-what-does-it-do)
- [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)
- [What will happen when I switch to the upcoming Liquidsoap 2.3.0?](#what-will-happen-when-i-switch-to-the-upcoming-liquidsoap-230)
- [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)
<!-- Generated by gh-toc, https://moonbase59.github.io/gh-toc/ -->
<!-- ToC end -->

Expand Down Expand Up @@ -322,3 +323,33 @@ Most certainly, as of 2024-06-23…
See also:

- https://github.com/savonet/liquidsoap/pull/3931#issuecomment-2184937173


## <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>

This most often happens with _large files_, _large remote files_, and files that are _hard to analyse_ because they’re already clipping (too loud).

Check your Liquidsoap log for entries like

```
2024/06/26 10:01:43 [request:2] Time limit exceeded by 16.00 secs!
```

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_.

In such cases, I suggest to _pre-tag_ files using the `cue_file` tool, but this might not always be possible.

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.

In AzuraCast’s _Edit Liquidsoap Configuration_, in the _second input box_, add this parameter:
```
settings.autocue.cue_file.timeout := 90.0
```

**Note:** Please do _not_ use arbitrary large values like `480` "just to prevent it happening"! Doing so could well have adverse side effects.

_Save Changes_ and _Restart Broadcasting_.

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.

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 comments on commit 9ce753e

Please sign in to comment.