HLS Output
Starting with liquidsoap 1.4.0, it is possible to send your streams as HLS output.
The main operator is output.file.hls. Here’s an example using it, courtesy of srt2hls:
aac_lofi = %ffmpeg(format="mpegts",
%audio(
codec="aac",
channels=2,
ar=44100
))
aac_midfi = %ffmpeg(format="mpegts",
%audio(
codec="aac",
channels=2,
ar=44100,
b="96k"
))
aac_hifi = %ffmpeg(format="mpegts",
%audio(
codec="aac",
channels=2,
ar=44100,
b="192k"
))
streams = [("aac_lofi",aac_lofi),
("aac_midfi", aac_midfi),
("aac_hifi", aac_hifi)]
def segment_name(~position,~extname,stream_name) =
timestamp = int_of_float(gettimeofday())
duration = 2
"#{stream_name}_#{duration}_#{timestamp}_#{position}.#{extname}"
end
output.file.hls(playlist="live.m3u8",
segment_duration=2.0,
segments=5,
segments_overhead=5,
segment_name=segment_name,
persist_at="/path/to/state.config",
"/path/to/hls/directory",
streams,
source)Let’s see what’s important here:
streamsdescribes the encoded streams. It’s a list of:(stream_name, encoder).stream_nameis used to generate the corresponding media playlists. Encoders can be any encoder supported by liquidsoap. However, the HLS RFC limits the list of possible codecs tomp3andaac. Furthermore, for the best possible compatible, it is recommended to send data encapsulated in aMPEG-TSstream. Currently, the only encoder capable of doing this in liquidsoap is%ffmpeg.persist_atis used to allow liquidsoap to restart while keeping the existing segments and playlists. When shutting down, liquidsoap stores the current configuration atpersist_atand uses it to restart the HLS stream when restarting.segmentsandsegments_overheadare used to keep track of the generated segments. Each media playlist will contain a number of segments defined bysegmentsand an extra set of segments, defined bysegments_overhead, is kept past the playlist size for those listeners who are still listening on outdated segments.
There are more useful options, in particular on_file_change, which can be used for instance to sync up your segments and playlists to a distant storage and hosting service such as S3.
Liquidsoap also provides a output.harbor.hls and output.harbor.hls.ssl which allow to serve HLS streams directly from liquidsoap. Their options should be the same as output.file.hls, except for harbor-specifc options port and path. It is not recommended for listener-facing setup but can be useful to sync up with a caching system such as cloudfront.