On Sun, Dec 13, 2020 at 2:05 AM Anton Khirnov wrote:
> Quoting mindm...@gmail.com (2020-11-29 05:08:38)
> > From: Mark Reid
> >
> > The current behaviour ends up squaring the avg_frame_rate if the conter
> mode flag is set.
> > This messes up the timecode calculation, and looks to me as a regres
Quoting mindm...@gmail.com (2020-11-29 05:08:38)
> From: Mark Reid
>
> The current behaviour ends up squaring the avg_frame_rate if the conter mode
> flag is set.
> This messes up the timecode calculation, and looks to me as a regression that
> seems to have been introduced 428b4aac.
>
> The n
On Sat, Nov 28, 2020 at 8:08 PM wrote:
> From: Mark Reid
>
> The current behaviour ends up squaring the avg_frame_rate if the conter
> mode flag is set.
> This messes up the timecode calculation, and looks to me as a regression
> that
> seems to have been introduced 428b4aac.
>
> The new behavio
From: Mark Reid
The current behaviour ends up squaring the avg_frame_rate if the conter mode
flag is set.
This messes up the timecode calculation, and looks to me as a regression that
seems to have been introduced 428b4aac.
The new behaviour is use the "Number of frames" field for avg_frame_ra
