[Bug 778298] New: [REGRESSION]: decodebin2: Wrong stream-topology reported for some streams

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 778298
           Summary: [REGRESSION]: decodebin2: Wrong stream-topology
                    reported for some streams
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-base
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: tsaunier at gnome.org
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Pitivi downstream report: https://phabricator.freedesktop.org/T7673

Since:

> commit 46835f550d0a49338a3477973df842b1443c7a81
> Author: Sebastian Dröge <sebastian at centricular.com>
> Date:   Sat Dec 17 21:34:40 2016 +0200
>
>    decodebin2: Put the correct pad into the stream-topology if a parser/converter is used
>    
>    We have to take the capsfilter into account then as the elements are not
>    linked directly. Previously this caused NULL be set in these cases.


Basically since that commit the discoverer detects 2 h264 streams, including
one with `video/x-h264, stream-format=(string)byte-stream,
alignment=(string)nal` as caps which is just wrong.

To reproduce you can run:

echo "change-severity, issue-id=file-checking::no-stream-id,
new-severity=critical" > /tmp/00486.override &&
GST_VALIDATE_OVERRIDE=/tmp/00486.override gst-validate-media-check-1.0
https://phabricator-static.freedesktop.org/file/data/loerosd6vrwvlaeewe2d/PHID-FILE-nfwo23d5fpc7lerg6n3q/00486.MTS
Which will error out telling you that the discoverer reported a stream which
does not have a stream ID which is not correct.

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