[Bug 729371] New: dash/qtdemux: Reported video size does not correspond to what avdec_h264 states

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=729371
  GStreamer | gst-plugins-bad | 1.x

           Summary: dash/qtdemux: Reported video size does not correspond
                    to what avdec_h264 states
    Classification: Platform
           Product: GStreamer
           Version: 1.x
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: tsaunier at gnome.org
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


When playbing
http://rdmedia.bbc.co.uk/dash/ondemand/bbb/avc3/1/client_manifest-common_init.mpd
, qtdemux states that the video has the following caps:

   width=(int)1920, height=(int)1080, framerate=(fraction)100/1

but avdec_h264 changes them to:

   width=(int)512, height=(int)288,framerate=(fraction)100/1

In gst-validate running:

  gst-validate-1.0 playbin
uri=http://rdmedia.bbc.co.uk/dash/ondemand/bbb/avc3/1/client_manifest-common_init.mpd

we get the follwoing issue reported:

  critical : a field in caps has an unexpected value
             Detected on <avdec_h264-0:src> at 0:00:00.285289601
             Details : Field width from setcaps caps 'video/x-raw,
format=(string)I420, width=(int)512, height=(int)288,
pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive,
chroma-site=(string)mpeg2, colorimetry=(string)bt601,
framerate=(fraction)100/1' is different from expected value in caps
'pending-fields, width=(int)1920, height=(int)1080, framerate=(fraction)100/1,
pixel-aspect-ratio=(fraction)1/1;'
             Description : fields set on a sink pad should be propagated
downstream via set caps

Also I am wondering if framerate=100/1 is for real...

-- 
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.