Although AVStream driver code works, using UpdateDriverForPlugAndPlayDevices
does not. Installing the same driver manually via the Device Manager works OK.
Harry
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Mike Horgan
Sent: Tuesday, August 11, 2015 5:47 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Windows 10 suppor for Stream Class drivers
The driver for these (what I'll call legacy devices) was released back in
9/2013. The devices enumerate and function as system sound devices and within
number of tested daws on Windows 7/8.1.
Testing on Windows 10 Insider Preview revealed issues with WDM operation. This
was noted on builds up through 10162. The discussions on the forums indicated
that there were known WDM issues which supposedly were addressed as of build
10166 which I was never able to update to as it was so close to the actual
release. When Windows 10 finally arrived for download with my MSDN
subscription I did a clean install on a new partition for testing.
I tested four separate legacy devices with this driver with similar results.
The devices all seem to enumerate fine. Three out of the four devices wouldn't
play any system sounds via the audio control panel. The four would only play
if 16 bit format selected.
All four were severely limited in operation with commercial daws. WDM Audio
only would work in daws which allowed specific selection of KS operation.
Identical testing with newest audio interfaces based on a different AVStream
driver codebase exhibited no issues when run on Windows 10.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Vincent Burel (VB-Audio)
Sent: Tuesday, August 11, 2015 3:16 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: Windows 10 suppor for Stream Class drivers
Hello,
I don't think there is change in audio interface on WIN10, our primary test
with MME, KS or WASAPI are basically ok....
And it's even possible that the famous bug on WASAPI input in exclusive mode
could be fixed... we are still checking.
But other bug could have been created (we already got different strange bugs...
e.g. an USB output point stopped working several time in our long duration test
- 96h - obliging us to re-plug the USB device - restarting computer did not fix
it - we are investigating this problem).
The fact is this WIN 10 update can rename audio point with generic name (and
also change default device, and possibly the enumeration order) can disturb all
audio configurations for all programs and user can get the feeling that nothing
work anymore... but re-checking the entire audio configuration seems to fix the
problem in most cases.
The WIN10 audio point renaming can disturb especially the KS interface because
the higher risk to have redundant name for audio point, then selecting KS
device can become a problem for some applications...
Also, it's possible to have a difference of behavior between a WIN10 update
(where all driver are already installed) and a fresh WIN10 installation ...
will see...
But it's sure that Microsoft forgot to make a validation process there...
Regards
Vincent Burel
www.vb-audio.com<http://www.vb-audio.com>
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Mike Horgan
Envoyé : lundi 10 août 2015 20:19
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Windows 10 suppor for Stream Class drivers
Can anyone tell me whether or not Windows 10 will support stream class drivers?
I have a number of audio interfaces whose driver is a stream class minidriver
which has worked fine through Windows 8.1.
With Windows 10 these devices all have numerous WDM issues (ASIO is fine).
Direct Sound and MME doesn't seem to work at all, while for the most part KS
audio functions. Trying to play system sounds doesn't work at all, or in the
case of one device only seems to work at 16 bits.
Newer device with AVStream drivers seem to operate fine. Is there any word on
what the expectation might be for stream class, or whether support for it has
been dropped?
===============================================================
Mike Horgan
Engineering
Line 6
O: 818.575.3670
Check out AMPLIFi -
The first and only 5-speaker guitar amp with Bluetooth® music streaming and iOS
wireless control, connected directly to the world's largest community of
guitarists and tones via the cloud.
line6.com/amplifi<www.line6.com/amplifi>
