Matthew, I'll get you the code. Give me a day or two to get it in a form that's intelligible to a 3rd party. It's not exactly a driver issue, but it appears to be an audio subsystem issue. I'll admit that a good part of it is my being sloppy about ignoring documented parameters that become more important in Windows 7. Maybe it's just me complaining about having to rewrite my code.
Matthew van Eerde wrote:
> Some code that works perfectly for me on Vista crashes with Windows 7I'd be very interested in looking at such code, if you're comfortable sharing it (either with the list or to me directly)*From:* wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Mark Walker*Sent:* Friday, February 05, 2010 8:14 AM *To:* wdmaudiodev@xxxxxxxxxxxxx *Subject:* [wdmaudiodev] Re: IKsControlI need at least XP and above. Vista+ is much better for audio drivers in general I've found, at least in a design sense. However, 65% of the desktops still use XP, so it's still important. My observation is also that some of these Vista+ interfaces behave differently on Windows 7 than in Vista. Some code that works perfectly for me on Vista crashes with Windows 7, so it looks like some of this new stuff still needs to be worked out at MS.On 2/4/2010 8:53 AM, Matthew van Eerde wrote:The non-deprecated Vista-and-further way to get an IKsControl is to call IMMDevice::Activate(...) on an adapter IMMDevice. Sample here:Using the IKsControl Interface to Access Audio Propertieshttp://msdn.microsoft.com/en-us/library/dd316787(VS.85).aspx <http://msdn.microsoft.com/en-us/library/dd316787%28VS.85%29.aspx>What OS are you running on?
****************** 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/
