The supported codecs are: H264, H265, AAC, MP3, and AC-3.
Flussonic Media Server supports access via DASH to live streams, VOD files, and DVR (catchup and timeshift).
DASH uses a manifest file for transmitting information about a requested stream. To keep it simple, we call it "playlist" here, but the accurate word is DASH manifest.
On this page:
When your stream is already recorded on a server with our DVR, you can play video via DASH if you know the beginning and ending time of telecast, for example, from EPG.
URLs for playing video from archives will be like this:
Such a URL will give a list of segments starting from UTC 1362504585 (2013, March, 5th, 17:29:45 GMT) and for one hour forward (3600 seconds).
If you have more than one language or more than one bitrate, you will get an adaptive stream with the possibility to select the audio track.
Flussonic Media Server has a special playlist "rewind-N.mpd" with a wide sliding window that allows you to rewind DASH streams and pause them for many hours.
Here 7200 is the duration of the DASH manifest in seconds, so your clients will be able to pause the stream for up to 2 hours or rewind to the start of a TV show without using catchup URLs.
Also, there is a playlist in which you can receive a live stream and rewind up to a specified time: "archive-N-now.mpd", where N - is a Unix timestamp of the moment to which users can rewind the stream.
Note. This information is useful if you need a static manifest for playing DVR over DASH of a currently live stream.
- 1350274200 — the start time of a requested chunk in DVR archive.
- 4200 — how many seconds to play back.
Imagine you have streams that are broadcasted live and recorded to DVR. For playing them back from the archive, the requested fragment might end in the future where no broadcast exists yet.
Flussonic allows you to choose the type of manifest (playlist) to send to clients when playing back DVR of such live streams over DASH. A DASH manifest can be static or dynamic (updatable).
By default, Flussonic updates the manifest along with live broadcast progress, which means the manifest is dynamic. When the real time reaches the specified moment when the archive fragment must end, the manifest automatically becomes static because all info about the stream is received and there is no need to update the manifest any longer. In some cases it might be better to use a static manifest.
To specify the type of a manifest, use the
dynamic=false. Flussonic Media Server will generate a static manifest. In a player, an archive will be played the same way as a file. The manifest will contain information about the requested time range and will not be updated during playback.
dynamic=auto. This is the default behavior, so this parameter can be omitted. First, Flussonic creates a dynamic manifest (and updates it while a live broadcast is going in parallel with DVR playback). Then Flussonic changes the manifest to static – it happens when the live broadcast reaches the end time of the requested DVR fragment.