- Newest
- Most votes
- Most comments
Please double-check that ' Global Configuration/ Support Low Framerate Inputs' is enabled to ensure that if your upload should have a momentary drop in frame rate, the source will still be decoded.
If you are using RTMP push input, the RTMP handshake may not be completing; or the source may change frame rates or specs after the initial handshake/input probe. The way for customers to reset the RTMP listener process on the MediaLive side is to stop and restart the channel.
Also: We recommend starting the channel on a known good VOD input (it can be a logo, a "Coming up next" bumper, or even black video) to properly initialize all the outputs and metrics regardless of the state of the streaming input. When the Channel is completely and successfully started, then confirm there are no Alerts and the 'NetworkIn' metric shows your streaming source is coming in . Then you can confidently switch to the streaming input.
Hi, thank you for your suggestion. Meantime the AWS Support sent me following answer:
"However, one of our support engineers used OBS to reproduce your steps and create another capture which resulted in the same issue when we attempted to transcode it on MediaLive. Analyzing the HEVC bitstream from that capture, there is no Sequence Parameter Set (SPS) in the HEVC bitstream of the capture. The SPS contains information necessary for a decoder, like the video resolution. Our suspicion is that your workflow created a HEVC encode in which the SPS was only generated once rather than being regenerated periodically. For a transport stream file it's reasonable for the video to only carry a single SPS at the beginning of the stream, but when performing live streaming the SPS should be repeated periodically (at least once every couple seconds, usually once per GOP) to accommodate decoders that tune into the stream at random points. Unfortunately, we are not experts in OBS and therefore can not advise you on the best way to fix the problem with the OBS encoder."
But I did several tests with Wowza, Nimble Server and Callaba Cloud with the exact same setup and all of the other servers didn't have any problem with that stream. Only AWS fails to encode it.
Relevant content
- Accepted Answerasked 7 months ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Constant Bitrate (CBR) is not the same as Constant Frame Rate (CFR). Using a frame rate the Medialive is spec.ed to utilize is very important.
What frame rate are you using? What type of encoder are you using?
1080p25 x264 5Mbps – Wirecast and OBS. The frame rate is CFR 25. The option VFR doesn't exist in the encoders I am using. Thank you.