GNOME Bugzilla – Bug 343837
[wavparse] can't handle WAV file with 'bext' header chunk
Last modified: 2006-06-14 08:21:48 UTC
I've a wav file which totem cannot play... Other wav files play fine, and the problematic file works in xmms and mplayer. Here's the output of the gst-launch command: gst-launch-0.10 filesrc location=deb.wav ! wavparse ! audioconvert ! audioresample ! alsasink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ERROR: from element /pipeline0/wavparse0: Could not demultiplex stream. Additional debug info: gstwavparse.c(1171): gst_wavparse_stream_headers (): /pipeline0/wavparse0: Invalid WAV header (no fmt at start): bext ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... FREEING pipeline ...
Created attachment 66733 [details] wav file wich won't play This is only the first 500 KB of the (big) wav file... Fails in totem and gst-launch, works with mplayer.
Should be fixed in -good CVS now: 2006-06-14 Tim-Philipp Müller <tim at centricular dot net> * gst/wavparse/gstwavparse.c: (gst_wavparse_peek_chunk_info), (gst_wavparse_peek_chunk), (gst_wavparse_stream_headers), (gst_wavparse_chain): When operating chain-based, don't make any assumptions about the chunking of the incoming data and make streaming work on days other than the second Thursday after a full moon. Also fix up debug messages here and there. Skip any 'bext' chunks in front of the 'fmt ' chunk. Fixes #343837. * gst/wavparse/gstwavparse.h: Cosmetic fix: remove trailing comma after last enum.