How to relate WAVE_MAPPER audio line with its audio device

Question

Hello fellow programmers,

I'm developing an application that among other things, enumerates all input audio devices (using SetupAPI) and then for each audio device, it lists all input audio lines (using winmm.dll).

Basically, the way I'm relating the two is getting the device path from the audio device and then using waveInMessage to compare the audio line's device path.

Now, I want to be able to do the same with the windows default [input] audio line (WAVE_MAPPER).

The problem is that using waveInGetDevCaps for WAVE_MAPPER returns "Microsoft Sound Mapper", and using waveInMessage with DRV_QUERYDEVICEINTERFACE returns an empty string.

Any suggestions on how to find out which device the Microsoft Mapper is mapping to?

Answer 1

Well for one I've found DirectSound to be a lot easier and with far less XP to Vista undocumented oddities (And far less undocumented oddities in general).

But probably the only way you'll work it out is to enumerate all the other devices and see which one matches the WAVE_MAPPER one.

Honestly though ... use DirectSound or, if you are able to do Vista and Win 7 only, use the Core Audio API. Winmm is an ANCIENT API and was pretty broken when it was first introduced ...

Answer 2

The device that WAVE_MAPPER is mapped to depends on the parameters passed to waveInOpen. From the documentation:

WAVE_MAPPER - The function selects a waveform-audio input device capable of recording in the specified format.

This means you can't check the device properties without actually opening it. Once you open it, you should be able to get the actual device ID with waveInGetID.

Answer 3

Please correct me if I'm wrong, but I've been watching some videos from past Microsoft conferences on sound development. On the latest one from Larry Osterman, he mentions new sound features in [I believe] Windows 7 that his team worked on.

One of the features was [the name is my interpretation] "device hot swap". Let's say your application is playing back using the "windows default sound playback" endpoint, and that at this moment is a set of USB Headphones. Suddenly you disconnect the headphones. Up to Windows 7, your application would crash [if you didn't foresee that test scenario]. In Windows 7 [and here's the hook to the original subject], IF you're using the Windows default playback device, Windows will gracefully and automatically swap the output stream to the new default, which could be the speakers.

What I'm trying to get to, is that I'm trying to fit the WAVE_MAPPER device into a class where it is not supposed to be. Maybe, conceptually speaking, the WAVE_MAPPER despite having the same capability of audio stream input and output, should be treated as an exception.

I'll try to be more concrete. In my application, I have a list of audio devices, and each audio device has a list of audio lines. Audio devices have properties such as VID and PID that are easily discoverable through the SetupAPI and can be related to audio lines via winmm's waveInMessage. WAVE_MAPPER doesn't follow that logic and I was trying to make it do.

So instead of trying to relate the WAVE_MAPPER with its underlying audio device, I will just treat it as what it is: the default audio device.