Speaker endpoints are hardcoded to be "Speakers" because there were so many devices with speaker bridge pin friendly names like "volume control" or "master volume" etc. which made no sense at all as a device name. It was something that we didn't want to do but it fixed a common problem across a lot of legacy devices. You are correct that we had to make some suboptimal design choices to accommodate the simple devices which comprise the vast majority of hardware. Regards, Mitch -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Eugene Muzychenko Sent: Monday, December 18, 2006 7:19 PM To: Hakon Strande Subject: [wdmaudiodev] Re: A custom endpoint name for the output device in Vista Hello Hakon! > That node type name is hard coded in Vista By Design. But why? If there is a category field and an OPTIONAL name field, what is a logic for that? For applications, it is much more better to look for an appropriate endpoint by a category, not by a name. For a driver, it may be better to specify a compatible pin category but a different name to distinguish between similar subdevices. I see that some changes from XP to Vista are made as there were only dumb, simplest audio devices having only microphone/line inputs and a speaker output :( Regards, Eugene ****************** 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/ ****************** 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/