Anton Khirnov (12023-01-27):
> This is not forcing timestamps on output frames. This is solving the
> general problem where the correct matching of input frames is determined
> by some external logic. The specific case that is of interest to me is
> where this logic is the ffmpeg CLI framerate
Quoting Nicolas George (2023-01-27 15:53:42)
> framesync generates output based on its input. Therefore to force
> timestamps on output frames you need to force timestamps on input
> frames.
This is not forcing timestamps on output frames. This is solving the
general problem where the correct
Anton Khirnov (12023-01-27):
> Useful when there is some external process that determines canonical
> frame synchronization. E.g. the framerate conversion code in ffmpeg CLI.
> ---
> doc/filters.texi| 6 ++
> libavfilter/framesync.c | 121 ++--
>
On 1/27/23, Anton Khirnov wrote:
> Useful when there is some external process that determines canonical
> frame synchronization. E.g. the framerate conversion code in ffmpeg CLI.
> ---
> doc/filters.texi| 6 ++
> libavfilter/framesync.c | 121 ++--
>
Useful when there is some external process that determines canonical
frame synchronization. E.g. the framerate conversion code in ffmpeg CLI.
---
doc/filters.texi| 6 ++
libavfilter/framesync.c | 121 ++--
libavfilter/framesync.h | 11
3 files
