Challenge 6: Let’s Play Out!
Previous Challenge Next Challenge
Introduction
Now that we have a stream that’s ready for broadcast and has SCTE-35 ad insertion markers, we need to encode it for the various devices that will play the stream.
Ateme Titan Live is a broadcast-grade encoder. We will use it to take in the final produced stream and prepare it for delivery over the web. As shown in the architecture diagram, Titan Live and Nea Live are the final step before the stream is handed off to Google Cloud’s CDN and used as the origin.
Tools Used
- Ateme Titan Live for encoding
- Ateme Nea Live for packaging
Description
First off, log into both Titan and Nea using the credentials given to you by your coach.
- Titan URL: https://titan.endpoints.[your_project_id].cloud.goog
- Nea URL: https://nea.endpoints.[your_project_id].cloud.goog
We will first create a new input and set its input source to SRT and calling it: SRT output URL from Techex Darwin
Then we will configure an output profile using the default: H.264/AAC in an HLS format.
The crucial part of the configuration is setting up the destination. In our architecture, Titan Live will hand off to the Ateme Nea Packager, which then interfaces with the Google Cloud Video Stitcher API. This is a pre-configured output profile in Titan Live. The output should be configured to create HLS manifests.
Important
To achieve the above, you will be following a step by step guide to configure your pipeline on Ateme Titan and Nea.
Success Criteria
- Your pipeline input is ingested into Titan Live.
- Your output is encoded with H.264/AAC in an HLS format
- Your output flows into Nea and a package and manifest is produced