11/25/2021

Aac A.s. Plvi Driver

  • Jan 29, 2021 This report offers an overview of the market trends, drivers, and barriers with respect to the Japan Autoclaved Aerated Concrete (AAC) market. It also provides a detailed overview of the market of different regions across Hokkaido, Tohoku, Kanto, Chubu, Kinki, Chugoku, Shikoku, Kyushu.
  • Was great while it lasted. I purchased 11/2014 and don't play much golf, maybe 5 rounds a season and 3-4 times a season at driving range. While at driving range 7/15/17 the shaft splintered right where connects to club head, exactly like one of the pics in earlier review.
  • Drivers Library We know a lot about PC drivers Welcome to the PC Matic Driver Library, the internet's most complete and comprehensive source for driver information.

T e r, a n d p e r s o n n e l a s s e t i n v e n t o r y; a n d prescribes the use of the following: DA Form 647 (Personnel Register), DA Form 647–1 (Personnel Register), and DA Form 3986 (Personnel Asset Inventory). This regulation applies to t h e A c t i v e A r m y, t h e A r m y N a t i o n a l.

-->

Driver flighting in the Partner Center enables you to distribute your driver within defined Windows Insider rings, while providing automatic monitoring and evaluation. A report of your driver's performance will be generated after the completion of a flight, enabling you to evaluate its critical functionality and update scenarios. Upon a successful flight and approval from Microsoft, the driver will be distributed publicly through Windows Update.

The following video provides an overview for the driver flighting program in more detail:

Signing up for driver flighting

To sign up for driver flighting, submit a support ticket to the Partner Center. Support for the Partner Center is accessed in the upper-right corner of the browser window, as shown below:

Note

When signing up for driver flighting, make sure you are inside the Partner Center. Clicking the support button from another area of the Partner Center will connect you with a non-dashboard support group.

Within the ticket, specify the following:

  • The estimated number of existing devices that will be targeted by the driver
  • The estimated volume of promotion requests you will make per month
  • Your seller and/or publisher ID

After receiving your support ticket, it may take up to five business days for you to receive a response.

Once your account has been approved, your organization's administrators will be able to configure users for flighting by going to the Settings page and selecting Manage Users. Make sure the appropriate users have at least one of the following roles selected:

  • Shipping label owner
  • Shipping label promoter

How to promote a driver for driver flighting

After being submitted to the Partner Center, you can promote your drivers for flighting with the following steps:

  1. Once your driver has been submitted and is in the validation stage of processing, create a new shipping label and fill out the details and properties sections. See Publish a driver to Windows Update for more information.

  2. Select one or more driver promotion option to promote your driver for flighting, as described below:

Promotion OptionDescription
Automatically deliver and install the driver during Windows UpgradeMarks the driver for delivery via Dynamic Update, enabling it to be delivered to applicable machines during an operating system upgrade.
Automatically deliver and install the driver on all applicable systems.Marks the driver as a Critical Update (CU), enabling it to be automatically installed via Windows Update.
  1. Complete the additional details required for promotion for flighting:

    1. The email address of the Microsoft sponsor you are working with for the promotion
    2. The business justification for promoting the publication request
    3. The process used to validate the quality of the driver
    4. The OEMs (if any) that are affected by the driver publication
  2. Select the appropriate statements that apply to your driver. These answers will improve the speed of the evaluation process:

    Important

    Please note the following:

    • It is recommended to avoid requiring a reboot after driver installation.
    • Drivers that deploy UI and/or software during installation are not Windows 10 in S mode compliant, and cannot be flighted to this operating system.
    • A co-engineering driver is a driver being developed for an unreleased version of Windows. co-engineering drivers:
      • will only be distributed to applicable devices in the Microsoft insider program during the flighting process.
      • Will not be distributed to devices that are not a part of the Microsoft insider program after a successful flight.
      • will be terminated for flighting after 60 days. A flight bug report will be provided after the flighting process is complete.
  3. Complete the shipping label process as usual.

