[gstreamer-bugs] [Bug 608167] New: [decodebin2] Doesn't push out full topology

[GStreamer (bugzilla.gnome.org)]

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

           Summary: [decodebin2] Doesn't push out full topology
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bilboed at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=152319)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=152319)
read all caps

I'll take a simple example, but this behaviour happens with many other cases,
mostly those when a parser is being used.

When taking a simple mp3 file (i.e. not surrounded with id3), the resulting
topology isn't complete.

We end up with "typefind ! mp3parse ! mad" being plugged in internally. One
would expect the stream topology to contain:
* the upstream caps (i.e. the caps from typefind.src)
* the caps between mp3parse and mad
* the final caps from mad (from its source pad)

Right now the resulting topology structure contains:
* the upstream caps (audio/mpeg, mpegversion=(int)1, layer=(int)3)
* the final caps (audio/x-raw-int, endianness=(int)1234, channels=(int)2,
width=(int)16, dept....)

The problem is that this information isn't complete, it's missing the caps
between mp3parse and mad, which contain quite a bit more information like this:
audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)2, layer=(int)3,
rate=(int)22050, channels=(int)2, parsed=(boolean)true

For some reason, the code writing the topology structure misses out the caps
between mp3parse and mad, the attached patch fixes that issue.

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