[gstreamer-bugs] [Bug 590014] New: Future of parsers

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

  GStreamer | gstreamer (core) | Ver: git
           Summary: Future of parsers
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: thiagoss at embedded.ufcg.edu.br
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


While discussing asf remuxing with Christian, we started talking about
requiring parsed input on all muxers, and forcing demuxers to mark their output
as parsed (when suitable) but we currently don't have a definition of what a
parsed stream is. Another problem is that different containers might have
different "parsed" definitions.

It would be nice if we could come up with a reasonable definition of what a
parsed stream is and how it would interoperate it with different container
formats. Also, having a roadmap would help.

Christian mentioned he had already discussed this with other people, I'll ask
him put it down here as a starting point.


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