Another consideration is whether a particular solution can be made to work on a number of products in the Windows family. In making all of the previously mentioned decisions, the hardware vendor must weigh the value of performance enhancements against the cost of implementing them. Both decisions affect how the devices on the audio adapter appear to applications. The data ranges specify the data formats that the devices can support in their wave and MIDI streams. The topology is a logical map of the data paths and control nodes in the adapter circuitry. Two additional decisions involve how to present the adapter topology and pin data ranges to audio applications. For more information, see Introducing the WaveRT Port Driver. When designing a custom adapter driver that uses PortCls, the devices on the audio adapter are made available to applications using WaveRT. For more information about AVStream, see AVStream Overview. For more information about PortCls, see Introduction to Port Class. PortCls is the correct choice for most audio adapters. Both PortCls and AVStream are part of the Windows operating system. However, if a vendor-supplied custom audio driver is necessary, the vendor must choose whether the driver should be designed to work in conjunction with the PortCls system driver (Portcls.sys) or the AVStream class system driver (Ks.sys). The vendor does not need to provide a custom driver for a UAA-compatible audio device.
Windows contains operating-system support for PCI, USB, and IEEE 1394 devices that conform to the Microsoft Universal Audio Architecture (UAA) guidelines. The first decision is whether to design an audio device that requires a vendor-supplied custom driver. Hardware vendors should make several design decisions before beginning development of a Windows-based audio hardware device. Windows Driver Model (WDM) audio drivers make use of the kernel streaming (KS) components, which operate in kernel mode and are part of the operating system.
0 kommentar(er)
