Редагувати

Поділитися через


Volume Controls

Clients that manage shared-mode streams typically use the ISimpleAudioVolume and IAudioSessionEvents interfaces in WASAPI to control and monitor the stream volume levels. Through the methods in the ISimpleAudioVolume interface, the client can get and set the volume levels of the audio sessions that the shared-mode streams belong to. If Sndvol or another application changes the session volume level, the client can receive notification of the change through the IAudioSessionEvents interface.

Clients that manage exclusive-mode streams typically use the IAudioEndpointVolume and IAudioEndpointVolumeCallback interfaces in the EndpointVolume API to control and monitor the stream volume levels. Through the methods in the IAudioEndpointVolume interface, the client can get and set the volume level of an audio endpoint device. If Sndvol or another application changes the volume level of the endpoint device, the client can receive notification of the change through the IAudioEndpointVolumeCallback interface.

As explained in Audio Sessions, Sndvol is the system volume-control program. It displays volume controls for the audio-rendering endpoint devices in the system. (Currently, it does not display the volume controls for audio-capture endpoint devices.) To view the volume controls for a particular device, click Device in the menu bar and select a device name from the list of available devices.

The Sndvol window separates the volume controls for a device into two groups. The group box on the left side of the window is labeled Device. The Device box contains a single volume control that is controlled by the IAudioEndpointVolume interface. Changes that the user makes to this volume control can be monitored through the IAudioEndpointVolumeCallback interface.

The group box on the right side of the Sndvol window is labeled Applications. The Applications box contains the volume controls for the applications that currently share the device. For applications that use the device in shared mode, the volume controls represent the volume levels that are controlled by the ISimpleAudioVolume interface. Changes that the user makes to these volume controls can be monitored through the IAudioSessionEvents interface.

Although a shared-mode application can use its IAudioSessionEvents interface to monitor changes that the user makes to the application's volume control in the Applications box in the Sndvol window, the application cannot monitor changes to the volume controls of other, unrelated applications. Similarly, an application can change the volume levels of its audio sessions through the ISimpleAudioVolume interface, but it cannot change the volume levels of sessions that belong to other, unrelated applications.

However, two or more related applications (or instances of the same application) can share the same volume control in the Applications box in the Sndvol window either by assigning their audio streams to the same cross-process session or by associating their respective sessions with the same grouping parameter. For more information, see Audio Sessions and Grouping Parameters.

WASAPI provides two additional interfaces, IChannelAudioVolume and IAudioStreamVolume, to control the volume levels of shared-mode streams. These interfaces are mainly used by specialized clients that require control over the volume levels of either individual channels in a session or individual streams in a session.

The DeviceTopology API enables clients to access the volume controls in the topologies of audio adapters. However, clients that manage exclusive-mode streams typically use the EndpointVolume API instead of the DeviceTopology API to control the stream volume levels. The EndpointVolume API simplifies control of the volume of an endpoint device in two ways. First, if an endpoint device implements a hardware volume control, the DeviceTopology API requires the client to traverse the device topology in search of the hardware control. In contrast, the EndpointVolume API automatically finds the hardware volume control for the client. Second, if the endpoint device does not implement a hardware volume control, a DeviceTopology client must implement a volume control in software. In contrast, the EndpointVolume API automatically substitutes a software volume control for the missing hardware control.

The following sections describe volume controls for audio sessions and for audio endpoint devices:

Programming Guide