Streaming servers are set up and configured explicitly to deliver your webcasts. They enable transcoding for adaptive bit rate streaming so that your live event is made available in any network and on any device. In addition, the streaming server is responsible for the cue point injections, which are set by an operator during a live stream.
A configuration of the streaming server is only necessary if you are using your own server. By default, movingimage offers this service for you, i.e. we make available our streaming server. You can simply select the setup from the list of streaming servers (see below). |
The movingimage Webcast supports Wowza Live (Origin) as the sole source of playout information. It separates ingest streams from playback streams.
To create a streaming server, perform the following steps:
Click the [Create] button to open a form.
All fields are required, except for Backup Ingest API Endpoint, Backup Ingest Username, Backup Ingest Password. These three fields are only required if you intend to use a second, backup Wowza instance. |
The Streaming Variables are used within the URL Templates to construct the live and DVR playout URLs.
These options control which transcoded qualities will be passed to the Akamai network. Select only the options you need and configure the same qualities within the Wowza transcoder settings. |
Customers using the movingimage Wowza platform will use these predefined transcoder settings to create adaptive streams:
|
Only ingests with a framerate of up to 30fps for live streaming are supported. |
The URL Templates construct the live and DVR playout URLs. There are default templates the Wowza playout source, although you can modify them to match your environment.
If you want streaming quality equal to and lower than 1080p for Wowza Live, use this HRS URL template (note that this is default setting for streaming servers): https://$wowzahost$/$appname$/ngrp:$streamname$_$language$_all/master.m3u8 If you want streaming quality equal to and lower than 720p (i.e. 360p, 480p, 720p), use the following HRS URL template: |
This table briefly describes the settings found within the Streaming Server
General Information: | |
---|---|
Name: | This name will appear in the Live panel within the webcast configuration when choosing a streaming server. |
Ingest Endpoints: | |
Primary Ingest API Endpoint: | The URL to the primary Wowza API endpoint (e.g. "http://primary.wowza/api"). |
Primary Ingest Username: | A username that can connect to the primary Wowza API endpoint. |
Primary Ingest Password: | The password for the above username. |
Backup Ingest API Endpoint: | The URL to the backup Wowza API endpoint (e.g. "http://backup.wowza/api"). This optional field allows you to set up a backup API, which will make an extra set of recordings of your live stream, a primary set and a backup set. For example, imagine you have a webcast with two language streams, and you set it up to upload to a VideoManager after the conclusion of the live stream. If you have also set up a backup API, four video files should be uploaded to your VideoManager: one for each language created from the primary API, and one for each language created from the backup API. |
Backup Ingest Username: | A username that can connect to the backup Wowza API endpoint. |
Backup Ingest Password: | The password for the above username. |
These fields below are the templates used to generate URLs for each webcast. Here you can use placeholders to construct your streaming URLs. The placeholders will be filled in with the items in the "Default Variables" pane (see details below). You can add a $language$ placeholder if you intend to stream webcasts in multiple languages; this allows creation of different URLs for each language you choose to support. | |
Streaming Variables: | |
Wowza Application Name: | The "Application Name" as used in the Wowza configuration. The value here will be used in Streaming URL templates wherever the $appname$ placeholder is set. |
Wowza Host: | The value here will be used in Streaming URL templates wherever the $wowzahost$ placeholder is set. This could be the same server as the primary Wowza server (in the Ingest Endpoints), or a proxy / caching server in front of the Wowza server. |
Default Language: | The default language that you intend Webcast streams to use. New webcasts will automatically create a language set using this language. The short country code (e.g. en, de) will be used in the templates wherever the $language$ placeholder is set. |
Stream Name: | Note that this is not an editable field in this edit pane or any other. Each webcast is given a unique stream name when it is created (e.g. "59196e2d2d85b47d5c1a0c8f"). It will appear in the templates wherever the $streamname$ placeholder is set. |
URL Templates | |
URL templates are used to generate the streaming URLs for each webcast. Here you can use placeholders to construct your streaming URLs. The placeholders will be filled in with the items in the "Streaming Variables" pane (see details above). You can add a $language$ placeholder if you intend to stream webcasts in multiple languages; this allows creation of different URLs for each language you choose to support. | |
HLS URL: | The URL template for the live stream (e.g. "https://$wowzahost$/$appname$/$streamname$_$language$/master.m3u8") |
HLS DVR URL: | The URL template for the post-live DVR stream (e.g. "https://$wowzahost$/$appname$/$streamname$_$language$Dvr/playlist.m3u8?DVR") |
Template / Variable Usage Example: | |
Imagine you've just created a webcast and it's automatically generated stream name is, "59196e2d2d85b47d5c1a0c8f". If the following settings (using Akamai CDN playout) had been configured here... * | |
HLS URL Template: | https://$wowzahost$/$appname$/$streamname$_$language$Dvr/playlist.m3u8?DVR |
Default Language: | English (en) |
Stream Name: | 59196e2d2d85b47d5c1a0c8f (note: this is automatically generated and can not be modified) |
Setting a default Streaming Server configuration means that it will be selected automatically when creating a new Webcast.