Streaming Media

Streaming Media on Facebook Streaming Media on Twitter Streaming Media on LinkedIn
 
Upcoming Industry Conferences
Streaming Media East [2-3 June 2020]
Esport & Sports Streaming Summit [2 June 2020]
OTT Summit [2-3 June 2020]
Video Engineering & Technology Summit [2-3 June 2020]
Enterprise & Education Video Summit [3 June 2020]
Content Delivery Summit [1 June 2020]
Past Conferences
Streaming Media West [19-20 Nov 2019]
Esport & Sports Streaming Summit [19-20 Nov 2019]
OTT Leadership Summit [19-20 Nov 2019]
Video Engineering Summit [19-20 Nov 2019]
Live Streaming Summit [19 Nov 2019]

Tutorial: Delivering to Internet and Intranet Viewers with the DVEO Magnus Anytime Family of Products

This tutorial explores the workflow and application of the DVEO Magnus Anytime family of products, which combine high-density H.264 encoding and an integrated streaming server for multiple screen delivery both inside and outside your firewall.

Configuring the System

A typical use-case scenario would be a stadium or similar facility that needs to send one set of streams to a CDN for internet delivery, while delivering to mobile viewers internally (Figure 7, below).

Figure 7. A setup for a typical Magnus Anytime use case at a baseball park.

Here’s how you might configure the system to meet that use case. You start by defining the streams in the Stream Setup tab (Figure 4). In the project we’re producing for this tutorial we’re using only a single input, though the capture hardware on this system can handle up to 4 inputs (Figure 8, below).

Figure 8. Input Setup options.

We’re building two groups of adaptive streams; the first is configured for RTMP push for delivery to the CDN for Internet viewing (Figure 9, below). Throughput varies by system configuration, but the typical system can convert up to eight 1080p inputs into eight adaptive groups of up to ten files each.

Figure 9. The first configured adaptive stream.

The unit provides good control over general and H.264-specific encoding parameters. Tweakers will appreciate the advanced options available (Figure 10, below).

Figure 10. Advanced encoding options for H.264 adaptive streaming.

We’re sending the second group of files to the Helix server for transmuxing for internal distribution. You can configure these as desired but you should format them as an MPEG-2 transport stream and push them to the Helix server via UDP (Figure 11, below).

Figure 11. Formatting the output to the Helix server for internal use.

The server itself implements a full version of RealNetworks’ Helix Universal Server, with support for HLS, DASH, multiple flavors of RTSP, Server Playlists, and Stream Bookmarking (Figure 12, below).

Figure 12. Helix delivery options mirror those in Real Networks’ Helix Universal Server.