GNOME Bugzilla – Bug 689691
WASAPI plugin not work
Last modified: 2014-11-27 13:28:26 UTC
I tried the component with: gst-launch-0.10.exe -v wasapisrc ! filesink location="prv" Setting pipeline to PAUSED ... /GstPipeline:pipeline0/GstWasapiSrc:wasapisrc0.GstPad:src: caps = audio/x-raw-int, width=(int)16, depth=(int)16, rate=(int)8000, channels=(int)1, signed=(boolean)true, endianness=(int)1234 Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstWasapiSrcClock /GstPipeline:pipeline0/GstFileSink:filesink0.GstPad:sink: caps = audio/x-raw-int, width=(int)16, depth=(int)16, rate=(int)8000, channels=(int)1, signed=(boolean)true, endianness=(int)1234 But in the file "prv" I can see only "NULL" character (zero). What's I'm wrong? =================================================================== I tried "gst-launch-0.10 -v audiotestsrc ! wasapisink", but I get a error: Setting pipeline to PAUSED ... /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = audio/x-raw-int, width=(int)16, depth=(int)16, rate=(int)8000, channels=(int)1, signed=(boolean)true, endianness=(int)1234 Pipeline is PREROLLING ... /GstPipeline:pipeline0/GstWasapiSink:wasapisink0.GstPad:sink: caps = audio/x-raw-int, width=(int)16, depth=(int)16, rate=(int)8000, channels=(int)1, signed=(boolean)true, endianness=(int)1234 Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock ERROR: from element /GstPipeline:pipeline0/GstWasapiSink:wasapisink0: Could not write to resource. Additional debug info: gstwasapisink.c(241): gst_wasapi_sink_render (): /GstPipeline:pipeline0/GstWasapiSink:wasapisink0: IAudioRenderClient::GetBuffer () failed: AUDCLNT_E_BUFFER_SIZE_ERROR Execution ended after 33002000 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... /GstPipeline:pipeline0/GstWasapiSink:wasapisink0.GstPad:sink: caps = NULL /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = NULL Setting pipeline to NULL ... Freeing pipeline ...
Thanks for the bug report, and sorry no one got around to looking at it sooner. GStreamer 0.10 is rather old and no longer maintained, and there have been quite a few changes in the wasapi elements since this bug report, so I think it's best to close this. Please re-open or file a new bug if you still have issues with recent versions of GStreamer 1.x, thanks!