[wdmaudiodev] Re: Associating a waveIn/waveOut device with an IMMDevice

  • From: Mike Preston <mike@xxxxxxxxxxxxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Wed, 21 Feb 2007 10:08:47 -0800

Thanks, Larry. I'll give it a try. So is there something specific about what might make it fail? I know that "unavailable" endpoints don't show up in the waveOut/waveIn enumeration. Does it have something to do with the endpoint's state?


Thanks,
Mike

Larry Osterman wrote:
It's not pretty :(.

Essentially you need to send the DRV_QUERYFUNCTIONINSTANCEID and
DRV_QUERYFUNCTIONINSTANCEIDSIZE to waveOutMessage on each wave
device.  That will return the endpoint name that each wave device is
associated with.  You can call IMMDeviceEnumerator::GetDevice to
retrieve an IMMDevice for that endpoint.

Note that the DRV_QUERYFUNCTIONINSTANCEID API WILL fail in some
cases, so don't assume it works.


-----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Mike Preston Sent: Wednesday, February 21, 2007 9:21 AM To:
wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Associating a
waveIn/waveOut device with an IMMDevice

I saw some chatter about this on the list a while back, but it seemed
to center around access a custom interface.  Does anyone have any
info on associating a waveOut/waveIn device with an IMMDevice in
general?  I can enumerate through the list of MM Devices using the
Core Audio APIs, which show all the Render/Capture endpoints, and I
can enumerate through all the waveOut/waveIn devices, which only show
the devices that are available, and which always put the default
device first.  How can I take an IMMDevice and determine what index
to use with the waveOut/waveIn functions to access the same endpoint?


Thanks, Mike -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Mike Preston          | Home/Office: (360)756-1655 | | E-mail:
mike@xxxxxxxxxxxxxxxxxxx | Cell: (360)303-9331 | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| |
The man who follows the crowd will usually get no         | |
further than the crowd.  The man who walks alone is       | |
likely to find himself in places no one has ever been.    | |
-- Alan Ashley-Pitt | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ******************

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/




--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|            Mike Preston          | Home/Office: (360)756-1655 |
| E-mail: mike@xxxxxxxxxxxxxxxxxxx |        Cell: (360)303-9331 |
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
|     The man who follows the crowd will usually get no         |
|     further than the crowd.  The man who walks alone is       |
|     likely to find himself in places no one has ever been.    |
|                     -- Alan Ashley-Pitt                       |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
******************

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: