Tags: MolotovTv/FFmpeg
Tags
h264_metadata bitstream fixed_frame_rate_flag fix After changes like ef13faf, the h264_metadata bitstream filter stopped working when using the fixed_frame_rate_flag option on an input stream that doesn't contain VUI because the default inferred value of low_hrd_delay_flag seems to be 1. ffmpeg used to raise a warning, but proceeded anyway but now aborts after the other fixes since the output is rightfully invalid. I believe this change makes the bitstream filter conform to page 403 of the ITU spec: "When fixed_frame_rate_flag is equal to 1, low_delay_hrd_flag shall be equal to 0. When low_delay_hrd_flag is not present, its value shall be inferred to be equal to 1 − fixed_frame_rate_flag."
Molotov patches * hlsenc lower verbosity * aacdec log debug * add ism_offset option to offset fragment start times * add audio_track_timescale option * always write an stss box in CMAF mode * Molotov JSON syslog option
h264_metadata bitstream fixed_frame_rate_flag fix After changes like ef13faf, the h264_metadata bitstream filter stopped working when using the fixed_frame_rate_flag option on an input stream that doesn't contain VUI because the default inferred value of low_hrd_delay_flag seems to be 1. ffmpeg used to raise a warning, but proceeded anyway but now aborts after the other fixes since the output is rightfully invalid. I believe this change makes the bitstream filter conform to page 403 of the ITU spec: "When fixed_frame_rate_flag is equal to 1, low_delay_hrd_flag shall be equal to 0. When low_delay_hrd_flag is not present, its value shall be inferred to be equal to 1 − fixed_frame_rate_flag."
Molotov patches * hlsenc lower verbosity * aacdec log debug * add ism_offset option to offset fragment start times * add audio_track_timescale option * always write an stss box in CMAF mode * Molotov JSON syslog option
PreviousNext