[wdmaudiodev] Re: Exposing a topology to Vista

  • From: Hakon Strande <hakons@xxxxxxxxxxxxxxxxxxxxx>
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Mon, 14 Apr 2008 12:16:33 -0700

For KSNODETYPE is SPEAKERS, we will provide a "Speakers" name for the device 
regardless of the friendly name of the bridge pin.  This was decided on provide 
a slightly better WYSIWYG experience with legacy drivers on Vista where 
friendly names were all over the place with names like "Mixer" due to legacy 
fallout from how IHVs had exposed devices in sndvol32 for years vs the new 
audio endpoint (peripheral) focused user experience in Vista.

We only do this for the name of the endpoint so maybe you can supply 2 or more 
different icons to differentiate between the endpoints?

In W7 we want to get rid of this hardcoded behavior.


Hakon Strande<mailto:HakonS@xxxxxxxxxxxxx> | Windows Sound Team PM | (p) 

From: wdmaudiodev-bounce@xxxxxxxxxxxxx 
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Eckert
Sent: Tuesday, March 11, 2008 7:27 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Exposing a topology to Vista

What category should we use for multiple multichannel outputs that need to be 
uniquely identified?
If have 16 output channels that we want to expose as two 7.1 devices for 
instance, if we use the speaker category we can set the configuration as 7.1 
but cannot distinguish between the two and if we use another category we can't 
set the configuration and the device is reduced to setereo.

Tom Eckert
AudioScience Inc.

Hakon Strande wrote:
I would like to ask the community to please use the exact ksnodetype that 
matches the device you are connecting to Windows. These form factor hints are 
used by the system for policy decisions. If the logical device is a pair of 
headphones then please use the KSNODETYPE that matches that form factor device 

You can read more about how device topology works in Windows Vista here:




More info relating to Windows Vista and audio:



Hakon Strande<mailto:HakonS@xxxxxxxxxxxxx> | Windows Sound Team PM | (p) 

From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> 
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Pages
Sent: Monday, March 10, 2008 3:20 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: Exposing a topology to Vista

Hi Andrew,

Going from memory of a discussion on this list a couple of years back (and I 
might well be wrong), I think Vista requires the default playback endpoint to 
KSNODETYPE_SPEAKER pin, it always appears "Speakers" whereas a 
KSNODETYPE_LINE_CONNECTOR pin is given its pin name. As far as I know, none of 
this Vista-specific stuff has been documented in the WDK as yet.


----- Original Message -----
From: Andrew Murray<mailto:amurray@xxxxxxxxxxxxxx>
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Sent: Tuesday, March 11, 2008 1:41 AM
Subject: [wdmaudiodev] Exposing a topology to Vista


I have constructed an audio driver that currently consists of a WaveCyclic 
filter and a Topology filter. The topology I expose from these filters appears 
fine in Windows XP and KsStudio. However I am not having as much luck within 

When the 'sounds' applet from the control panel in Vista is opened the correct 
playback and recording endpoints appear and have the correct properties 
associated with them (i.e. volume, mute, etc). However a red cross appears on 
the speaker in the system tray and the message "No audio device is installed" 
appears when I click on 'Open Volume Mixer'...

I've searched the archives for this group and browsed the internet but cannot 
find any clues as to what may be causing this. Does the group have any 
suggestions? Or can someone point me in the right direction, particularly in 
where I can find documentation regarding the way in which Vista (or XP for that 
matter) discovers the driver's topology.

Most of my topology's pins have custom names; does Vista look for specific 


Andrew Murray

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.6 - Release Date: 06/03/2008 00:00

PNG image

PNG image

Other related posts: