AWS medialive documentation change
Summary
Added requirements for video aligned pipeline locking method, specified incompatible input types, and clarified output requirements for CMAF Ingest.
Security assessment
Changes describe functional requirements for a new pipeline locking method without addressing vulnerabilities or security controls. No evidence of security fixes.
Diff
diff --git a/medialive/latest/ug/pipeline-locking-verify-input.md b/medialive/latest/ug/pipeline-locking-verify-input.md index 3f02c24b4..b3c9b5e8a 100644 --- a//medialive/latest/ug/pipeline-locking-verify-input.md +++ b//medialive/latest/ug/pipeline-locking-verify-input.md @@ -5 +5 @@ -No support for HLS inputsInputs must include embedded timecode Frame rate requirementsEpoch locking and SCTE 35 +No support for HLS inputsInputs must include embedded timecode (source timecode method)Requirements for video aligned pipeline locking Frame rate requirementsEpoch locking and SCTE 35 @@ -17 +17 @@ If the channel includes an HLS input, MediaLive stops attempting to lock pipelin -## Inputs must include embedded timecode +## Inputs must include embedded timecode (source timecode method) @@ -19 +19 @@ If the channel includes an HLS input, MediaLive stops attempting to lock pipelin -The input must include embedded timecode. These rules apply: +When you use the source timecode pipeline locking method (the default), the input must include embedded timecode. These rules apply: @@ -21 +21 @@ The input must include embedded timecode. These rules apply: - * For both [locking modes](./pipeline-locking-set-up.html#pipeline-locking-mode), the input must have an embedded timecode. + * When using the source timecode method, the input must have an embedded timecode. This requirement applies to both pipeline locking mode and epoch locking mode. @@ -29,0 +30,25 @@ MediaLive continually probes the current source for an embedded timecode. Whenev +## Requirements for video aligned pipeline locking + +When you use video aligned pipeline locking (**Pipeline locking method** set to **VIDEO_ALIGNMENT**), embedded timecodes are not required. + +**Output requirements** + +Video aligned pipeline locking currently works only with CMAF Ingest outputs. + +**Input requirements** + +Certain input types are not compatible with video alignment: + + * File inputs (MP4_FILE, TS_FILE) + + * HLS inputs (URL_PULL with HLS content) + + * RTMP_PULL inputs + + + + +When an incompatible input type is active, video aligned pipeline locking runs in "open loop" mode (unlocked) but continues processing. No validation error is raised, which supports input switching workflows where some inputs may be incompatible. + +For all other input types, video aligned pipeline locking uses visual signature comparison to synchronize the pipelines. Both pipelines must receive the same video content for successful synchronization. +