Whenever I try to upload a bug report using the Microsoft Beta Client I get
"An unexpected error occurred - code = 12019" in the Microsoft File Transfer
Manager. I've tried turning the firewall off but that didn't help.
Jeff
Sam, Jeff and others on the wdmaudiodev list,
I just wanted to re-iterate that we take regressions very seriously and thank those who are already helping us find them. For Windows Vista we have made the biggest changes in the audio system since Windows 3.1 (IMO) so some fallout should be expected during the development cycle of the operating system.
We would very much appreciate it if you would file bugs through the beta feedback system when you find issues with how your device and/or device driver operates in Windows Vista so we can investigate and root-cause every regression found.
While legacy drivers using established driver models like AVStream, WaveCyclic and WavePCI should continue to work in Windows Vista, there are changes in preferred driver model (WaveRT port is new for Vista), how devices are exposed and what is considered a Designed for Windows Vista audio device. The latter will impact those of you who build devices and drivers that require a Logo.
You can read about Windows audio technologies and initiatives here: http://www.microsoft.com/whdc/device/audio/default.mspx
Especially important to note is the UAA initiative: http://www.microsoft.com/whdc/device/audio/uaa.mspx
The Windows Vista Logo program requirements here (look for version .6 to come out in the next couple of weeks): http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx
Thanks in advance for your help to keep Windows Vista as backward compatible as possible.
Sincerely,
Hakon Strande PM Integrated, Internal, External, and Wireless Audio Devices MediaTech/DMD/Windows Client/Microsoft
-----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian Sent: Friday, August 12, 2005 2:36 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: Audio device selection on Longhorn
That is probably why my logoed driver for XP/2000 fails to display any wave devices in the audio properties drop down lists, and why it fails to make any QCap.dll filters in GraphEdit (but it does make KxProxy.dll filters). So, for example, my device is not listed under "capture devices" but it is listed under "wdm streaming devices".
MSFT is look at this right now using my device and my driver.
It seems to me that if a wave device was exposed under xp, it should also be exposed under Longhorn.
I should have answer in a couple of weeks (I am told by MSFT) regarding whether it is a bug on my end or a bug in Longhorn.
You can see my previous post for more information.
-----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Pages Sent: Thursday, August 11, 2005 11:32 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Audio device selection on Longhorn
We manufacture a range of multi-channel sound cards. Each channel is implemented as a WavePCI subdevice, and each subdevice is given a distinctive name (Chan.1, Chan.2, etc.). This works fine on Windows 2000, XP
and Server 2003, and our cards are logo'd for these platforms.
On Longhorn Beta 1, however, in the Sounds and Audio Devices Properties dialog, the Preferred Playback Device dropdown lists destination pins rather
than subdevices, and identifies them by pin type (rather than pin name) so that we get two entries saying "Speaker output on Auricon". On the Preferred
Recording Device dropdown list, it appears to list all source pins, again identified by pin type, so we get multiple entries for each subdevice, all called "Line In on Auricon". Needless to say this is not a good user experience.
Also our input topology is a mixer rather than a selector, allowing any or all physical inputs to be mixed into each wave input subdevice, so selecting
the Preferred Recording Device from a list of source pins doesn't make a
whole lot of sense.
Jeff Pages Innes Corporation Pty Ltd
******************
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/
