Skip to main content
Managing Live Events
Updated over a week ago

AnyClip provides publishers with the ability to set up, configure, and schedule Live events for their customers.

For publishers with Live Events permission, clicking the Live tab in the AnyClip Platform displays the Live Events window.

live1.jpg

The Live Events list contains all the events you've set up; however, you can also filter for Past Events, Current Events, and Future Events by selecting them from the dropdown list. You can also use the search option to search for a specific event by name or ID.

In this window, you can view all events and add new ones, and the status of each event, which can be one of the following:

  • Ready – for future events

  • Live – for current events

  • Ended – for past events

In addition, when you click the three-dot edit menu next to a Live event, you can also Edit, Embed, Duplicate, and Archive that event.

Live streaming redundancy

AnyClip’s Live events are based on the following Amazon Web Services:

  • AWS MediaLive

  • AWS MediaPackage

  • Amazon CloudFront

By using these services, we can provide redundancy at multiple levels, as detailed below.

Input Redundancy:

  • AnyClip creates a standard channel that provides two redundant encoder pipelines using AWS MediaLive.

  • By using the input redundancy feature in the AWS Elemental MediaPackage, this allows a live channel to seamless failover across the two-channel pipelines provided by AWS MediaLive and the redundant inputs used by a AWS MediaPackage channel.

  • The result is a highly available live channel from a single endpoint as well as a better-quality viewing experience.

CDN Redundancy:

  • Amazon CloudFront supports multiple origins for backend architecture redundancy.

  • Amazon CloudFront’s native origin failover capability automatically serves content from a backup origin when the primary origin is unavailable.

CDN Fallback:

AnyClip uses LimeLight CDN as a fallback HTTP server for CDN redundancy in case the Amazon CloudFront stream fails for any reason.

Live Event Creation Flow is described on the following pages


Did this answer your question?