Implementing a Custom Audio Endpoint Enumerator
Beginning with Windows Server 2008 R2, you can implement a custom remote audio endpoint enumerator as part of a Remote Desktop protocol provider.
To implement a custom remote audio endpoint enumerator
Your custom endpoint enumerator solution should implement four main types of objects: device enumerator objects, device collection objects, device objects, and property store objects.
Object type Description
Device enumerator object
A device enumerator object provides the endpoint enumerator functionality. It exposes methods that return a default endpoint and specified collections of endpoints. For example, depending on the criteria specified, the enumerator can return communication endpoints, playback endpoints, or capture endpoints. The device enumerator object must implement the IMMDeviceEnumerator interface.
Device collection object
A device collection object represents a collection of audio devices. It must implement the IMMDeviceCollection interface.
A device object represents a particular audio device. It provides access to the audio device's property store and exposes the audio playback and capture interfaces available on the device. The device object must implement the IMMDevice and IMMEndpoint interfaces.
Property store object
A property store object exposes the properties associated with an audio device. Some of these properties are used by the system, but applications can store arbitrary properties with the audio endpoint as well.
All audio devices have the following three properties:IPropertyStore interface.
The custom endpoint enumerator must be implemented in a DLL that can be loaded into the audio system and other applications. The DLL must be signed so that secure processes can load it. The DLL must implement and export the GetTSAudioEndpointEnumeratorForSession function, which acts as an entry point to the custom endpoint enumerator.
The Remote Desktop Services service calls the QueryProperty method and sets the QueryType parameter to WTS_QUERY_AUDIOENUM_DLL to retrieve the name of the enumerator object.
Custom enumerator objects use COM-like interfaces and a COM-like reference counting mechanism, but they are not true COM objects. The custom endpoint enumerator must have the ability to work with legacy audio interfaces used by applications that do not support COM. For this reason, the custom endpoint enumerator must not rely on COM's life cycle management mechanism. Consumers of your audio endpoint enumerator, such as MMDevAPI.dll, load the custom endpoint enumerator DLL when required by user applications, and they will not unload the enumerator while the enumerator holds a reference to a device enumerator object, device collection object, device object, or property store object. It is not possible, however, for these consumers to track references to other types of objects owned by the custom endpoint enumerator. Accordingly, we recommend that your custom endpoint enumerator not create any objects that could outlive these four types of objects.
To implement a custom audio device enumerator, you must implement a custom audio endpoint. The way that your custom audio devices are linked is by using the following two statements:
We do not expect you to implement the full list of IMMDevice::Activate interfaces in your custom audio device enumerator. Instead, you should implement IAudioOutputEndpointRT and IAudioInputEndpointRT. You can optionally implement a few more, such as IAudioEndpointVolume. For any interface you do not implement, you should return E_NOINTERFACE (you must use this specific failure code). Windows will then fall back to a stock implementation of the interface (for example, IAudioClient2).
For additional reference documentation about how to implement and register audio endpoints, see IAudioInputEndpointRT. For a diagram that shows how WASAPI works, see User-Mode Audio Components. Note that all of user-mode audio is new beginning with Windows Server 2008.
- Creating a Remote Desktop Protocol Provider
Build date: 10/15/2013