[wdmaudiodev] Re: Vista Build 5270 + friendly names for audio driver wave devices
- From: "Uwe Kirst" <U.Kirst@xxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Thu, 19 Jan 2006 18:59:48 +0100 (MET)
Thank you,
I will try that,
Uwe
> --- Ursprüngliche Nachricht ---
> Von: "Mitchell Rundle" <mitchr@xxxxxxxxxxxxx>
> An: <wdmaudiodev@xxxxxxxxxxxxx>
> Betreff: [wdmaudiodev] Re: Vista Build 5270 + friendly names for audio
> driver wave devices
> Datum: Tue, 17 Jan 2006 10:15:51 -0800
>
> Yes, you can do that. The friendly name lookup is added to the registry
> by ks.inf (search ks.inf for "MediaCategories"). You can add additional
> friendly names via your inf following the same pattern.
>
> For example:
>
> ...
> AddReg=PinNameRegistration
>
> [PinNameRegistration]
> HKLM,%MediaCategories%\%GUID.Analog_12%,Name,,%Name.Analog_12%
> HKLM,%MediaCategories%\%GUID.Analog_34%,Name,,%Name.Analog_34%
> ...
>
> [Strings]
> ...
> MediaCategories="SYSTEM\CurrentControlSet\Control\MediaCategories"
> ...
> GUID.Analog_12="{6A66CCD2-14D2-4ea4-A034-251F3FAA14D7}"
> GUID.Analog_34="{6A66CCD3-14D2-4ea4-A034-251F3FAA14D7}"
> ...
> Name.Analog_12="Analog (1+2)"
> Name.Analog_34="Analog (3+4)"
> ...
>
> Note that the first GUID is generated with guidgen. Subsequent GUIDs
> are incremental to keep them proximal in the registry.
>
> Regards,
> Mitch Rundle
> Microsoft Corp.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of uwe kirst
> Sent: Monday, January 16, 2006 1:30 AM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: Vista Build 5270 + friendly names for audio
> driver wave devices
>
> Hello Mitch,
>
> I agree with Jeff that is should be possible to give a individual name
> to each device or endpoint.
> For example our product uses the following names which mostly do not
> correlate with any of the ms typs:
>
>
> Analog (1+2)
> Analog (3+4)
> Analog (5+6)
> Analog (7+8)
> Analog (9+10)
> SPDIF
> ADAT1(1+2)
> ADAT1(3+4)
> ADAT1(5+6)
> ADAT1(7+8)
> ADAT2(1+2)
> ADAT2(3+4)
> ADAT2(5+6)
> ADAT2(7+8)
>
>
> Regards,
> Uwe
>
> Jeff Pages wrote:
>
> > Mitch,
> >
> > I wonder if you could tell me how to differentiate between multiple
> > endpoints of the same type, say a card with four or eight general
> > purpose line inputs? I'd like to be able to call them Line Input A,
> > Line Input B, etc., or some such thing that correlates with the
> > physical input connectors.
> >
> > Jeff Pages
> > Innes Corporation Pty Ltd
> >
> > ----- Original Message ----- From: "Mitchell Rundle"
> > <mitchr@xxxxxxxxxxxxx>
> > To: <wdmaudiodev@xxxxxxxxxxxxx>
> > Sent: Saturday, January 14, 2006 5:12 AM
> > Subject: [wdmaudiodev] Re: Vista Build 5270 + friendly names for audio
>
> > driver wave devices
> >
> >
> > Device names, or more correctly "Audio Endpoint" display names are
> > derived from bridge pin friendly names. These friendly names come
> > from "Name" GUID in the KSPIN_DESCRIPTOR of each bridge pin. If you
> > are writing an adapter driver, then this is in your PCPIN_DESCRIPTOR
> tables.
> > The "Volume Control" string corresponds to the name GUID
> > KSAUDFNAME_VOLUME_CONTROL. You should probably change that to
> > KSNODETYPE_SPEAKER.
> >
> > Here are our recommendations for the pin categories and names of
> > bridge pins that represent jacks or USB endpoints:
> >
> > For speakers:
> > category = name = KSNODETYPE_SPEAKER
> >
> > For headphones:
> > category = name = KSNODETYPE_HEADPHONES
> >
> > For microphone:
> > category = name = KSNODETYPE_MICROPHONE
> >
> > For line in or out:
> > category = name = KSNODETYPE_LINE_CONNECTOR
> >
> > For SPDIF in or out:
> > category = name = KSNODETYPE_SPDIF_INTERFACE
> >
> > For headset microphone:
> > category = name = KSNODETYPE_PERSONAL_MICROPHONE
> >
> > For headset earphone:
> > category = name = KSNODETYPE_COMMUNICATION_SPEAKER
> >
> > WRT to the last 2, note that in Vista, the following 2 lines have been
>
> > added to ksmedia.h
> >
> > #define KSNODETYPE_HEADSET_MICROPHONE KSNODETYPE_PERSONAL_MICROPHONE
> > #define KSNODETYPE_HEADSET_SPEAKERS
> KSNODETYPE_COMMUNICATION_SPEAKER
> >
> > In Vista it is important that you get the pin categories correct
> > because it determines what and how devices show up in the audio APIs,
> > control panel, etc.
> >
> > Regards,
> > Mitch Rundle
> > Microsoft Corp.
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> > -----Original Message-----
> > From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> > [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of uwe kirst
> > Sent: Friday, January 13, 2006 9:01 AM
> > To: wdmaudiodev@xxxxxxxxxxxxx
> > Subject: [wdmaudiodev] Vista Build 5270 + friendly names for audio
> > driver wave devices
> >
> > Hello,
> >
> > I have just tried Vista again to see wether the devicename issues have
>
> > beed fixed or not.
> > It seems that the friendly names are not set automatically. All
> > devices are named:
> >
> > "Volume Control"
> >
> > If you open a Windows audio app (e.g. Wavelab) you can select the
> > audio device from a list of devices which are all called "Volume
> Control".
> > The funny thing is that you can change the name of each device if you
> > go
> > to:
> >
> > Control Panel -> Sound and Speech Recognition ->Audio Devices and
> > Sound Themes -> Audio Devices
> >
> > By double clicking on each device I'm able to set individual
> > devicenames.
> > My question is if it is possible to set the devicesnames from the
> > beginning within the driver or the .inf file.
> > The friendly names which are also set in the registry are not
> > recognized by vista.
> >
> > thanks,
> > 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/
> >
> > ******************
> >
> > 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/
> >
> >
>
> ******************
>
> 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/
>
--
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
******************
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:
