1. Core Audio API
Augustinas Žiliukas IT 3 grupė

2. History 1991 – Windows Multimedia Extensions (aka MME, aka WinMM)
Microsoft decided to add audio API for their OS (Windows 3.0).
1995 – DirectSound (aka DirectX Audio)
Microsoft needed to improve their audio API to get attention from gaming industry, which currently were based on BioS.
1998 – Windows Driver Model / Kernel Streaming (aka WDM/KS)
With WDM, both MME and DirectSound audio now passed through something call the Kernel Audio Mixer (usually referred to as the KMixer). KMixer was a kernel mode component responsible for mixing all of the system audio together. KMixer introduced latency.
2007 – Windows Core Audio
Was presented with the release of Windows Vista .Kmixer was removed and most of the audio components were moved from kernel land to user land(API).

3. Audio Capabilities Low-latency Improved reliability Improved security
Assignment of particular system-wide roles
Software abstraction of the audio endpoint devices

4. Core Audio 4 APIs
Multimedia Device (MMDevice) API.Clients use this API to enumerate the audio endpoint devices in the system.
Windows Audio Session API (WASAPI).Clients use this API to create and manage audio streams to and from audio endpoint devices.
DeviceTopology API. Clients use this API to directly access the topological features (for example, volume controls and multiplexers) that lie along the data paths inside hardware devices in audio adapters.
ENDpointVolume API. Clients use this API to directly access the volume controls on audio endpoint devices. This API is primarily used by applications that manage exclusive-mode audio streams.

5. MMDevice API
Import Mmdeviceapi.h

6. WAS API
Import:Audioclient.h, Audiopolicy.h

7. DeviceTopology API
Import Devicetopology.h

8. EndpointVolume API
Import Endpointvolume.h

10. Thank you for your attention!