[gstreamer-bugs] [Bug 610923] matroskamux can't handle variable resolution

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Mar 5 06:58:03 PST 2010


https://bugzilla.gnome.org/show_bug.cgi?id=610923
  GStreamer | gst-plugins-good | 0.10.17

Mark Nauwelaerts <mnauw> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mnauw at users.sourceforge.net

--- Comment #1 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2010-03-05 14:57:59 UTC ---
On the one hand, above pipelines are a bit off:
* split-packetized=true only has any effect if the input is packetized, which
it is not in case of some raw file input
* a recent h264parse should parse the stream and determine width/height, which
might then conflict with capsfilter

On the other hand, do you have more specific info on the problem with "caps
renegotiation in PLAYING".  For example, afaics, matroskamux has been recently
changed to require input caps to provide width/height, but it should not
complain if the width/height change at some point.  Things will then be a bit
borderline having track metadata that only corresponds to part of the stream
(as they would be with any container).  Particularly, codec-data could have
some problems, but it could/should work out provided the appropriate sps/pps
are contained in the stream.

Sort of summary: a recent h264parse should provide width/height in caps, which
will then go into matroska resolution info, and if appropriate sps/pps
(containing a.o. resolution data) are in-stream, a resolution change should
work.
It might also be useful having h264parse produce avc output (using properties
or output caps negotiation).

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