Content owners use Veset Nimbus cloud playout platform to originate linear TV channel. Veset Nimbus is a true cloud-based SaaS platform. Neither upfront investment nor long term commitment, whether direct or indirect, is required from the customer.
The platform’s web-based intuitive, simple and user-friendly interface allows users to create new linear TV channels in a fast and efficient manner. Veset Nimbus output is a broadcast quality steam that can be delivered to the viewers via OTT and/or traditional distribution channels.
AWS has evolved into a pre-eminent 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 previously closed and IT-resistent broadcast technology market. Migration of many of Elemental capabilities to AWS Elemental platform and further addition of wide range of services focused on OTT distribution in particular enhance capabilities of Veset Nimbus as it is natively developed for AWS and seamlessly integrates with the wide range of AWS Elemental services.
For example broadcasters use Amazon MediaLive, MediaStore and 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 setup Amazon services to broadcast to any vMVPD and OTT platforms including Roku, Hulu, Samsung, Amazon Prime video and others.
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 few other graphics, insert ad breaks, 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 AWS local network.
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 AWS MediaLive console choose the same AWS region as one used to host Veset Nimbus playouts. Create a new RTP input, this will give you the main and backup RTP endpoints.
Open AWS MediaStore console in the same AWS region as one hosting AWS MediaLive. Create two containers. Note the data endpoint URLs, we need to input those in AWS MediaLive HLS destinations.
Open AWS CloudFront console in the same AWS region as one hosting AWS MediaLive. Create a distribution. Add two origins and point to both AWS MediaStore containers that we created.
The output HLS can be sent from 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 to see metadata of the feed and switch the captions.
For more information about Veset Nimbus and AWS Elemental products please refer to:
Cloud Playout gathers industry experts to examine why media companies are moving playout into the cloud, the different use cases, and the different models as well as the implications of these architectures.
The report is one of four in the DPP’s 2021 series, The Cloud for Media, which aims to explore the reality of media in the cloud today, and shed light on the challenges that remain.