[wdmaudiodev] Re: Mixer compatibility under Vista
- From: "Jeff Pages" <jeff@xxxxxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 10:13:30 +1000
Hi Andrew,
Our cards don't do any output cross-mixing, so we were able to provide all
the functionality needed through the WDM mixer API. On XP and earlier we
provided input cross mixing, but Vista's "endpoint" architecture precludes
that so under Vista we're just presenting one capture device (endpoint) per
physical input. I'm not sure if the loss of an input mixer will impact any
of our clients though, but I think the major concern was being able to pass
the inputs through to the outputs under program control and that can still
be done either in compatibility mode or using the new DeviceTopology API.
Jeff
----- Original Message -----
From: "Andrew Elder" <aelder@xxxxxxxxxxxxxxxx>
To: <wdmaudiodev@xxxxxxxxxxxxx>
Sent: Thursday, September 28, 2006 7:15 AM
Subject: [wdmaudiodev] Re: Mixer compatibility under Vista
Hi Jeff,
I recall from previous posts that you make audio cards that may have some
of the same issues as ours.
Do you expose your own custom mixing interface ?
- Andrew
Jeff Pages wrote:
Hi Andrew,
I'm pretty sure I read in a post earlier this year that Vista doesn't
support non-WDM mixer DLLs, even in XP-compatibility mode.
Jeff
----- Original Message ----- From: "Andrew Elder"
<aelder@xxxxxxxxxxxxxxxx>
To: <wdmaudiodev@xxxxxxxxxxxxx>
Sent: Thursday, September 28, 2006 12:46 AM
Subject: [wdmaudiodev] Mixer compatibility under Vista
[RESEND - no response]
All,
We have wave driver that doesn't show any mixer devices under Vista
RC-1, even when we do the following "compatibility" step:
"{Starting with RC1 (build 6500) you can activate the mixer shim by
checking the "Run this program in compatibility mode for: XP (Service
Pack 2)"."
This driver does not present a WDM audio interface. Instead, a DLL is
loaded by entries in Drivers32 (wave and mixer) and this communicates
via a custom interface to a kernel driver.
Our test application in this case is a simple console application that
calls mixerGetNumDevs() and mixerGetDevCaps(). Thats all. We have added
a call to GetVersionEx() to verify that the "shim" is running.
This raises some questions:
1) is compatibility mode supposed to work with DLLs, or does it expect a
WDM audio interface ?
2) anyone else had issues similar to this one ?
3) any suggestions about what to test next ?
Thanks,
Andrew
******************
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/
Other related posts:
