[wdmaudiodev] Re: Vista 32 + friendly names

  • From: Uwe Kirst <u.kirst@xxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Mon, 05 Nov 2007 22:12:55 +0100

David A. Hoatson schrieb:
Hello,

I'm still not 100% sure how Vista determines what device name to display, so it would be great if someone from Microsoft would give a complete description. Things certainly changed from XP. If there is a Topology driver, then it appears that the Category element on the destination pin that is connected to the wave out device is used. In addition, if you want to have the system sounds control panel applet show speaker configuration (to allow selection of surround sound speaker setup), then that Topology Category element must be KSNODETYPE_SPEAKER which will name your device "Speakers" with your driver name concatenated to the end. In this case the Name element of the pin descriptor is ignored.


This happens also in my driver. Speaker is named speaker. Therefore I used the KSNODETYPE_SPEAKER only once and used other KSNODETYPEs for other devices. For the recording devices I tried KSNODETYPE_MICROPHONE and KSNODETYPE_DIGITAL_AUDIO_INTFACE. Both does not seem to work, however KSNODETYPE_LINE_CONNECTOR seems to work. Does anyone know why? I would like to use KSNODETYPE_DIGITAL_AUDIO_INTERFACE (I have seem other products using KSNODETYPE_DIGITAL_AUDIO_INTERFACE, so basically it seems to be possible).

If you don't have a topology driver, then the name of the destination pin returned in CWaveMiniport::GetDescription() is used. For multi-channel multi-device drivers that might have reused the filter description tables, this presents a problem in Vista as all the devices end up being the same name. Unique filter description tables are required for each device in Vista.

In other words you have much less control over how your devices are named with Vista if you want to support surround sound speaker setups.

I know that this isn't even close to a complete description, since if you change the category of your pin it will effect the name the will be used in the pin descriptor.

Hopefully someone from Microsoft will answer and correct me if I am wrong on any of the above points and fill in the missing details.

That would be great.

Hello,

It seems that the device names (friendly names) of my mme audio driver are reported to applications which are running with administrator rights only. If the arbitrary application does not run as administrator, the device names will not be listed.

How can I change this?

My original question was related to a user mode driver component of my driver which provides additional devicenames, which are not directly controlled by windows, but appear in the list of audio devices of an arbitary audio application. It must be something about the access rights management that is somehow different from XP.
Maybee driver calls are not allowed for any user?

Thank you
/Uwe



******************

WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:    mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:  mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:    mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx

URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/

Other related posts: