While a Source carries a continuous stream of video, it may contain within it multiple “Events”. Events on the Source may be created on-the-fly or scheduled in advance, and they are key because AWS MediaConnect resources are only enabled when an Event is active.
An Event may be defined differently between the Distributor and the Subscribers, or between Subscribers. Each Event has a start and end time which identifies the content’s time slot. These Events may be adjacent in time, disconnected or they may even overlap.
An example can be a live sporting event. The stream on the Source may cover the entire event with build-up and post-analysis. Subscribers, however, may define the Event as the main action only, and set their Events times accordingly.
An Event may also have multiple Sources, ie an editorially identical stream sent to many Sources, an option to be used for adding resilience where identical streams exist across multiple input routes.
An Event may also have multiple Sources with different inputs, ie a multi-sport or multi-camera event.
M2A Connect manages the activation and deactivation of AWS infrastructure according to Event requests.
Creating an Event at M2A Cloud Console
At the “Events” pane at the M2A Console, click “Create”.
A small window will open. Select if a “Single Event” needs to be created, or “Batch Events”. It’s also possible to get reports on events. Single Events can also be created by clicking within a Source channel. By default, the Source clicked on is the Source selected but other Sources can be added and the default removed.
Creating a Single Event
By selecting “Single Event”, a new window will open:
After naming and adding a description to this event, select one or more Sources for this Event.
On Air Time (start/end)
These times should be seen as defining the editorially important content. If the times are known with certainty, these can be exact; if only loosely known, add padding to the start and end.
Resource Time (start/end)
On either side of the On Air Time are the Resource times. These determine when the AWS resources will start and finish. This allows time for the AWS resource allocation and spin-up, as well as typical line-up activities at the beginning, and keeps the AWS running in case of over-run. If the box “Use default resource times” is ticked, then the resources will spin up 1 hour before “Event on Air Start Time” and spin down 15 minutes after “Event on Air End Time”.
Event Labels
Labels can be added to Events for identification and rights management purposes.
Creating Batch Events
Select this option if you wish to create Events in bulk, or with additional complexity. The batch tool allows for many events to be created with repeating patterns of regularity, or sharing the same set of labels.
Event Report
Reports of events of a set period can be created for all sources or for one or more sources at a time. These reports can be exported in “CSV”, “XLS”, or “JSON” format.