How to create a linear TV channel with Veset Nimbus and AWS Elemental

Guide · Gatis Gailis ·

Content owners use the Veset Nimbus cloud playout platform to originate linear TV channels. Veset Nimbus is a true cloud-based SaaS platform. On the pay-as-you-go plans, no upfront investment or long-term commitment is required from the customer.

The platform’s web-based interface allows users to create new linear TV channels quickly. Veset Nimbus output is a broadcast quality stream that can be delivered to the viewers via OTT and/or traditional distribution channels.

AWS has evolved into a major global cloud platform for media organisations worldwide. With the addition of Elemental in 2015 to its roster of video processing and distribution capabilities, AWS significantly enhanced its relevance to the previously closed and IT-resistant broadcast technology market. The migration of many Elemental capabilities to the AWS Elemental platform, and the further addition of a wide range of services focused on OTT distribution in particular, enhance the capabilities of Veset Nimbus, as it is natively developed for AWS and integrates with AWS Elemental services such as MediaLive.

For example broadcasters use AWS Elemental MediaLive, MediaStore and Amazon CloudFront services to stream their linear TV channels to viewers across the globe using a wide variety of protocols that are layered on top of HTTP.

In this article we will demonstrate how to originate a linear TV channel using Veset Nimbus cloud playout and set up AWS services to deliver it to vMVPD and OTT platforms such as Roku, Hulu, Samsung, Amazon Prime Video and others.

Veset Nimbus

We will ingest a 2 hour movie with captions and several ads. Then we will create a playlist, split the movie in 8 parts, add Veset logo and a few other graphics, insert ad breaks, and add SCTE-35 triggers to the ad breaks. Then we will apply the playlist to a channel and assign the channel to two playouts: main and backup. We will configure the playout outputs to send RTP with SCTE-35 triggers and EIA-608 captions to AWS MediaLive over the AWS local network.

Movie and ads are being ingested

Movie and 4 ads scheduled, movie split with IN and OUT markers, graphics secondary events and SCTE-35 triggers added

Veset Nimbus is playing the channel on the main and backup playouts

Configure a playout output with AVC video and AAC audio, send it to AWS MediaLive RTP destination A (created in the next step below); also note the SCTE-35 track PID

AWS MediaLive

AWS MediaLive will work as a live transcoder and RTP to HLS segmenter. In this example we will create an adaptive HLS feed in four qualities. AWS MediaLive will store the HLS feed (M3U8 and TS files) in two respective AWS MediaStore containers. In the AWS MediaLive console choose the same AWS region as the one used to host the Veset Nimbus playouts. Create a new RTP input; this will give you the main and backup RTP endpoints.

MediaLive input created, Destination A will be the endpoint for main playout, Destination B will be the endpoint for backup playout

Set the input security group to allow traffic from Veset Nimbus main and backup playouts IP addresses and ports

Create a channel using the input created above

Configure channel settings Avail Configuration in SCTE-35 splice insert mode

Set Timecode Configuration to Embedded timecode

Set the HLS group destination A and B to the AWS MediaStore URLs created in the next chapter. Note that the protocol should be not https but rather mediastoressl, and that there should be a suffix, in this case we use /veset_demo

In the Ad Marker section set the HLS Ad Marker type to ELEMENTAL_SCTE35

In Settings of each HLS quality configure the SCTE-35 Behavior to PASSTHROUGH and SCTE-35 PID to 500 (this is the SCTE-35 PID from the Veset Nimbus output configuration)

AWS MediaStore

Open the AWS MediaStore console in the same AWS region as the one hosting AWS MediaLive. Create two containers. Note the data endpoint URLs; we need to input those in the AWS MediaLive HLS destinations.

AWS MediaStore containers created

AWS CloudFront

Open the AWS CloudFront console. Create a distribution. Add two origins and point them to both AWS MediaStore containers that we created.

AWS CloudFront

Testing the output

The output HLS can be sent from the AWS CloudFront CDN to mobile apps, web pages and OTT platforms. A good way to test the feed is to use VLC, as it allows you to see the metadata of the feed and switch the captions.

Testing the output in VLC

For more information about Veset Nimbus and AWS Elemental products please refer to:

How Veset works with Amazon Web Services

Veset Nimbus runs on AWS: buy through AWS Marketplace, run playouts in your own AWS account or Veset's, with MediaConnect and MediaTailor.