[Bug 738416] decodebin: Fix autoplugging of parser elements
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Mon Oct 20 05:15:44 PDT 2014
https://bugzilla.gnome.org/show_bug.cgi?id=738416
GStreamer | gst-plugins-base | git
--- Comment #10 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2014-10-20 12:15:41 UTC ---
(In reply to comment #9)
> > - prefer Parser/Converter over plain Parser
>
> Okay, But had a feeling that this will add one more overhead with out having
> any advantage in 99% of the usecases (normal use cases).
>
> > - only plug one parser in a chain for the same format, i.e. allow multiple
> > parsers if somewhere the caps have changed from the first to the second parser.
>
> previous comment again,,
>
> > I think an elegant way of doing that is by just not plugging multiple parsers
> > in a row, but if the previous element is not a parser just add one again if
> > needed
>
> This shouldn't work since we are not just adding extra parsers but extra
> capsfilters also. So the previous element won't be be parser.
> Basically every second parser in the system will cause two additions "one
> parser+ one capsfilter".
I meant looking at the previous GstDecodeElement inside decodebin. There you
would find the parser (and the capsfilter as a separate pointer in the same
struct).
--
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.
More information about the gstreamer-bugs
mailing list