On Wed, Aug 5, 2020 at 4:26 PM Martin Storsjö wrote:
>
> On Wed, 5 Aug 2020, myp...@gmail.com wrote:
>
> > On Sun, Jul 26, 2020 at 8:26 PM Jun Zhao wrote:
> >>
> >> From: Jun Zhao
> >>
> >> Respecting the framerate in the libopenh264enc codec context.
> >>
> >> Both the libx264 and libx264 encod
On Wed, 5 Aug 2020, myp...@gmail.com wrote:
On Sun, Jul 26, 2020 at 8:26 PM Jun Zhao wrote:
From: Jun Zhao
Respecting the framerate in the libopenh264enc codec context.
Both the libx264 and libx264 encoders already contain similar logic
to first check the framerate before falling back to t
On Sun, Jul 26, 2020 at 8:26 PM Jun Zhao wrote:
>
> From: Jun Zhao
>
> Respecting the framerate in the libopenh264enc codec context.
>
> Both the libx264 and libx264 encoders already contain similar logic
> to first check the framerate before falling back to the timebase.
>
> Signed-off-by: Jun Z
From: Jun Zhao
Respecting the framerate in the libopenh264enc codec context.
Both the libx264 and libx264 encoders already contain similar logic
to first check the framerate before falling back to the timebase.
Signed-off-by: Jun Zhao
---
libavcodec/libopenh264enc.c | 11 ++-
1 file c
From: Jun Zhao
Respecting the framerate in the libopenh264enc codec context.
Both the libx264 and libx264 encoders already contain similar logic
to first check the framerate before falling back to the timebase.
Signed-off-by: Jun Zhao
---
libavcodec/libopenh264enc.c | 11 ++-
1 file c
