Implementing pipeline locking
MediaLive locks the two pipelines in a standard channel whenever locking is possible. It locks the pipelines to ensure that the output from the two pipelines are frame-accurate with each other.
MediaLive locks the pipelines on a best-efforts basis. When pipeline locking isn't possible, processing continues. The inability to lock pipelines isn't considered to be a fault condition.
You can't disable pipeline locking in the applicable output types. But you should configure the behavior, to make sure it suits your workflow.
Note
You might be familiar with the term output locking. In MediaLive, the term used is pipeline locking. Whatever term is used, the effect is identical: frame accurate outputs.
Applicable outputs
Pipeline locking applies only to the following types of outputs:
-
HLS
-
MediaPackage
-
Microsoft Smooth
-
UDP
The channel can contain other types of outputs, but MediaLive won't attempt to lock their outputs. This means that in those other output groups, there is no guarantee that the content of the two pipelines will be frame-accurate with each other.
Pipeline locking modes
There are two modes of pipeline locking:
-
Pipeline locking (the default): lock the two pipelines to each other
-
Epoch locking: lock the pipelines using the Unix epoch as the reference.
