[Bug 733171] New: baseparse: handling of EOS when no output produced

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=733171
  GStreamer | gstreamer (core) | git

           Summary: baseparse: handling of EOS when no output produced
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: thiagossantos at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Currently baseparse considers an error any case where it has received EOS and
still hasn't produced any output buffer.

This seems to try to care for the case where a whole stream is dropped because
the input is completely random for a parser (linking of wrong parser for a
given media format), but this seems to cause errors in the following valid
scenarios:

1) fakesrc num-buffers=0 ! h264parse ! fakesink

A valid scenario is of a completely empty stream, this shouldn't lead to an
error but just to EOS.

2) In h264parse, for example, it will only output buffers after it has received
an SPS, so it might have received valid data before and successfully parse
input buffers but drop them waiting for the SPS. This can happen with mpegts as
the input can be completely unaligned and doesn't need to start from a SPS. If
you have a very short attempt at playing an h264 out of mpegts it can make
baseparse error out and cause your whole pipeline fail. This happens when
quickly switching mpegts programs.

I'm willing to fix this, but I'd like to reach a sane decision on how to handle
this.

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