[wdmaudiodev] Re: Can I identify my audio endpoint?
- From: "Alexandra Schoepel \(Ally\)" <Alexandra@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Thu, 26 Oct 2006 15:33:13 -0700
Hi Frank,
Regarding setting a special property to help us locate our endpoint: as
far as I can tell, the sysfx example adds properties to the FX
PROPERTIES key in the registry, but not the 'standard' one, e.g.
..\MMDevices\Audio\Render\{DS GUID}\Properties\
Am I missing something, or does the example only demonstrate adding
properties for the effects? It looks to me the only way to find the
endpoint associated with an audio driver is by the device
name/description from the inf.
Thanks,
Ally
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Frank Yerrace
Sent: Wednesday, October 18, 2006 3:53 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Can I identifying my audio endpoint?
I'm sorry I misled you with my previous response. A colleague reminded
me that PKEY_Endpoint_KsComponentId is not generally available in the
endpoint property stores. Another alternative- similar in concept- is
for your device INF to indirectly populate the endpoint property stores
with your own custom properties. The SYSFX sample demonstrates this.
(Sorry I don't have a pointer to the SYSFX sample or documentation at my
fingertips. I believe it's been referenced in other messages to this
mailing list.) Then your app can search for an endpoint that has your
custom properties in its property store.
Frank Yerrace
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Alexandra
Schoepel (Ally)
Sent: Tuesday, October 17, 2006 4:12 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Can I identifying my audio endpoint?
Yes it does. Okay, very cool. Is this key defined in a standard header
or is there a section of documentation describing how the KSCOMPONENTID
is encapsulated in the PROPVARIANT so I don't bother you any more. :)
Thanks again,
Alexandra Schoepel
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Frank Yerrace
Sent: Tuesday, October 17, 2006 3:59 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Can I identifying my audio endpoint?
Does your device have its own audio driver? One alternative is to read
PKEY_Endpoint_KsComponentId from the endpoint property store. This
returns a KSCOMPONENTID structure. However, for this endpoint property
to have useful information, the audio driver must support the KS
property KSPROPERTY_GENERAL_COMPONENTID and fill it in with useful
information.
Frank Yerrace
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Alexandra
Schoepel (Ally)
Sent: Tuesday, October 17, 2006 3:27 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Can I identifying my audio endpoint?
Hi guys,
What is the most effective way to identify one's own audio endpoint when
using the IMMDeviceEnumerator? None of the published Audio Endpoint
properties seem to be uniquely tied to the device. The DirectSound GUID
(PKEY_AudioEndpoint_GUID) seems to be a floating value assigned by the
OS and in no way tied to any information in the inf file of the driver.
Additionally, help on the IMMDevice::GetId function states that the
information it represents is opaque and should not be used to obtain
information about the device. Any advice?
Thanks,
Alexandra Schoepel
Other related posts:
