[gstreamer-bugs] [Bug 530513] h264parse dont have width and height caps

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=530513

  GStreamer | gst-plugins-bad | Ver: HEAD CVS




------- Comment #13 from Mark Nauwelaerts  2008-05-06 21:42 UTC -------
If I understand vorbisparse/theoraparse code/documentation/test result
correctly, it will "parse the header packets of the stream and put them as the
streamheader in the caps", which vorbisenc/theoraenc already do.  ...parse do
not put a width or height entry in the caps structure, apparently/perhaps (?)
because it is defined (? somewhere) that theora/vorbis caps should not have
these properties (?). As such, matroskamux can take the header packets from the
caps (not the stream) but still has to start digging for the proper bytes
providing width, height, etc (without depending on theora/vorbis libs to do
so).

Regarding (constant) bitrate, muxers might pick these up from (event) tags if:
a) e.g. lame would send such (pretty sure it does not do so now),
b) and, there would be a way to distinguish the ones sent by e.g. mad from
those by lame.  Or otherwise the undesirable ones should be eaten before
causing ambiguity somewhere (however, right now, lame explicitly passes on any
incoming event tags ...),
c) and, having muxers use e.g. GstCollectPads2 (in bug 415754) would give them
a clean chance to deal with incoming events (rather than a fighting/hacked one)

In any case, a great deal can be done here with caps, events, etc, but it seems
to be primarily a matter of having specs/agreement (?) that sort these things
out so that elements can rely on it in their (loose) interaction with one
another.  After all, the original topic here also seems to revolve around such
a matter of taste/opinion/usefulness  (so as not to appear getting off-topic :)
)


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=530513.