GNOME Bugzilla – Bug 796581
Crash when wasapisink is removed from pipeline.
Last modified: 2018-11-03 14:26:30 UTC
When wasapi is stopped (state set to NULL) and removed from pipeline, the program crashes. I've pretty much followed this example https://gstreamer.freedesktop.org/documentation/application-development/advanced/pipeline-manipulation.html#dynamically-changing-the-pipeline (but used only wasapisrc, audioconvert and wasapisink). The error shown on log is the following: :00:07.985599364 5144 042788A0 INFO wasapisink gstwasapisink.c:680:gst_wasapi_sink_reset:<autoaudiosink0-actual-sink-wasapi> reset called 0:00:07.985654852 5144 042788A0 ERROR wasapisink gstwasapisink.c:687:gst_wasapi_sink_reset:<autoaudiosink0-actual-sink-wasapi> IAudioClient::Stop failed (1): Incorrect function.
I get this exact error, except instead of crashing my program freezes when I try to start playback again. I'm curious if the patches from https://bugzilla.gnome.org/show_bug.cgi?id=796354 would fix this, but I don't currently have an appropriate build environment set up at the moment.
Actually, I think this is fixed in https://bugzilla.gnome.org/show_bug.cgi?id=796280
Hm. So I decided to set up a build environment (Windows 7, msys2, 32-bit) and built the current 1.14 branch (479b1ef76) and copied the wasapi dll over my current environment's dll. The sound from that build is terribly garbled and sounds weird -- and of course, didn't fix the crash either. I am on a VM. However, the current 1.14.1 release in msys2 plays music that isn't garbled, so I suspect that isn't the issue.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/735.