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

FFmpeg trac at avcodec.org
Thu Jan 26 10:38:49 EET 2023


#9814: time_scale / num_units_in_tick is not infinite precision
-------------------------------------+-------------------------------------
             Reporter:  Balling      |                    Owner:  (none)
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:  invalid
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by Elon Musk):

 * status:  open => closed
 * resolution:   => invalid

Comment:

 Issue is that your timebase is generic one that can not reproduce your fps
 perfectly, and .h264 does not store pts or timebase at all.

 ffmpeg -i example.h264 -vf settb=1001/30000,vfrdet -f null -

 This shows that file is "CFR", but that is meaningless as format never
 store timestamps or timebase, its just put by ffmpeg code so it can
 process it somehow.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9814#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list