[Bug 788416] New: GStreamer no longer plays Vorbis files with invalid packets

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 788416
           Summary: GStreamer no longer plays Vorbis files with invalid
                    packets
    Classification: Platform
           Product: GStreamer
           Version: 1.12.2
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: psychonaut at nothingisreal.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

After a recent update (probably from GStreamer 1.12.0 to 1.12.1)
GStreamer-based media players no longer play many of my Ogg Vorbis files.  An
example, with the attached foo.ogg:

$ gst-play-1.0 foo.ogg
Press 'k' to see a list of keyboard shortcuts.
Now playing /tmp/foo.ogg
ERROR Could not decode stream. for file:///tmp/foo.ogg
ERROR debug information: gstvorbisdec.c(352): vorbis_handle_header_packet ():
/GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstVorbisDec:vorbisdec0:
couldn't read header packet (-132)
Reached end of play list.

ogginfo doesn't report any problems with the file, but FFmpeg does:

$ ffmpeg -v error -i foo.ogg -f null -
[Vorbis parser @ 0x55de9d387700] Invalid packet

Despite this, FFmpeg-based players can still play the file.

I suppose that if the Vorbis files aren't to spec, then technically it's OK for
GStreamer to fail.  But it had been playing them perfectly and without
complaint for the last 15 years, so it's a bit annoying that it's suddenly
refusing to play them now.  Is there any chance that the old behaviour could be
restored, so that GStreamer at least *attempts* to play the Vorbis files rather
than failing outright?

This problem may be related to Bug 784530, which is about GStreamer refusing to
play Vorbis streams with a different kind of corruption.

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