After promoting your driver for shipping, Microsoft will evaluate your driver for approval, and provide a driver flighting report when the evaluation is complete – typically within two weeks from the time of shipping label publication. Please note that if a previously created shipping label is reused, its publication date will not be updated.

Reasons a driver may be rejected

A driver may be rejected for several reasons. Most commonly, rejection is caused by improper driver targeting. These include:

  • Targeting previous versions of Windows while also targeting Windows 10.
  • The device class being targeted may have specific CHID targeting requirements that you failed to properly follow. Some device classes require CHID like Firmware and other classes forbid the use of CHID like Display. Be sure you have entered your information correctly.
  • Using hardware IDs that unintentionally targets other OEMs.

Related topics

-->

Starting with Windows 10, release 1703, a USB Audio 2.0 driver is shipped with Windows. It is designed to support the USB Audio 2.0 device class. The driver is a WaveRT audio port class miniport. For more information about the USB Audio 2.0 device class, see https://www.usb.org/documents?search=&type%5B0%5D=55&items_per_page=50.

Plvi

The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.

The driver will identify in device manager as 'USB Audio Class 2 Device'. This name will be overwritten with a USB Product string, if it is available.

The driver is automatically enabled when a compatible device is attached to the system. However, if a third-party driver exists on the system or Windows Update, that driver will be installed and override the class driver.

Architecture

usbaudio2.sys fits within the wider architecture of Windows USB Audio as shown.

Related USB specifications

Aac

The following USB specifications define USB Audio and are referenced in this topic.

  • USB-2 refers to the Universal Serial Bus Specification, Revision 2.0
  • ADC-2 refers to the USB Device Class Definition for Audio Devices, Release 2.0.
  • FMT-2 refers to the Audio Data Formats specification, Release 2.0.

The USB-IF is a special interest group that maintains the Official USB Specification, test specifications and tools.

Audio formats

The driver supports the formats listed below. An alternate setting which specifies another format defined in FMT-2, or an unknown format, will be ignored.

Type I formats (FMT-2 2.3.1):

  • PCM Format with 8..32 bits per sample (FMT-2 2.3.1.7.1)
  • PCM8 Format (FMT-2 2.3.1.7.2)
  • IEEE_FLOAT Format (FMT-2 2.3.1.7.3)

Type III formats (FMT-2 2.3.3 and A.2.3):

  • IEC61937_AC-3
  • IEC61937_MPEG-2_AAC_ADTS
  • IEC61937_DTS-I
  • IEC61937_DTS-II
  • IEC61937_DTS-III
  • TYPE_III_WMA

Feature descriptions

This section describes the features of the USB Audio 2.0 driver.

Audio function topology

The driver supports all entity types defined in ADC-2 3.13.

Each Terminal Entity must have a valid clock connection in compatible USB Audio 2.0 hardware. The clock path may optionally include Clock Multiplier and Clock Selector units and must end in a Clock Source Entity.

The driver supports one single clock source only. If a device implements multiple clock source entities and a clock selector, then the driver will use the clock source that is selected by default and will not modify the clock selector’s position.

A Processing Unit (ADC-2 3.13.9) with more than one input pin is not supported.

An Extension Unit (ADC-2 3.13.10) with more than one input pin is not supported.

Cyclic paths in the topology are not allowed.

Audio streaming

The driver supports the following endpoint synchronization types (USB-2 5.12.4.1):

  • Asynchronous IN and OUT
  • Synchronous IN and OUT
  • Adaptive IN and OUT

For the asynchronous OUT case the driver supports explicit feedback only. A feedback endpoint must be implemented in the respective alternate setting of the AS interface. The driver does not support implicit feedback.

There is currently limited support for devices using a shared clock for multiple endpoints.

For the Adaptive IN case the driver does not support a feedforward endpoint. If such an endpoint is present in the alternate setting, it will be ignored. The driver handles the Adaptive IN stream in the same way as an Asynchronous IN stream.

The size of isochronous packets created by the device must be within the limits specified in FMT-2.0 section 2.3.1.1. This means that the deviation of actual packet size from nominal size must not exceed +/- one audio slot (audio slot = channel count samples).

