選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Special conditions for TS and CMAF manifests in MediaPackage

焦點模式
Special conditions for TS and CMAF manifests in MediaPackage - AWS Elemental MediaPackage v2
此頁面尚未翻譯為您的語言。 請求翻譯

If you are using TS or CMAF manifests for MediaPackage, these special conditions apply.

  • For TS manifests, we strongly recommend that you use audio rendition groups to avoid removing the video streams that are multiplexed with the audio streams that are filtered out. For more information about rendition groups, see AWS Elemental MediaPackage rendition groups reference.

  • In TS and CMAF manifests, the audio sample rate is not signaled, so it's not easy to visually check the original or filtered manifests for this setting. To verify the audio sample rate, check the audio sample rate at the encoder level and output level.

  • In TS and CMAF manifests, the BANDWIDTH attribute for a variant associates the bandwidth of the audio track with the video track, whether it is multiplexed with the video track, or if it is an audio rendition track referenced by the video track. Therefore, you can't visually inspect the original and filtered manifests to confirm the video_bitrate filter has worked. To verify the filter, check the video bitrate at the encoder level and output level.

  • For TS and CMAF manifests, request parameters appended to bitrate playlists or segments result in an HTTP 400 error.

隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。