HTML Motion Graphics in MediaLive Initializes to first input resolution it gets.

Question

Configuration:
- RMTP push input
- single pipeline
- single HLS output to s3
- max input res: 1080p at 10mpbs
- output: 720p QBVR optimized for mobile streaming
- HTML motion graphics enabled

We have a system that builds up the RTMP input resolution based on mobile network conditions. We have noticed that the HTML motion graphics takes its frame reference as the first input resolution that it gets.

e.g if the input resolution starts at 240p, the HTML motion graphics look distorted(looks like 240p basically) even though the output resolution is 720p. The expected behavior would be that the video quality would be low since the input is of a low resolution, but the HTML motion graphics should be based on a 720p frame and hence should be clear.

As a result, even if our input resolution builds up from say 240p -> 720p, the HTML motion graphics continue to be of lower quality.

Answer

When is the HTML5 overlay for the MediaLive channel inserted? Is it done before the channel has started? After the channel has begun? You may want to test starting the insertion after the channel has been started. Motion Graphics overlays needs to be enabled in the channel, then insertion turned on/off via the Scheduling function.

Dynamically changing the resolution in the MediaLive RTMP input may cause other issues. Creating a 720p output from lower resolutions will yield a poor quality image. 
Have you considered varying the bit rate of the RTMP signal and holding the resolution static, if possible?

HTML Motion Graphics in MediaLive Initializes to first input resolution it gets.

관련 콘텐츠