[Bug 775025] New: wavparse fails at end of stream with "No valid input found before end of stream"

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Thu Nov 24 15:59:24 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=775025

            Bug ID: 775025
           Summary: wavparse fails at end of stream with "No valid input
                    found before end of stream"
    Classification: Platform
           Product: GStreamer
           Version: 1.10.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: John_Sauter at systemeyescomputerstore.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

My application uses wavparse to load a WAV file into a buffer.  It started
failing with Gstreamer 1.10 as distributed in Fedora 25.  It appears that
wavparse now fails at end of stream, shutting down the pipeline.  I created a
simple demonstration of the problem as follows:

 gst-launch-1.0 filesrc location=test.wav ! wavparse ! fakesink

where test.wav is a one-second WAV file created with audacity, format S16LE,
two channels, both containing a 440Hz sine wave.  I tried other formats with
the same result.  The output is as follows:

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstWavParse:wavparse0: The stream is
of a different type than handled by this element.
Additional debug info:
gstwavparse.c(2221): gst_wavparse_loop ():
/GstPipeline:pipeline0/GstWavParse:wavparse0:
No valid input found before end of stream
Execution ended after 0:00:00.000384326
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Version numbers on my computer are: glib 2.50.1 ages 5001 and 1, gtk 3.22.2 and
GStreamer 1.10.0.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list