[FFmpeg-devel] [PATCH] avutil/timecode: fix starting frame number for 59.94 fps

[Michael Niedermayer]

On Thu, Feb 22, 2018 at 06:15:42PM +0530, Gyan Doshi wrote:
> Couple of questions on SE report that the user-supplied timecode string was
> altered in the output when remuxing a MXF with 59.94 fps stream.
> 
> Turns out the code assumed a fixed 30 fps. Fixed in patch.
> 
> Regards,
> Gyan

>  timecode.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 315e9c4d325ef9fc54ba4d76b9cfaa3b1c8996b3  0001-avutil-timecode-fix-starting-frame-number-for-59.94-.patch
> From b7e6ff948c46027c1af28f1b40e921fe6e76a4cc Mon Sep 17 00:00:00 2001
> From: Gyan Doshi <gyandoshi at gmail.com>
> Date: Thu, 22 Feb 2018 18:04:42 +0530
> Subject: [PATCH] avutil/timecode: fix starting frame number for 59.94 fps
> 
> The existing code for adjusting starting frame number assumes 29.97 as
> stream fps.
> ---
>  libavutil/timecode.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

will apply

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20180223/09a26035/attachment.sig>