- 最新
- 最多得票
- 最多評論
Can you please share the HLS main manifest for the asset? Does the HLS asset contain WebVTT captions.
Ok I was able to find your main manifest and if you curl the audio rendition manifest the number of audio segments do not match video segment.
For channel assembly # of segments of all individual variants must match and also their duration must be within 300ms of each other. This is required for Channel Assembly to be able to mark segment boundaries for ad insertion. In this asset, there are 51 video segments and only 50 audio segments due to longer audio segments.
Was this HLS asset created using MediaConvert? If yes, can you check the following, in HLS group setting: Make sure the field Minimum final segment length (sec) is set to 1second and under advanced setting of your video outputs (at top), the audio duration is set to match video duration.
Hi Dev_K,
Was this HLS asset created using MediaConvert? If yes, can you check the following, in HLS group setting:
Yes, we did use MediaConvert. I will check for your recommended settings and let you know about the results.
One more question regarding MediaConvert. Our Stream is supposed to run on SamsungTV in Brazil. They noted the following issue
Variant manifest has absolute URLs which we don’t support. Please have it changed to reflect relative URLs instead
Is it possible to allow relative URLs via MediaConvert?
Hi Dev_K,
I created a Hls-Output (link to main manifest) with the mentioned settings:
AudioDuration: "Match video duration" Minimum final segment length (sec) : "1"
Unfortunately the Alert SEGMENT_DURATION_MISMATCH still exists when adding this source as a program to my MediaTailor Channel. Any more ideas?
Kind regards,
Riva
相關內容
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前