Plus the upper edge of the audio and video class drivers is the
incomprehensible kernel streaming architecture, which you really don’t want
to re-implement an interface to unless there is some massively compelling
reason.
What benefit would there be in generating your own buggy usb iso class
driver?
Mark Roddy
On Wed, May 26, 2010 at 1:04 PM, Tim Roberts wrote:
> xxxxx@gmail.com wrote:
> > from the WDK 7600 :
> >
> > USBAudio Class System Driver
> > Microsoft recommends that hardware vendors use the USBAudio driver for
> their USB Audio devices instead of writing proprietary adapter drivers.
> >
> > What is the Microsoft? real intention ?
> >
>
> With the exception of the fine individuals who frequent this mailing
> list, it is an unfortunate fact that most driver writers write crappy
> drivers. Audio drivers are complicated, and it is very easy even for a
> senior developer to screw them up. Usbaudio.sys is the result of nearly
> 15 years of development effort by some very smart people, and it is
> folly for an individual to think he’s going to slap together a
> replacement in a few months that handles all of the corner cases properly.
>
> However, that admonition applies mostly to consumer hardware. Microsoft
> has to be worried about the hundreds of millions of personal computers
> with ordinary commodity hardware. For those people, latency is a
> medical term, not a programming term. They don’t CARE how many whiz
> bang features your driver has. All they want is for Britney Spears and
> the sound track from Avatar to come out of their speakers. Nothing else
> matters. Usbaudio.sys will do that, in a way that has been exercised on
> hundreds of millions of computers. It works. A third-party driver is
> just going to screw it up, and that results in people getting mad at
> Microsoft. “Darn Windows, it can’t even play this American Idol replay
> without crashing!”
>
> For professional equipment aimed at the true audiophile, the situation
> is a bit different. Those people are WILLING to put up with a little
> flakiness, in exchange for a minimal increase in functionality. If
> something goes wrong, they know to call YOU, not Microsoft.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>