[FFmpeg-trac] #9814(undetermined:reopened): time_scale / num_units_in_tick is not infinite precision

FFmpeg trac at avcodec.org
Thu Jan 26 11:02:34 EET 2023


#9814: time_scale / num_units_in_tick is not infinite precision
-------------------------------------+-------------------------------------
             Reporter:  Balling      |                    Owner:  (none)
                 Type:  enhancement  |                   Status:  reopened
             Priority:  wish         |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Balling):

 >Issue is that your timebase is generic one

 But we have fixed_frame_rate_flag set. So in reality we can assume it is
 CFR and THAT IS WHAT mov/mp4 muxer does. It sets '''Frame rate mode:
 Constant'''. Okay? Yet, because of bad code somewhere, it does paste 29.97
 instead of 29.97002997. Okay?? This is what was happening when drop-frame
 timecode!

 That is why I said

 >For that you need to increase 30000/1001 precision.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9814#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list