[Bug 667704] New: [videoparsers] framerate calculation

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=667704
  GStreamer | gst-plugins-bad | git

           Summary: [videoparsers] framerate calculation
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: julien.isorce at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=205027)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=205027)
minimal mpegts sample to reproduce the problem

* Steps to reproduce:

GST_DEBUG=*codecparse*:5 gst-launch-0.10 filesrc location=sample.ts !
mpegtsparse ! mpegtsdemux ! mpegvideoparse ! fakesink sync=1 silent=1 -v

 * Actual result:

codecparsers_mpegvideo gstmpegvideoparser.c:217:gst_mpeg_video_parse_sequence:
fps: 30000/1001

mpegvparse0.GstPad:src: caps = video/mpeg, framerate=(fraction)60000/1001

 * Other infos:

I attached a minimal sample to have the caps. With the full one the frame
duration is 0:00:00.033366666 (! ffdec_mpeg2video ! fakesink silent=0), so it
seems the real framerate is 30.

In gstmpegvideoparse.c:

mpvparse->fps_num = mpvparse->sequencehdr.fps_n *
(mpvparse->sequenceext.fps_n_ext + 1) * 2;

The extension is taken into account. Whereas in legacympegvideoparse there is a
FIXME about it.

 * Question:

Do you think this is a problem from the encoder or from mpegvideoparse ?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.