[gstreamer-bugs] [Bug 576142] New: [vorbisenc] Non-header output buffers have NULL caps

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

  GStreamer | gst-plugins-base | Ver: git
           Summary: [vorbisenc] Non-header output buffers have NULL caps
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: mail at renestadler.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I just noticed the following:

$ gst-launch-0.10 audiotestsrc num-buffers=1 ! vorbisenc ! identity ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

** (gst-launch-0.10:10122): WARNING **: identity0: could not get in_size

(gst-launch-0.10:10122): GStreamer-CRITICAL **: gst_caps_is_subset: assertion
`subset != NULL' failed

(gst-launch-0.10:10122): GStreamer-CRITICAL **: gst_caps_is_fixed: assertion
`GST_IS_CAPS (caps)' failed

** (gst-launch-0.10:10122): CRITICAL **: gst_base_transform_find_transform:
assertion `gst_caps_is_fixed (caps)' failed

[...]

I.e. putting a basetransform based element after vorbisenc shows that the
buffer caps are actually NULL. Apparently it has always been this way but
nobody noticed it before :)

Attaching proposed trivial patch.


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