AWS medialive documentation change
Summary
Updated RTP input documentation with expanded guidance on identifying video/audio/captions, including PID/language code usage and caption type distinctions.
Security assessment
The changes provide operational guidance for content extraction but contain no references to security controls, vulnerabilities, or authentication mechanisms. Focus is on workflow clarification rather than security.
Diff
diff --git a/medialive/latest/ug/extract-contents-rtp.md b/medialive/latest/ug/extract-contents-rtp.md index be9a514ac..2d701043f 100644 --- a//medialive/latest/ug/extract-contents-rtp.md +++ b//medialive/latest/ug/extract-contents-rtp.md @@ -7 +7,20 @@ -This procedure applies to both RTP inputs from the internet and inputs from Amazon Virtual Private Cloud. The content in an RTP input is always a transport stream (TS). The TS is made up of one program (SPTS) or multiple programs (MPTS). Each program contains a combination of video, a combination of audio, and optional captions. +This procedure applies to both RTP inputs from the internet and inputs from Amazon Virtual Private Cloud. The content in an RTP input is always a transport stream (TS). The TS is made up of one program (SPTS) or multiple programs (MPTS). Each program contains a combination of video and audio. It might also contain embedded-style or object-style captions. + +Obtain identifying information from the content provider: + + * For video – Choose the one video rendition that you want, and obtain its PID or bitrate. (The source content might contain more than one video rendition.) + +If two video renditions are identical, look at the audios and captions in each program. Those might be different, in which case you should choose the video rendition that contains the audio or captions formats you want. + + * For audio – For the same rendition as the video, obtain the PIDs or three-character language codes of the audio languages that you want. + +###### Note + +We recommend that you obtain the PIDs for the audio assets. They are a more reliable way of identifying an audio asset. Use the language only if there is only one instance of each audio language in the audio asset. + + * For captions – For the same rendition as the video, obtain the identifiers: + + * If the captions are embedded, obtain the languages in the channel numbers. For example, "channel 1 is French". + + * If the captions are object-style captions (for example, DVB-Sub), obtain the PIDs of the captions languages that you want. + @@ -9 +27,0 @@ This procedure applies to both RTP inputs from the internet and inputs from Amaz -Obtain identifying information from the content provider. @@ -11,6 +28,0 @@ Obtain identifying information from the content provider. -Asset | Details | Information to obtain ----|---|--- -Video | The source content might contain more than one video rendition.If two video renditions are identical, look at the audios and captions in each program. Those might be different, in which case you should choose the video rendition that contains the audio or captions formats that you want. | Obtain the PID of the video rendition that you want. -Audio | You must work with the audio that is in the same rendition as the video that you chose. | Obtain the PIDs or three-character language codes of the audio languages that you want.We recommend that you obtain the PIDs for the audio assets. They are a more reliable way of identifying an audio asset. -Captions | Embedded | Obtain the languages in the channel numbers. For example, "channel 1 is French". -Object-style captions, for example, DVB-Sub | Obtain the PIDs of the captions languages that you want.