File: stereotool.md

package info (click to toggle)
liquidsoap 2.3.2-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 11,912 kB
  • sloc: ml: 67,867; javascript: 24,842; ansic: 273; xml: 114; sh: 96; lisp: 96; makefile: 26
file content (54 lines) | stat: -rw-r--r-- 3,148 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# Stereotool support

Starting with version `2.2.0`, liquidsoap supports the shared library distributed by [Thimeo Audio Technology](https://www.thimeo.com/stereo-tool/)
using the `stereotool` operator (and `track.audio.stereotool` for the low-level, track-specific equivalent).

This feature is enabled in all release builds of liquidsoap starting with `rolling-release-v2.2.x` and should be enabled if you compile liquidsoap
with the optional `ctypes-foreign` opam module installed.

The operator can replace the use of the stereotool binary in your script and offers multiple benefits. In particular, it has a **very low latency**
compared to using the binary and also operates synchronously.

The operator should be quite easy to use. Here's an example:

```liquidsoap
# Define a source
s = ...

# Apply stereotool to it:
s = stereotool(
  library_file="/path/to/stereotool/shared/lib",
  license_key="my_license_key",
  preset="/path/to/preset/file",
  s
)
```

That's it! You can apply as many `stereotool` operators as you wish and at any stage in the script, thanks
to its synchronous nature. However, a current limitation is that **the processed audio signal is slightly delayed**.

This is because the operator has an internal processing buffer. We do plan on delaying metadata and track marks
to match this latency but this has not yet been implemented and will probably have to wait for the `2.3.x` release cycle.

This means that, until then, track switches and metadata updates might happen slightly earlier than the corresponding
signal. We're talking about `50ms` to `100ms` earlier, though, so that might not be a super big deal.

For the same reason, the source returned by `stereotool` is an _audio-only_ source. Otherwise, other concurrent tracks
such as video and etc would be slightly out of sync. If you need to use the operator in this kind of situation, you
might want to use a `ffmpeg` filter to e.g. adjust the video's PTS to match the audio delay.

In such case, you can refer to the `latency` method that is available on the source returned by the operator which
should indicate the delay to compensate from the processed audio signal.

The operator's `preset` parameter has a companion `load_type` parameter that can optionally be used to only load a subset of
the preset. You might refer to the upstream documentation if you need to use it.

Lastly, `stereotool` is a **proprietary software**. While we actively promote open source, we also want to meet
our users where they are and, for a lot of them, this means supporting the sound processing provided by the tool.

However, to use it, you will need a license. Using the operator without the proper license will _not_ result in an
error in your script but the audio signal might have spoken text and/or beeps added to it.

Using the operator with an invalid license will be reported in the logs. You might also use the `valid_license`
method available on the source returned by the operator, which returns `false` if the license is invalid. In this case, the `unlincensed_used_features`
method returns a string indicating which unlicensed features are being used.