[Bug 749433] New: pad-monitor test error about audio rate change

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=749433

            Bug ID: 749433
           Summary: pad-monitor test error about audio rate change
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-devtools
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: joybro201 at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

DISPLAY=:0 GST_GL_XINITTHREADS=1 GST_VALIDATE_SCENARIO=seek_forward
gst-validate-1.0  playbin
uri=http://dash.edgesuite.net/dash264/TestCases/1a/netflix/ElephantsDream_AAC48K_064.mp4.dash

The above test fails with the following error.

Critical error Field rate from setcaps caps 'audio/x-raw, format=(string)F32LE,
layout=(string)interleaved, rate=(int)48000, channels=(int)2,
channel-mask=(bitmask)0x0000000000000003' is different from expected value in
caps 'pending-fields, rate=(int)24000, channels=(int)2;'

I confirmed that avdec_aac element's sink and src pad have different caps as
following in the test pipeline.

<sink>
audio/mpeg
rate : 24000
channels : 2

<src>
audio/x-raw
layout : interleaved
rate : 48000
channels : 2

pad-monitor seems to assume that audio rate caps information shouldn't be
changed b/w a decoder's sink and src pad. But I'm not sure this assumption is
right for this case. It seems that rate of sink and src pad can be considered
the same because decoded data have interleaved layout.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.