[Bug 683184] [0.11] implement or remove GST_EVENT_STREAM_CONFIG

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=683184
  GStreamer | gstreamer (core) | 0.11.x

Olivier Crete (Tester) <olivier.crete> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olivier.crete at ocrete.ca

--- Comment #1 from Olivier Crete (Tester) <olivier.crete at ocrete.ca> 2012-09-04 17:51:20 UTC ---
I tried implementing it, but it was not trivial as expected as some elements
(parsers, muxers) use the codec_data in their setcaps negotiation, so the whole
thing can be quite entangled, etc. So implementing it in these elements
requires understanding what exactly is going on. And since from the CAPS you
can't know if there will be a stream-config event, it means that you have to
wait until the first buffer to process the whole thing and possibly fail. Maybe
the stream-config should instead be stashed in the GStructure of the CAPS event
instead of being a separate event, something like
gst_event_caps_set/parse_codec_data().


And in the current API (only having a codec_data buffers, etc), I'm not sure
what the benefit is exactly. My use-case was to put profile-level-id in both
caps (negotiated) and in the stream-config (declarative), but that requires
putting arbitrary things in the GStructure in the event.

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