[FFmpeg-trac] #786(avformat:new): GXF file frame rate double what it should be for some files.

FFmpeg trac at avcodec.org
Sun Dec 18 16:57:14 CET 2011

#786: GXF file frame rate double what it should be for some files.
             Reporter:  ryaowe      |                    Owner:
                 Type:  defect      |                   Status:  new
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |

Comment (by reimar):

 There has been a reported issue that was similar, but not identical (as I
 understood it, a internal too removed the per-stream FPS marking there
 which had a similar effect in the end).
 Their solution was to hack the assignment to stop the time base from going
 below 1/60.
 I think you maybe should be consider this option.
 Pro: It will work with files that I would consider correct, which always
 uses "fields" for time base
 Contra: It will break if you ever need to process content with more than
 60 frames per second / 120 fields per second.
 If this would work for you, too, I'll start thinking of adding this as an
 option as it seems to be quite a common issue, even if it should be due to
 broken files.
 The reason I would tend to believe your files are broken is because these
 fields are called "frames per second" and seem to contain "60" in your
 case. However I don't think your file is actually 60 frames per second,
 but only 60 fields per second (or 30 frames per second).

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/786#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list