On-Demand Streaming
HTTP Large
Smooth Streaming
The On-Demand Smooth Streaming feature provides adaptive streaming of a previously recorded event. In order for clients to take advantage of adaptive streaming, they will need to request the server manifest file from a server that is publishing the archived video as a stream. The requested file chunks will be cached on that POP creating an environment where future similar requests are served at an even quicker rate.
In order to provide smooth streaming capabilities to your clients, you should perform the following steps:
- Encode your video into a Smooth Streaming compatible video format (i.e., Smooth Streaming presentation).
- Decide whether you would like to use our on-demand smooth streaming service or your own IIS server. This publishing location, which is either a server on our CDN or your own IIS server, is the ingestion point for your encoded video. The location where you can store your video depends on the selected ingestion point.
- CDN: Make sure that On-Demand Smooth Streaming feature has been enabled and that the desired smooth stream presentation has been uploaded to CDN storage.
- IIS Server: Make sure that the presentation is located in an IIS virtual directory. Additionally, a customer origin configuration that points to that IIS virtual directory is required.
- If you would like to mask the CDN URL that points to your media, then you should create an edge CNAME for it. You will also need to define the corresponding CNAME record through your DNS service provider.
- Point your Smooth Stream compatible player to the server manifest file for the desired smooth stream using a CDN or an edge CNAME URL.
Note: On-Demand Smooth Streaming does not transmux video into an M3U8 format. As a result, an iOS device cannot stream content through On-Demand Smooth Streaming. However, if you have properly segmented/packaged the desired content and uploaded it to CDN storage or a customer origin server, you can stream it to iOS devices using a standard CDN URL or edge CNAME URL (e.g., http://wpc.0001.{Base Domain}/800001/videos/playlist.m3u8).