Re: [FFmpeg-devel] [PATCH v3] Allow 'concat' filter to support inputs with different frame rates

2019-09-08 Thread Nicolas George
Calvin Walton (12019-08-30): > Right now, the concat filter does not set the frame_rate value on any of > the out links. As a result, the default ffmpeg behaviour kicks in - to > copy the framerate from the first input to the outputs. > > If a later input is higher framerate, this results in

Re: [FFmpeg-devel] [PATCH v3] Allow 'concat' filter to support inputs with different frame rates

2019-09-02 Thread Nicolas George
Calvin Walton (12019-08-30): > Right now, the concat filter does not set the frame_rate value on any of > the out links. As a result, the default ffmpeg behaviour kicks in - to > copy the framerate from the first input to the outputs. > > If a later input is higher framerate, this results in

[FFmpeg-devel] [PATCH v3] Allow 'concat' filter to support inputs with different frame rates

2019-08-30 Thread Calvin Walton
Right now, the concat filter does not set the frame_rate value on any of the out links. As a result, the default ffmpeg behaviour kicks in - to copy the framerate from the first input to the outputs. If a later input is higher framerate, this results in dropped frames; if a later input is lower