- Newest
- Most votes
- Most comments
AWS MediaConvert, when creating clips, will look for the nearest I-Frame/IDR in the source file, before the clip Start Time Code. It will then decode from the IDR to and beyond the Start Time code.
The source example that was included seems to be fragmented MP4, with a fragment for each frame, which is a bit unusual. Typically, fragments contain multiple frames, up to several secs in duration. Currently MediaConvert will look for IDRs within a fragment or segment of the source file. The one frame per fragment is limiting MediaConvert from finding an IDR for a decode start. This means it starts its decode with a P or B frame and thus not a full image frame. This creates the blurring experienced until an I-Frame is encountered.
A possible work around is to have your sourced created with fragments that contain 1-2 seconds of video. If this is not achievable, locate where I-Frames are in the source and start the clipping at a fragment that contains an I-Frame.
Relevant content
- Accepted Answerasked a year ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago