Frequently, the application can recover from this error. Many of the methods in WASAPI return error code AUDCLNT_E_DEVICE_INVALIDATED if the audio endpoint device that a client application is using becomes invalid.

After initializing a stream, the client can obtain references to the other WASAPI interfaces by calling the IAudioClient::GetService method. The client calls the IAudioClient::Initialize method to initialize a stream on an endpoint device. To access the WASAPI interfaces, a client first obtains a reference to the IAudioClient interface of an audio endpoint device by calling the IMMDevice::Activate method with parameter iid set to REFIID IID_IAudioClient. The first of these is the IAudioClient interface. To record an audio stream from a capture endpoint device, an application periodically reads audio data from a capture endpoint buffer. The audio engine mixes the streams from the various applications. To play an audio stream through a rendering endpoint device, an application periodically writes audio data to a rendering endpoint buffer. The audio engine transports audio data between an endpoint buffer and an endpoint device. The audio engine is the user-mode audio component through which applications share access to an audio endpoint device. The system can manage all of the streams in the session as a single unit. Through the session abstraction, a WASAPI client can identify an audio stream as a member of a group of related audio streams. Header files Audioclient.h and Audiopolicy.h define the WASAPI interfaces.Įvery audio stream is a member of an audio session. The Windows Audio Session API (WASAPI) enables client applications to manage the flow of audio data between the application and an audio endpoint device.

Wasapi audacity