Descriptors

An audio function must implement exactly one AudioControl Interface Descriptor (ADC-2 4.7) and one or more AudioStreaming Interface Descriptors (ADC-2 4.9). A function with an audio control interface but no streaming interface is not supported.

The driver supports all descriptor types defined in ADC-2, section 4. The following subsections provide comments on some specific descriptor types.

Class-Specific AS interface descriptor

For details on this specification, refer to ADC-2 4.9.2.

An AS interface descriptor must start with alternate setting zero with no endpoint (no bandwidth consumption) and further alternate settings must be specified in ascending order in compatible USB Audio 2.0 hardware.

An alternate setting with a format that is not supported by the driver will be ignored.

Each non-zero alternate setting must specify an isochronous data endpoint, and optionally a feedback endpoint. A non-zero alternate setting without any endpoint is not supported.

The bTerminalLink field must refer to a Terminal Entity in the topology and its value must be identical in all alternate settings of an AS interface.

The bFormatType field in the AS interface descriptor must be identical to bFormatType specified in the Format Type Descriptor (FMT-2 2.3.1.6).

For Type I formats, exactly one bit must be set to one in the bmFormats field of the AS interface descriptor. Otherwise, the format will be ignored by the driver.

To save bus bandwidth, one AS interface can implement multiple alternate settings with the same format (in terms of bNrChannels and AS Format Type Descriptor) but different wMaxPacketSize values in the isochronous data endpoint descriptor. For a given sample rate, the driver selects the alternate setting with the smallest wMaxPacketSize that can fulfill the data rate requirements.

Type I format type descriptor

For details on this specification, refer to FMT-2 2.3.1.6.

The following restrictions apply:

FormatSubslot sizeBit resolution
Type I PCM format:1 <= bSubslotSize <= 48 <= bBitResolution <= 32
Type I PCM8 format:bSubslotSize 1bBitResolution 8
Type I IEEE_FLOAT format:bSubslotSize 4bBitResolution 32
Type III IEC61937 formats:bSubslotSize 2bBitResolution 16

Class-Specific AS isochronous audio data endpoint descriptor

For details on this specification, refer to ADC-2 4.10.1.2.

The MaxPacketsOnly flag in the bmAttributes field is not supported and will be ignored.

The fields bmControls, bLockDelayUnits and wLockDelay will be ignored.

Class requests and interrupt data messages

The driver supports a subset of the control requests defined in ADC-2, section 5.2, and supports interrupt data messages (ADC-2 6.1) for some controls. The following table shows the subset that is implemented in the driver.

EntityControlGET CURSET CURGET RANGEINTERRUPT
Clock SourceSampling Frequency Controlxxx
Clock SelectorClock Selector Controlx
Clock MultiplierNumerator Controlx
Denominator Controlx
TerminalConnector Controlxx
Mixer UnitMixer Controlxxx
Selector UnitSelector Controlxx
Feature UnitMute Controlxxx
Volume Controlxxxx
Automatic Gain Controlxx
Effect Unit
Processing Unit
Extension Unit

Additional information on the controls and requests is available in the following subsections.

Clock source entity

For details on this specification, refer to ADC-2 5.2.5.1.

At a minimum, a Clock Source Entity must implement Sampling Frequency Control GET RANGE and GET CUR requests (ADC-2 5.2.5.1.1) in compatible USB Audio 2.0 hardware.

The Sampling Frequency Control GET RANGE request returns a list of subranges (ADC-2 5.2.1). Each subrange describes a discrete frequency, or a frequency range. A discrete sampling frequency must be expressed by setting MIN and MAX fields to the respective frequency and RES to zero. Individual subranges must not overlap. If a subrange overlaps a previous one, it will be ignored by the driver.

A Clock Source Entity which implements one single fixed frequency only does not need to implement Sampling Frequency Control SET CUR. It implements GET CUR which returns the fixed frequency, and it implements GET RANGE which reports one single discrete frequency.

Clock selector entity

For details on this specification, refer to ADC-2 5.2.5.2

