GNOME Bugzilla – Bug 687135
riff: unknown WAVE_FORMAT_EXTENSIBLE audio format in wavparse
Last modified: 2015-06-23 13:49:29 UTC
I cannot play certain .wav files in Guayadeque in Ubuntu 12.10. I receive a gstreamer error. These files play in Rhythmbox and play in J River media center in Windows, so I'm sure the files are fine. I contacted the Guayadeque developer. He tested a file and received the following bug report he told me I should send to you: gst-launch-0.10 --gst-debug-level=2 playbin2 uri="file:///home/jrios/Downloads/05%20-%20Mellow%20Yellow%20(Mono).wav" Setting pipeline to PAUSED ... Pipeline is PREROLLING ... 0:00:00.020415281 5306 0x23bb9e0 WARN riff riff-media.c:1531:gst_riff_create_audio_caps: failed to add channel layout 0:00:00.020453854 5306 0x23bb9e0 WARN riff riff-media.c:1632:gst_riff_create_audio_caps: Unknown WAVE_FORMAT_EXTENSIBLE audio format 0:00:00.020481551 5306 0x23bb9e0 WARN wavparse gstwavparse.c:1669:gst_wavparse_stream_headers:<wavparse0> error: No caps found for format 0x0, 0 channels, 0 Hz ERROR: from element /GstPlayBin2:playbin20/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstWavParse:wavparse0: Could not determine type of stream. 0:00:00.020664561 5306 0x23bb9e0 WARN wavparse gstwavparse.c:2110:gst_wavparse_loop:<wavparse0> error: Internal data flow error. 0:00:00.020691010 5306 0x23bb9e0 WARN wavparse gstwavparse.c:2110:gst_wavparse_loop:<wavparse0> error: streaming task paused, reason error (-5) Additional debug info: gstwavparse.c(1669): gst_wavparse_stream_headers (): /GstPlayBin2:playbin20/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstWavParse:wavparse0: No caps found for format 0x0, 0 channels, 0 Hz ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... I'm completely new to Ubuntu, so please let me know what I should do. Thanks, Chris
Sorry for the delay. You've filed this bug in the wrong product. Instead of having filed it under "Bindings->gstreamermm-plugins-good", you should have filed it under "Platform->GStreamer". Reassigning to the correct product. Please be patient.
Thanks for the bug report. I believe this issue might be fixed in GStreamer git (1.x) already. Any chance you could make such a .wav file available to us so we can test it (and fix it if needed)? The first few kB will probably do the job already: $ head --bytes=750k foo.wav > head.wav if you could attach that to this bug report, that would be helpful.
chris: ping?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!