Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Components of Elemental Live in a cluster - Conductor Live and Elemental Statmux

Components of Elemental Live in a cluster

When you work with Elemental Live using Conductor Live, you work with channels (events), profiles, and nodes.

Channels and Events

A channel is a session that decodes and encodes a live video stream or a video file and produces a live output. Video input comes into the channel and video output is the final outcome of the channel. All the encoding activity occurs within a channel.

The channel that you create using Conductor Live becomes an event on the Elemental Live node.

Profiles

The encoding activity is defined in a profile: the information contained in the profile includes the source of the video input, the kinds of processing that the video will undergo, the types of output protocols to produce (for example, Archive or UDP/TS), and the types of outputs (the containers).

Nodes

The physical computer where the video activity is handled is called a node. When you are deploying Conductor Live, nodes are grouped into a cluster: by adding a node to a cluster, you make it known to Conductor Live. If a node is not in a cluster, it is not being managed by Conductor Live.

Channel – Profile – Node Association

When you create a channel, you associate it with one profile and one node. So the associations between these three entities is via the channel.

Image file diagram-ncp.png

In addition, keep the following in mind:

  • One profile can be used by multiple channels: so profiles are multi-use.

    Image file diagram-cp.png
  • One node can handle multiple channels: so nodes are multi-taskers.

    Image file diagram-nc.png
PrivacySite termsCookie preferences
© 2024, Amazon Web Services, Inc. or its affiliates. All rights reserved.