[Bug 681819] h264parse: parsing disabled in case of fakesink pipeline

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=681819
  GStreamer | gst-plugins-bad | 0.10.23

Mark Nauwelaerts <mnauw> changed:

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

--- Comment #1 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2012-09-14 11:18:50 UTC ---
Not sure how much "a bug" this is.

It makes sense for h264parse to get out of the way if input == output.  Also,
in this (diagnostic) case/pipeline, h264parse could be triggered by setting an
appropriate capsfilter, rather than modifying code.

That said, the underlying problem is probably that there are many
interpretations and levels of 'passthrough'; whether that refers to leaving all
of the input intact, or only the data-units and still setting/modifying
metadata (what kind of metadata then, flags and/or timestamps ?) etc.

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