Sometimes waveIn_DataAvailable gets called with BytesRecorded = 0 after recording is started about naudio

[markheath]

Might be worth looking at WasapiCapture now that it supports built-in resampling in NAudio 2.1.0

[markheath]

Not seen this myself. You might want to try WaveInEvent instead

[Vort]

@markheath, did you tried my test program with 1.7.3 version or newer?

[markheath]

sorry, haven't had a chance to try this myself. However, if I had an application that needed to stop and start recording frequently with small gaps, I would actually not use StopRecording and StartRecording. Instead I would just have a boolean flag saying whether I was currently recording and in my DataAvailable event I'd just ignore it if my flag wasn't set

[Vort]

that needed to stop and start recording frequently with small gaps

Gaps are small in this test program because it is easier to reproduce the problem in such way.

Instead I would just have a boolean flag

I was thinking about solution with data discarding, but it have some problems:

1. It uses more system resources that is needed for such task. I know that overhead is low, but ideally it should be zero.
2. User may want to disconnect recording device between transmissions.

sorry, haven't had a chance to try this myself

So this report is valid and should not be closed?
I was created it not because I can't think of some workaround.
Just because I wanted to help in making this library better.

[markheath]

OK thanks I see. I was just doing a cleanup of old stuff, sounds like this is a genuine bug, but not one I've had time to look at. Very happy to accept PRs for anyone who wants to tackle fixing this. One idea I've had for some time is that the WaveIn and WaveOut statuses need to include Starting and Stopping states which will make managing edge cases like restarting while we're still stopping much easier.

[nathan-alden-sr]

I just ran into this problem myself. If I record a short clip (say, a second or so) and then call StopRecording(), then StartRecording() very shortly thereafter, I get that exception.

[markheath]

thanks for reporting. If I were doing NAudio again from scratch I'd have some additional "starting" and "stopping" states on WaveIn, which I think would make it easier to code around issues where recording (and playback) start and stop very quickly. Remember with recording that you can always capture soundcard data without necessarily "recording" it to a file. This is quite a common approach, so starting recording is just flipping a boolean flag to say we want to keep captured audio. It might help in the short term until we can get this bug fixed.

[nathan-alden-sr]

@markheath Thanks. 👍 Nice little library. Took me no longer than 5 minutes to get it recording to a MemoryStream.

[anthonyraymond]

I found a workaround, definely not the best way to handle it but...

You have to create a new WaveIn and use use the same MemoryStream each time you want to record.

MemoryStream stream = waveIn.MemoryStream;
waveIn = new WaveIn();
waveIn.MemoryStream = stream;
waveIn.WaveFormat = new WaveFormat(44100, 1);
waveIn.DataAvailable += waveIn_DataAvailable;
waveIn.RecordingStopped += waveIn_RecordingStopped;

// record one time, then stop recording, then create a new WaveIn, and so on...

It's dirty, but it works.

[markheath]

not sure why you need a new instance of WaveIn here? Just start recording again and write to the same memory stream if you want

[lixikun]

Do we have a solution for this Exception?
waveIn_RecordingStopped: exception=NAudio.MmException: WaveStillPlaying calling waveUnprepareHeader
в NAudio.MmException.Try(MmResult result, String function)
в NAudio.Wave.WaveInBuffer.Reuse()

[Vort]

// record one time, then stop recording, then create a new WaveIn, and so on...

@anthonyraymond thanks. I tried it and it works, but not for too long.
In my case (I don't use MemoryStream), program leaks handles with every reinitialization.
Which means that after some amount of start-stop cycles, not only your program can't start recording anymore, but any other program in the system.
After I added waveIn?.Dispose(); before waveIn = new WaveIn();, handle leak stopped.
But who knows what other surprises are still waiting with this solution.
(My comment is vaild for version 1.7.3. What is the behaviour of previous and later versions, I don't know)

[rey-allan]

Might be worth looking at WasapiCapture now that it supports built-in resampling in NAudio 2.1.0

This worked for me! Thanks for the suggestion!