h264parse: fix test and set not using the same input
authorVincent Penquerc'h <vincent.penquerch@collabora.co.uk>
Fri, 6 Jan 2012 10:52:36 +0000 (10:52 +0000)
committerVincent Penquerc'h <vincent.penquerch@collabora.co.uk>
Fri, 6 Jan 2012 10:54:11 +0000 (10:54 +0000)
This fixes H.264 output not having a set framerate, and
confusing some of the elements downstream (such as interlace).

gst/videoparsers/gsth264parse.c

index 505def9a69d1955ba2f0ca4729ab7bf0b3a8f7e5..05a5bab2ad3bc24111948545deb0d2dc0308fe45 100644 (file)
@@ -1060,7 +1060,7 @@ gst_h264_parse_update_src_caps (GstH264Parse * h264parse, GstCaps * caps)
       gst_caps_set_simple (caps, "width", G_TYPE_INT, sps->width,
           "height", G_TYPE_INT, sps->height, NULL);
       /* but not necessarily or reliably this */
-      if (h264parse->fps_num > 0 && h264parse->fps_den > 0)
+      if (sps->fps_num > 0 && sps->fps_den > 0)
         gst_caps_set_simple (caps, "framerate",
             GST_TYPE_FRACTION, sps->fps_num, sps->fps_den, NULL);
     }