GNOME Bugzilla – Bug 681201
0.11 - Remuxing webm file fails with "vorbis stream headers missing"
Last modified: 2012-08-09 09:08:08 UTC
Created attachment 220319 [details] png of pipeline running I am trying to remux a webm file in Transmageddon. It fails with the following errors on the console: Could not multiplex stream. matroska-mux.c(1773): gst_matroska_mux_audio_pad_setcaps (): /GstPipeline:pipeline0/GstEncodeBin:encodebin0/GstWebMMux:muxer: vorbis stream headers missing or malformed we got an error, life is shit Could not multiplex stream. I can upload the input file if wanted.
Managed to reproduce with gst-launch - gst-launch-1.0 uridecodebin uri=file:///home/cschalle/Videos/got.webm caps=audio/x-vorbis ! webmmux ! filesink location=test.webm Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Missing element: Uncompressed packed YUV 4:4:4 decoder WARNING: from element /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0: No decoder available for type 'video/x-raw, format=(string)I420, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt709, framerate=(fraction)10000000/333667'. Additional debug info: gsturidecodebin.c(882): unknown_type_cb (): /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0 ERROR: from element /GstPipeline:pipeline0/GstWebMMux:webmmux0: Could not multiplex stream. Additional debug info: matroska-mux.c(1773): gst_matroska_mux_audio_pad_setcaps (): /GstPipeline:pipeline0/GstWebMMux:webmmux0: vorbis stream headers missing or malformed ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ...
Tested some more, adding vorbisparse after uridecodebin makes this work. But I shouldn't need to plug vorbisparse manually should I? Especially since my Transmageddon pipeline is a uridecodebin -> encodebin pipeline.
Maybe related to bug #681335 Could happen if we first get a caps event without the stream headers (because the decoder or whatever wanted to provide caps asap) and only later a new caps event with the complete information is sent.
I think it's basically bug #640589
*** This bug has been marked as a duplicate of bug 640589 ***