By using AWS re:Post, you agree to the Terms of Use

Acceptable HLS input for MediaLive

0

We are trying to use MediaLive for some streaming tasks, and it's pretty straightforward to start with using MP4 as source files to PULL from.
But when starting to try with HLS Pull, it seems there is no clear guidance regarding if there is any specific rules for the HLS feed.
For instance

  1. is it ok for the .m3u8 playlist include multiple sub-playlist which include different qualities, or it has to be a single tier with .ts segments only?
  2. Can the .m3u8 be a static one (vod) or a live feed with updating/dynamic contents?

I've tried a few our .m3u8 but it seems there is always some errors coming out of the pipeline alerts:
like:
Video Not Detected [VideoBuffer[1]] Video not detected: Check input signal
Audio Not Detected [1.1] Audio not detected: Check input signal

IT would be great to get some helpful guide here re using HLS Pull as the input, and I can share our testing feed via PM.

asked 2 years ago105 views
1 Answer
0
Accepted Answer

featheast-ss

AWS Elemental MediaLive does indeed support HLS Live and HLS VOD as input to an MediaLive channel. See https://docs.aws.amazon.com/medialive/latest/ug/inputs-supported-containers.html
In this page notice the reference to the Buffer Segments field and the use thereof for VOD assets vs. Live HLS.

By default MediaLive will use the highest bit rate rendition in the HLS Stack, but can be overridden in the Input Attachment settings, General Settings - HLS Input Settings - HLS Input - Bandwidth. MediaLive does not switch between renditions for the duration of the channel being in a running state.

Additionally the audio can't be in their own renditions within the HLS stack. It must be bundled with the video. As stated on https://docs.aws.amazon.com/medialive/latest/ug/inputs-supported-containers-and-codecs.html. "The audio and video assets must be multiplexed into a single stream. MediaLive can’t ingest audio assets that are in an audio rendition group. "

Feel free to open a ticket with AWS Support and we can troubleshoot the issue for you.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions