Flussonic Media Server documentation


Data Source Types

A source is from where Flussonic receives a stream of video data. A source can be an IP camera, a satellite headend, an HTTP server, and so on. To specify the source of a stream, you need to know its address and the video protocol over which Flussonic receives video data, in other words, you need to know the URL.

To send video data between Flussonic Media Servers we recommend using Flussonic's internal protocol M4F. This protocol is ideal for setting up replication of a DVR archive or for re-streaming individual streams in a cluster.

Important. Flussonic Media Server does not support the http data source type, and specifying an URL as http://host/path will result in an error. You should use a URL that explicitly specifies a video protocol — HTTP MPEG-TS, HLS, or any other protocol supported by the system. This page includes examples of URLs for various protocols.

Important. Do not specify a file on the server as a source. Broadcasting of files is configured differently from live sources. Learn more in VOD file broadcasting.


We recommend using M4F to send video between Flussonic servers.

  • m4f://hostname:port/stream — syntax
  • m4f://flussonic.example.com/channel_01 — example

About the M4F protocol


  • tshttp://hostname:port/stream — syntax (ingest over HTTP)
  • tshttps://hostname:port/stream — syntax (ingest over HTTPS)
  • tshttp:// — example of a URL

An HTTP MPEG-TS data source is, for example, VLC.


  • udp:// — multicast URL
  • udp:// — ingest of a multicast stream through the specified interface
  • udp:// — unicast URL


A TCP MPEG-TS data source:

  • tstcp://


  • hls://HOSTNAME/PATH/TO/MANIFEST.m3u8 — syntax
  • hls:// — example of an HLS URL
  • hls://example.com/news/index.m3u8 — example of an HLS URL.
  • hlss://HOSTNAME/PATH/TO/MANIFEST.m3u8 — syntax of ingest over HTTPS
  • hls2://example.com/news/index.m3u8 — ingest of a multi-bitrate HLS source.
  • hlss2://example.com/news/index.m3u8 — ingest of a multi-bitrate HLS source over HTTPS.

A generic HTTP server could serve a pre-packaged HLS manifest and chunks with video data. In the case where the manifest file is static Flussonic would not be able to ingest HLS stream. Flussonic Media Server will wait for new segments to appear until till timeout, then it will restart this source and try to fetch again the existing segments.

It is possible to validate a playlist by its modification time, but this method is not very reliable. By default, Flussonic Media Server has enabled feature called "stalled check". Here, the server downloads only the new segments after the first fetch, making sure that no segments from first fetch will be used.

Sometimes you would want to make sure that your source is not a generic HTTP server, but a streaming server that will not serve outdated segments and you want to enable HLS source in ondemand configuration.

To make sure that your streaming server would not serve outdated segments in ondemand you should use this option.

Stale protection option affects stream startup time, when this option is enabled Flussonic Media Server will wait for at least 2-3 new segments before making stream available.

You can disable stale protection with this directive: skip_stalled_check=true;

Use this feature at your own risk — with it enabled, old content might be repeated over and over.

stream ort {
  url hls://source:8080/stream/index.m3u8 skip_stalled_check=true;

For HLS sources you can set the user_agent option:

hls://source:8080/stream/index.m3u8 user_agent="Custom Agent v1.2"


When receiving a stream from an RTSP camera, you should include the camera's IP address and the path to its RTSP stream in the URL. The path is not always published in the camera's user manual. You might need to contact the camera's vendor or manufacturer to get this information.

  • rtsp://hostname/path — syntax
  • rtsp://user:password@ip/path — URL with authorization
  • rtsp2://hostname/path — the rtsp2 protocol instructs Flussonic to transcode the audio stream into AAC. Learn more
  • rtsp:// — example of an RTSP URL


  • rtmp://hostname/application/stream
  • rtmp://

The RTMP protocol requires that an RTMP URL has at least two segments. The first segment (application) is by default used as the name of the RTMP application.

If the name of the RTMP application on the server consists of more than one segments, add two slashes to the URL in order to explicitly divide the RTMP application and stream name.

MPEG2-TS options

When working with tshttp://, udp://, and tstcp:// sources, you can use MPEG2-TS specific options.

Ingesting specific MPEG-TS programs and PIDs:

stream ort {
  url tshttp://source:8080/stream program=21 pids=45,46,47;

Disabling subtitles

By default, Flussonic Media Server always ingests subtitles from published streams. This is true for streams with either static or dynamic names. You don't need to explicitly set the option allow_subtitles=true.

If you do not need subtitles in a stream, set the option allow_subtitles to false:

stream ort {
  url tshttp://source/stream allow_subtitles=false;

Note. For live published streams (streams with dynamic names), subtitles are always ingested and cannot be disabled. Disabling the allow_subtitles option will not work.

Enable bypass of the NIT table:

stream ort {
  url tshttp://source:8080/stream bypass_eit=true;

Enable this option if you want to get EPG data on Flussonic output.

HTTP options

When connecting to a stream over HTTP, you can set the User-Agent HTTP header with the user_agent option:

stream example {
  url tshttp://source:8080/stream user_agent="VLC"

To specify a custom HTTP header, for example 'Referer':

stream example {
  url tshttp://source:8080/stream header.Referer=https://flussonic.com;


  • timeshift://STREAM/3600

The timeshift:// is a scheme that allows you to create a new stream identical to the stream but with a predefined delay. In this example the delay is 3600 seconds (one hour). It is delivered from the recorded archive.


  • shout://source:8080

The shout:// scheme is used to ingest SHOUTcast and ICEcast internet radio streams.


  • mixer://stream1,stream2

Use the scheme mixer:// to mux video from the first specified stream with audio from the second one. Learn more


  • mosaic://cam1,cam2,cam3,cam4?fps=20&preset=ultrafast&bitrate=1024k&size=340x240&mosaic_size=4

Use the scheme mosaic:// to create a mosaic — a combination of multiple video streams in one. Learn more