Setting up a single-pipeline channel without upgrade potential

If you don't want to implement pipeline redundancy now or in the future, you set up the channel as a single-pipeline channel, and you set up the inputs as single-class inputs, where possible.

Note

Before you decide to implement this option, read the information about setting up without pipeline redundancy, but with the option to easily upgrade later on.

Follow these guidelines when you plan the workflow:

• When you create inputs, set up the inputs as follows:

  • Set up CDI inputs and RTP inputs as standard inputs, because that's the only way to set them up.

  • Set up all other inputs as single-class inputs. To set up the input in this way, set the Input class field to Single input.

• When you create the channel, do the following:

  • Set up the channel as a single-pipeline channel. See Complete channel and input details.

  • At the step to attach inputs to the channel, attach the inputs that you have identified. The inputs might be both standard-class inputs and single-class inputs.

• Contact the upstream system and request that they provide one content source. Even if your channel includes CDI inputs or RTP inputs, the upstream system for those inputs should provide only one source.

How a single-pipeline channel works

When you set up a single-pipeline channel without any upgrade provision, the channel is a single-pipeline channel. The inputs can be a combination of single-class inputs and standard-class inputs.

• The channel contains one pipeline—pipeline 0.

• Each single-class input that is attached to the channel contains one pipeline. The input is connected to one content source.

  As this diagram illustrates, the upstream system provides one instance of the source content to the input, to the pipeline that is indicated by the blue line. The input provides that one instance to the one pipeline in the channel. The channel produces one instance of the output for the downstream system.

  

• Each CDI input or RTP input that is attached to the channel contain two pipelines. However, only one of the pipelines is connected to a content source. The other input pipeline is inactive.

  As this diagram illustrates, the upstream system provides one instance of the source content to the input, to the pipeline that is indicated by the blue line. The input provides that one instance to the one pipeline in the channel. The channel produces one instance of the output for the downstream system. The other pipeline in the input (the green pipeline) is always inactive.

  

Failure handling

If there is a problem that causes a pipeline to stop functioning, MediaLive stops producing output. The downstream system stops receiving output.