1 Answer
- Newest
- Most votes
- Most comments
0
Can you try to configure “Include Filler NAL Units” option in the RTMP output group: Applies only when the rate control mode (in the codec settings) is CBR (constant bit rate). Controls whether the RTMP output stream is padded (with FILL NAL units) in order to achieve a constant bit rate that is truly constant. When there is no padding, the bandwidth varies (up to the bitrate value in the codec settings). We recommend that you choose Auto.
answered a year ago
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago

A few comments. Not sure why you have 0 B frames. B frames are needed for efficient compression. Either way not the problem you are having.
I am almost certain that you did these tests with static content. RTMP generally ramps itself down when content is static such as color bars and a slate.
I would define all aspect of the Media Live encode and not allow "same as source". Pixel shape should be 1 to 1.
Semi curious how are you getting SRT into Media Live. The only way I can think of is through an SRT listen in Media Connect. Media Live does not accept SRT.
Yes, sorry I was unclear. SRT in from mediaconnect, then vpc input from mediaconnect to medialive. I stream the same content from my computer to the RTMP destination, I get 1080p and 6.5mbps. I stream out of mediaconnect with SRT to my machine, I get 1080p. But when I do mymachine->mediaconnect->medialive->RTMP 3rd party provider. I get ~1.5mbps and sometimes 1280x720. Also, I tried with static content and moving text and the infamous twitch sync footage you can find somewhere on the internet. As for the B frames, it's been a habit to remove them to lower the lookahead as it would require the full GOP to be downloaded before being displayed. Not sure in this case it changes much though.