- Newest
- Most votes
- Most comments
Hi there,
The most probable causes for this observed change in the playback speed could be the following:
- Due to frame-rate conversions happening because of your job settings.
- Timecode inconsistencies between input and output resulting in speed variation.
- Audio/Video synchronisation issues in the input can cause such a difference in transcode.
- Input file integrity. Corrupted input files can lead to unexpected behavior during transcoding.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
To check for frame rates and playback speed-related metadata specifically, you can use the following commands with FFprobe:
- Check and compare Frame Rate data in the input and output files:
ffprobe -v error -select_streams v:0 -show_entries stream=r_frame_rate -of default=noprint_wrappers=1 FILE_NAME
This command extracts the frame rate information from the video stream
- Check and compare Playback Speed Metadata in the input and output files:
ffprobe -v error -select_streams v:0 -show_entries frame=pict_type -of default=noprint_wrappers=1 FILE_NAME
This command provides information about the picture types, and by analysing the output, you may get an idea if there are any unusual patterns affecting playback speed.
- Further, you can also check for time base information to ensure that the timing of frames is consistent between the input and output files:
ffprobe -v error -select_streams v:0 -show_entries stream=time_base -of default=noprint_wrappers=1 FILE_NAME
By examining these details, you can identify any discrepancies in frame rates or playback speed metadata between the input and output files, helping you pinpoint the issue causing the speed-up problem.
Please also try running your job without enabling SceneChangeDetect: "TRANSITION_DETECTION"
as this feature can cause GOP level changes which could be a possible reason for the shift in frames.
Lastly, try running the job with a few different .wmv files to make sure that this is not an issue with this particular file. If this turns out to be the case, you can use FFPROBE to analyse these different .wmv files to understand what exactly is the issue with this particular file.
In case all the above recommendations fail to provide you a resolution, I would highly recommend reaching out to our AWS Premium Support team for deep dive technical assistance - https://aws.amazon.com/premiumsupport/faqs/
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your help. I tried running the ffprobe commands and this is what I noticed:
After this, I tried removing SceneChangeDetect: "TRANSITION_DETECTION" from MediaConvert instruction and I've got this from new transcoded file: time_base=1/30000
I think it's also important to mention that, I also tried transcoding the file using ElasticTranscoder, and it worked successfully there but not with MediaConvert