Streaming to a CDN or multicast streaming
A Content Delivery Network (CDN) relies on geo-diverse CDN servers to receive and disperse web content to the CDN server closest to the user. The closer the server is to the user, the faster the content is delivered. Streaming your content through a CDN allows you to stream any time, anywhere, regardless of the viewing device and you don't have to worry about maintaining your own video streaming servers on site.
Streaming content to a multicast IP address lets you directly share the stream with multiple viewers on the same LAN. All viewers receive the same stream at the same time. Similar to turning on a radio station where all listeners hear the same music at the same time. Multicasting is useful for training sessions when there is a specific timeframe for the audience to view the content live.
With Pearl-2, you can publish to several different CDNs or other streaming destinations simultaneously. Streaming a channel to CDNs and multicast streaming is available only when the H.264 codec is configured as the channel encoding, see Configure video encoding.
|Publishing Options||Use this option to...|
|Content Distribution Network (CDN)||
Stream web content to many viewers on different Content Delivery Networks simultaneously to any geographical location. Using a CDN to host your broadcast is highly scalable and saves you from having to purchase and maintain your own servers to host and deliver video content.
Using one or more CDNs to stream live content allows you to reach a large geographically diverse audience and because CDNs perform format conversion, the stream is platform independent.
Streaming protocols supported include: SRT (push), HLS (push), MPEG-DASH (push), RTMP/RTMPS.
For more information about streaming to a CDN, see Streaming to servers, CDNs, and other devices.
This delivery method relies on network equipment that supports multicasting and is usually used on high bandwidth corporate LANs and not on Internet-based architectures.
Multicasting is what's typically used to stream video and audio to an IP TV or set-top box playlist. If you're streaming over a Gigabit Ethernet network to a 10/100 Mbps set-top box that is dropping frames, you can limit the stream's bandwidth, see Set up traffic shaping.
Multicast streaming protocols supported include: MPEG-TS USP, MPEG-TS RTP/UDP, and RTP/UDP.
For more information about using multicasting for streaming your content, see Multicast streaming
To stream video outside of your LAN, use a CDN or configure port forwarding on your router. Consult your Network Administrator to set up port forwarding.
You can even use an XML profile to setup streaming if the CDN supports that. By default, no streaming is configured for the channels configured on Pearl-2.
In addition to streaming, Pearl-2 can ingest streams as input sources. The following ingest streams formats are supported:
- SRT (push)
- RTSP announce
- RTMP (push)
Publishing to a CDN
When you publish a stream to a CDN provider, make sure you use a streaming protocol that the CDN supports. Contact your CDN for a list of supported streaming protocols and audio codecs they support.
To publish content to a CDN provider, ensure you have:
- the URL (or path) to the mount point or an XML configuration file (provided by the CDN provider)
- the supported transport protocols, audio codecs, and any other settings like key frame rates and bit rates recommended by the CDN provider
- select the H.264 codec from the channel's Encoding page
You can control when streaming to a CDN is enabled by using the Admin panel or the touch screen. See Start and stop streaming to a CDN.
You can also test how your content is streamed by sending your content to Epiphan’s CDN. For a list of Epiphan’s preferred CDN providers, see: https://www.epiphan.com/partners/cdn-partners/.