[Bug 723125] New: wavparse: Fails if some broadcast wave format (BWF) tags preceed fmt chunk

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=723125
  GStreamer | gst-plugins-good | git

           Summary: wavparse: Fails if some broadcast wave format (BWF)
                    tags preceed fmt chunk
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: mike at mikeasoft.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Currently if a file doesn't contain a fmt tag as the first section in the
header wavparse will search for it until it either finds it or comes across an
unknown tag. The present implementation is configured to ignore a number of
known header sections, however this doesn't include headers from the Broadcast
Wave Format (BWF). This can result in wavparse failing to play wave files with
additional BWF metadata (if this metadata precedes the fmt section).

This can be reproduced with the attached sample which was produced by a Sound
Devices 702 audio recorder. When played via a simple playbin it produces the
following output:

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element
/GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstWavParse:wavparse0:
Could not determine type of stream.
Additional debug info:
gstwavparse.c(1966): gst_wavparse_stream_headers ():
/GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstWavParse:wavparse0:
Invalid WAV header (no fmt at start): iXML
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...

The attached patch makes wavparse aware of all the BWF tags and so allows the
clip to play correctly.

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