[gstreamer-bugs] [Bug 570619] [qtmux] with faststart disabled doesnt write moov atom when output is an appsink

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Feb 25 06:36:56 PST 2009


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

  GStreamer | gst-plugins-bad | Ver: git

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |




------- Comment #2 from Tim-Philipp Müller  2009-02-25 14:37 UTC -------
Be that as it may, I think all such muxers should output at least a warning, if
not an error, in this case. Writing broken files and not even telling the user
about it isn't cool.

We should be able to detect whether downstream supports 'seeking' or not,
either via a SEEKING query on start-up and/or at the end when we push the
newsegment event before rewriting the header (if the push fails because we're
shutting down posting an error should be fine as well, since we can probably
assume it will be dropped as the bus is flushing)


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




More information about the Gstreamer-bugs mailing list