[gstreamer-bugs] [Bug 432612] matroskamuxer doesn't handle segments correctly

[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=432612

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

Mark Nauwelaerts changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manauw at skynet.be




------- Comment #2 from Mark Nauwelaerts  2007-08-05 10:38 UTC -------
IMO, muxers should do as little as possible (time) transformations behind the
(hidden) scenes, but put streams into container as faithfully as possible (and
out of them for demuxer).  Rather, gstreamer's pipeline architecture should be
exploited to make sure the muxer's input is as "clean" as possible.
For example, rather than having a "naive patch" (or another one for that
matter) (again) duplicate segment handling code in yet another element, it
seems that the same effect (basically) can be achieved by using identity
single-segment=true in the pipeline somewhere before matroskamux.  And if the
effect that one wishes to achieve in a particular case may be different, than
it would seem "cleaner" to put this in custom element (before muxer), or patch
identity, or some other element, etc  [for example, for my general transcoding
app, I have some element that (re)computes timestamps purely based on frame or
sample count in stead of segments; should clearly not be in a muxer either].
In particular, pre-transforming a "strange" stream into a "nice" stream would
settle this for any subsequent muxer, rather than trying to have all of them
prepared for as many possible cases (with approximately duplicated code).


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