Motion Graphic Overlay - AWS Elemental Live

This is version 2.18 of the AWS Elemental Live documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Live and AWS Elemental Statmux Documentation.

Motion Graphic Overlay

You can insert a motion overlay into the event so that it overlays the video in all the video outputs. You can insert only one motion overlay into the event, but you can use the REST interface during the event to cause the overlay to run repeatedly, either with the same content or new content. Only one motion asset can be run at a time in this way.

Supported File Types

You can use a .swf file, a .mov file, or a set of ordered still .png files as assets for motion image overlays. For .swf and .mov files, the frame rate of the overlay asset must match the frame rate of the underlying video. For sets of .png files, you specify the frame rate when you set up the overlay.

Options for Insertion

The motion overlay is a global processor, which means that it will be inserted in all outputs. The overlay will be burned into the video after decoding and input-specific processing and before encoding and creation of individual streams and outputs. Note that unlike static overlays, a motion overlay can only be set up as a global processor. It cannot be specified in the input (so that it applies only to one video input) and it cannot be specified in the output (so that it applies only to one output stream).

Examples

  • Example 1: “Coming up” Motion Overlay – You want to insert a PNG asset (a series of PNG files that will run as a 10 second motion overlay) 59 minutes into the runtime of the event. The motion overlay may be a “coming up” motion overlay. You want the motion overlay to be placed in the lower right corner of the video frame. You can implement this use case via the web interface or the REST API.

  • Example 2: Animated Corporate Logo – You want to insert a PNG asset (a series of PNG files that will run as a 10 second motion overlay) and run it every 5 minutes starting 20 minutes into the runtime of the event. You specify the single asset in the event and specify the first runtime. You start the event then, after the motion overlay has run once, you send a REST API command to modify the start time of the asset to a new time. You repeat this command (each time with a new start time) as many times as you want.

  • Example 3: Combo – You want to insert a motion PNG asset (a series of PNG files that will run as a 10 second motion overlay) and run it every 5 minutes starting 20 minutes into the runtime of the event. You specify the single asset in the event and specify the first runtime. You start the event then, after the motion overlay has run once, you use the REST API to modify the start time of the asset to a new time. You repeat this command (each time with a new start time) as many times as you want.

    Two minutes before the end of the event, you want a different PNG asset to show (a “coming up” motion overlay). You send a REST API command to change the start time and the content.