The USB Audio 2.0 driver does not support clock selection. The driver uses the Clock Source Entity which is selected by default and never issues a Clock Selector Control SET CUR request. The Clock Selector Control GET CUR request (ADC-2 5.2.5.2.1) must be implemented in compatible USB Audio 2.0 hardware.

Feature unit

For details on this specification, refer to ADC-2 5.2.5.7.

The driver supports one single volume range only. If the Volume Control GET RANGE request returns more than one range, then subsequent ranges will be ignored.

The volume interval expressed by the MIN and MAX fields should be an integer multiple of the step size specified in the RES field.

If a feature unit implements single channel controls as well as a master control for Mute or Volume, then the driver uses the single channel controls and ignores the master control.

Additional Information for OEM and IHVs

OEMs and IHVs should test their existing and new devices against the supplied in-box driver.

There is not any specific partner customization that is associated with the in-box USB Audio 2.0 driver.

This INF file entry (provided in a update to Windows Release 1703), is used to identify that the in-box driver is a generic device driver.

The in-box driver registers for the following compatible IDs with usbaudio2.inf.

See the USB audio 2.0 specification for subclass types.

USB Audio 2.0 Devices with MIDI (subclass 0x03 above) will enumerate the MIDI function as a separate multi-function device with usbaudio.sys (USB Audio 1.0 driver) loaded.

The USB Audio 1.0 class driver registers this compatible ID with wdma_usb.inf.

And has these exclusions:

An arbitrary number of channels (greater than eight) are not supported in shared mode due to a limitation of the Windows audio stack.

IHV USB Audio 2.0 drivers and updates

For IHV provided third party driver USB Audio 2.0 drivers, those drivers will continue to be preferred for their devices over our in-box driver unless they update their driver to explicitly override this behavior and use the in-box driver.

Audio Jack Registry Descriptions

Starting in Windows 10 release 1703, IHVs that create USB Audio Class 2.0 devices having one or more jacks have the capability to describe these jacks to the in-box Audio Class 2.0 driver. The in-box driver uses the supplied jack information when handling the KSPROPERTY_JACK_DESCRIPTION for this device.

Jack information is stored in the registry in the device instance key (HW key).

The following describes the audio jack information settings in the registry:

<tid> = terminal ID (As defined in the descriptor)

<n> = Jack number (1 ~ n).

Convention for <tid> and <n> is:

  • Base 10 (8, 9, 10 rather than 8, 9, a)
  • No leading zeros
  • n is 1-based (first jack is jack 1 rather than jack 0)

For example:

T1_NrJacks, T1_J2_ChannelMapping, T1_J2_ConnectorType

For additional audio jack information, see KSJACK_DESCRIPTION structure.

These registry values can be set in various ways:

  • By using custom INFs which wrap the in-box INF for the purpose to set these values.

  • Directly by the h/w device via a Microsoft OS Descriptors for USB devices (see example below). For more information about creating these descriptors, see Microsoft OS Descriptors for USB Devices.

Microsoft OS Descriptors for USB Example

The following Microsoft OS Descriptors for USB example contains the channel mapping and color for one jack. The example is for a non-composite device with single feature descriptor.

The IHV vendor should extend it to contain any other information for the jack description.

Troubleshooting

If the driver does not start, the system event log should be checked. The driver logs events which indicate the reason for the failure. Similarly, audio logs can be manually collected following the steps described in this blog entry. If the failure may indicate a driver problem, please report it using the Feedback Hub described below, and include the logs.

For information on how to read logs for the USB Audio 2.0 class driver using supplemental TMF files, see this blog entry. For general information on working with TMF files, see Displaying a Trace Log with a TMF File.

For information on 'Audio services not responding' error and USB audio device does not work in Windows 10 version 1703 see, USB Audio Not Playing

Aac A.s. Plvi Driver Updater

Feedback Hub

If you run into a problem with this driver, collect audio logs and then follow steps outlined in this blog entry to bring it to our attention via the Feedback Hub.

Aac A.s. Plvi Driver Course

Driver development

This USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft.

See also