#1: Preparing your content


Checklist for your content

  1. Content has to be available for broadpeak.io. Check your firewall, and whitelist the IPs of broadpeak.io if necessary.
  2. If you are mixing linear channels, they should be synchronized to the same clock, preferably broadpeak.io's clock. More information here.
  3. Check that your manifests are compliant with broadpeak.io here. We recommend that the different contents of your virtual channel are encoded and prepared in the same way (mandatory for HLS).
  4. Define your streams as sources in broadpeak.io.

Whether you are creating new outputs from your packager for this application or using existing sources, this section will help you make sure that your Virtual Channel application can run successfully.

In broadpeak.io, you must define your Sources before anything else.
You have the option to define Sources directly via the web application UI, or by using the API.

For more information on defining Sources, please see Understanding how to use Broadpeak.io. A Source represents only one output. It s also called an adaptation stream, or variant. You can have a single channel, but different outputs to address different user or device segmentations. Each of these outputs would be a Source in broadpeak.io. Even easier, a streaming link/url from your packager = a Source in broadpeak.io.


1. Defining your content as Source

Whether you do it through the web UI or the API, you need to create a new Source with the following attributes:

Live stream

Source name: we also suggest you to give it a meaningful name so that you can recognize your replacement content as such when needed, such as "MyReplacementStream_HLSv4_ts"


Video on Demand content is called Asset in broadpeak.io . Asset and Live sources share the same parameters. At this point broadpeak.io does not check that the specified URL provides the right type of manifests, but this may change in the near future.

Asset sources may be used as slot-specific replacement content in a Virtual Channel application

Image slate

Please contact the customer success team who will help you implement this.
You can contact us directly via the chat, or email us at [email protected].

MPEG-DASH Manifests

To make sure your MPEG-DASH streams are supported by broadpeak.io, we invite you to consult the following section: Input Streaming Formats

It is recommended that resolutions and codecs be alike between original and replacement sources - but not mandatory. The protocol allows easily to have different AdaptationSets and Representations from a DASH Period to another.

HLS manifests

To make sure your HLS streams are supported by broadpeak.io, please see the Input Streaming Formats section.

In HLS, players are more sensitive to codecs or resolution change within the same stream. For this reason, manifest contextualization can be successful only if the original and the replacement content are prepared in the same way. For more information about HLS Variant matching rules, see the Understanding Broadpeak.io behavior section.

2. Streams must be available from broadpeak.io

Your streams must always be available from broadpeak.io. If you are using a firewall, make sure that correct inbound and outbound rules are configured so that broadpeak.io can pull the resources using the port that is defined on your streaming endpoint.

If you are using HTTP over custom port, you must specify in the URL the port which needs to be used when defining your content as Source in broadpeak.io. Make sure that your firewall has the correct inbound and outbound rules to allow broadpeak.io to pull the resources using the custom port.
Ex: http://myorigin.com:81/mystream/myoutput/index.m3u8

IP addresses to whitelist:

  • (NEW!)
  • (NEW!)