M3U8 manifest with M4S frames, No parser found for container

Question

Hi,
I have in MediaLive

Input_A: 
RTMP_PULL SINGLE class,  M3U8 manifest. Internal frame format - M4S

Channel:
 Input attachment: Input_A 
 Output group: Archive, Amazon S3

Start Channel.
Alert:
Message: "Failed to probe input: Unable to open input file [.../segment_6.m4s]: [Failed probe/open: [No parser found for container]]"

Have changed Input codec, the same result. CloudWatch with Debug level doesn't have more detailed information. 
I think "segment_6.m4s" is correct because I made MP4 from M3U8 manifest. I guess the issue is that MediaLive doesn't know how to work with M4S frames but I didn't find information about it or need custom parameters set for M4S frames. 
Everything ok if  M3U8 manifest contains TS frames.
Is somebody faced with it? Thanks.

re:Post Agent · Accepted Answer

It appears that you're encountering an issue with MediaLive not being able to process M4S (MPEG-4 Segment) frames from an M3U8 manifest. This is indeed an unusual setup, as MediaLive typically expects HLS inputs to use TS (Transport Stream) segments.

MediaLive is designed to work with specific input formats, and M4S is not a standard format for HLS streams. The error message "No parser found for container" suggests that MediaLive doesn't have a built-in capability to handle M4S segments.

Here are a few points to consider:

1. Input Format: MediaLive is expecting HLS inputs to use TS segments. Your setup with M4S segments is non-standard for HLS and may not be supported.

2. Input Type: You mentioned using RTMP_PULL as the input type, but you're actually trying to ingest an HLS stream (M3U8 manifest). This mismatch could be part of the problem. For HLS inputs, you should use the HLS input type in MediaLive.

3. Compatibility: MediaLive has specific requirements for input formats. While it can handle MP4 inputs in some cases, it's not designed to work with M4S segments in an HLS stream.

To resolve this issue, you might need to:

1. Convert your input stream to use TS segments instead of M4S. This is the format MediaLive expects for HLS inputs.

2. If possible, provide the content as a standard MP4 input rather than an HLS stream with M4S segments.

3. Check if your upstream system can provide the content in a format more compatible with MediaLive, such as standard HLS with TS segments or RTMP.

If none of these options are feasible, you may need to use a different service or implement a transcoding step before ingesting into MediaLive to convert the content into a compatible format.  
**Sources**  
[Formats supported in different types of outputs - MediaLive](https://docs.aws.amazon.com/medialive/latest/ug/supported-format-outputs.html)  
[Create an MP4 input - MediaLive](https://docs.aws.amazon.com/medialive/latest/ug/setup-input-mp4.html)  
[Ensure correct setup on the HLS upstream server - MediaLive](https://docs.aws.amazon.com/medialive/latest/ug/setup-uss-hls.html)

Roman Chekmazov · Answer

Here is list of supported input protocols on MediaLive: https://docs.aws.amazon.com/medialive/latest/ug/inputs-supported-formats.html 
There we mention: "With HLS, the media must be a transport stream. MediaLive doesn't support ingest of HLS content that contains any other type of media." 
So you are trying to ingest unsupported container.
Recommend to change your HLS container to ts to use it with MediaLive

M3U8 manifest with M4S frames, No parser found for container

Relevant content