This project has moved and is read-only. For the latest updates, please go here.

WasapiCapture not reusable

Feb 28, 2012 at 6:34 PM

I've been writing an app that records chunks of input audio to multiple files, with gaps between, but I discovered that if I try a call sequence which essentially boils down to this:

WasapiCapture client = new WasapiCapture();
// set up output processor for file 1
// wait for end of content for file 1
// set up output processor for file 2

then the second StartRecording() fails inside InitializeCaptureDevice() at the call to audioClient.Initialize()

I was able to work around this by disposing of my WasapiCapture client and constructing a new one each time, because my system load was low enough that I didn't care about the needless thread destroy/create and whatever the overhead of fetching a new IAudioClient might be. In other circumstances all that unnecessary work might be a problem though.

I see the MS documentation for IAudioClient states that "the client must successfully call Initialize once and only once to initialize the audio stream between the client and the device" (italics mine), so I'm thinking some strategy where NAudio remembers the WaveFormat it uses in a call to audioClient.Initialize() and on subsequent calls to InitializeCaptureDevice(), throws if a recording is active, does nothing if the WaveFormat has not changed, or disposes the old audioClient and initializes a new one if the WaveFormat has changed. Doing something like that would probably also need some modification to CaptureThread so that it didn't exit until the WasapiCapture object is disposed.

Mar 2, 2012 at 2:05 PM

yes, WasapiCapture just works for one-time recording, and it is best to create a new one. Probably is something that should be fixed in a future NAudio. Will turn this into a work item.


Mar 2, 2012 at 2:06 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.