Evolution USB Devices Driver Download



Bring up drivers. USB Function driver bring-up is only required if you support USB Function mode. If you previously implemented a USB Function driver for a USB micro-B connector, describe the appropriate connectors as USB Type-C in the ACPI tables for the USB Function driver to continue working. If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. After the device-specific driver is installed, Windows 10 will select that driver instead of the standard USB audio 2.0 driver when you first connect the device.

-->

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.

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

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

Evolution Usb Devices Driver Download Windows 8

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.

Usb Device Drivers Windows 10

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
Download a driver for usb

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.

Evolution USB Devices Driver Download

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

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.

Driver development

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

Evolution Usb Devices Driver Download Windows 10

See also

Download A Driver For Usb

  1. Before connecting the VerticalMouse, go to Control Panel, Mouse:
    • On the Buttons tab, uncheck the box for Switch Primary and Secondary Buttons.
    • On the Pointer Options tab, uncheck the box for Enhance Pointer Precision and set the pointer speed slider to the middle position.
  2. Insert the plug or receiver in a USB port.
    • For wireless models, select a port away from other USB plugs or devices to avoid signal interference.
    • If pointer movement is unreliable, use an extension cable to position the receiver farther away from other USB plugs or devices.
    • Avoid using KVM switches since the VerticalMouse may not work with them.
  3. On wireless models, insert the battery and slide the On/Off switch to the green position.
  4. Adjust the pointer speed as desired with the pointer speed button behind the wheel.
  5. Evoluent Mouse Manager (driver) may optionally be installed to customize the buttons with a variety of functions, such as Copy, Paste, Enter, Double Click, etc. Download the driver here.
  1. Before connecting Evoluent VerticalMouse, go to the Applications folder to find and remove any existing Evoluent Mouse Manager and any other mouse software, except touchpad drivers, to avoid software conflict.
  2. USB wired or wireless receiver models:
    • Insert the plug or receiver in a USB port.
    • For wireless models, select a port away from other USB plugs or devices to avoid signal interference.
    • If pointer movement is unreliable, use an extension cable to position the receiver farther away from other USB plugs or devices.
    • Avoid using KVM switches since the VerticalMouse may not work with them.
  3. Mac/Bluetooth models without a receiver:
    • Go to System Preferences, Bluetooth and click Setup New Device or the + sign to add the mouse.
    • Insert the battery and slide the On/Off switch on the VerticalMouse to the green position or cycle it off and on to begin pairing.
  4. Adjust the pointer speed as desired with the pointer speed button behind the wheel.
  5. Evoluent Mouse Manager (driver) may optionally be installed to customize the buttons with a variety of functions, such as Copy, Paste, Enter, etc. Download the driver here. You may have to temporarily allow installing programs downloaded from anywhere in System Preferences, Security and Privacy.

Note regarding High Sierra (10.13) or newer Mac OS

  • The Evoluent Mac driver (known as “extension”) may be blocked in Mac OS 10.13 High Sierra or newer OS by a new system security feature known as Secure Kernel Extension Loading. Refer to this article on the Apple web site: https://developer.apple.com/library/archive/technotes/tn2459/_index.html.
  • If the mouse buttons do not perform your selected functions in the driver, or if the system shows “no VerticalMouse device attached”, go to System Preferences, Security to see if there is an option to allow the Evoluent extension. The option is only there for 20 minutes after installing the driver or restarting. If it is not there, restart the computer to reload it.
  • The extension will be listed as software from Jack Lo (the creator). If after allowing the extension it is still not working, restart the computer again. If restarting does not work, uninstall and reinstall the Evoluent software and restart the computer.
  • To determine if Secure Kernel Extension Loading is blocking the Evoluent extension, open a Terminal window to enter this command:

    kextstat | grep evoluent

  • If the Evoluent extension is allowed, the command will return a line of info. If it is blocked, the line will be blank. When it is blank, reinstall the driver and restart the computer.
  • Hold the VerticalMouse with your fingertips.
  • Put the edge of your hand on your desk.
  • Move the mouse mostly by moving your fingers, not your entire arm.
  • Tilt up the left side of a right-handed mouse to disable tracking, or tilt up the right side of a left-handed mouse.
  • Slide the mouse without moving the pointer.
  • It is very important to have your forearm in a horizontal position. The optimal arm angle may be achieved by raising your chair or using an underdesk keyboard tray to lower the mouse.
  • Position the mouse close to you to avoid extending your arm outwards.
  • Relax your shoulder.

VerticalMouse D, VerticalMouse 4

Top button – left click

Wheel button – forward

Middle button – wheel/middle click

Bottom button – right click

Upper thumb button – back

Bottom thumb button – requires driver to function

VerticalMouse C

Top button – left click

Wheel button – there is no wheel click on VMC

Middle button – wheel/middle click

Bottom button – right click

Upper thumb button – back

Bottom thumb button – requires driver to function

  • On the VerticalMouse, there are three flat buttons on the side. Evoluent makes the middle button perform the middle click, also known as wheel click, because pressing a flat button is more comfortable than pressing a wheel as is common with other mice.
  • Early computer mice had three buttons but no wheel. When the wheel was introduced, it doubled as the middle button since horizontal mice are not wide enough for three buttons and a wheel.
  • Evoluent VerticalMouse has enough height to provide three proper buttons again. If you prefer the wheel for wheel click, please download the driver to program the wheel button as wheel click.
  • When the driver is installed, some button functions are different from system default. Open Mouse Manager to check the functions.
  • The program or app you are using might be customized with different button functions than the global settings on the Buttons tab. In Mouse Manager, open Customize Buttons for Different Programs to check whether your programs has been customized.

When the driver is installed, and the Eye Comfort function is enabled with Dim Pop-Ups selected, the right click menu does not appear in some Microsoft Office programs when nothing in the document is selected. This issue may be avoided by changing the dimming method to Undim Pop-Ups.

Your system might be configured for a horizontal left-handed mouse. Go to Control Panel, Mouse, Buttons tab to uncheck Switch Primary and Secondary Buttons.

If you often unintentionally press a button, you may disable the button. Please install the driver and select the Disabled function for the button.

The desk surface may be too reflective. Test the mouse on a piece of white printer paper. If it tracks correctly on the paper, the mouse is working properly. Use a mouse pad to improve tracking.

  • Go to Control Panel, Mouse, Pointer Options to uncheck the box for Enhance Pointer Precision (this system feature actually makes the pointer jumpy).
  • Adjust the pointer speed with the pointer speed slider in Mouse, Pointer Options.
  • Press the pointer speed button behind the wheel to select a slower speed for more precise control.

Earlier models have an illuminated logo that cannot be turned off. Later models may be turned off this way:

  1. Unplug the VerticalMouse 4 when the computer is on.
  2. Press and hold the – end of the pointer speed button and plug in the USB connector. If your mouse is a later production unit, the logo will turn off. To turn on the logo again, press and hold the + end of the pointer speed button when you plug in the USB connector.
  • Slide the power switch on the bottom of the mouse to the green position.
  • Install a fresh battery with the + terminal facing out.
  • Remove the receiver and reinsert it to see if Windows makes the disconnect and reconnect sounds. Ensure that computer speakers are connected and the volume is turned on.
  • The receiver might not be paired with the VerticalMouse. Pair the receiver with the mouse according to the instructions below
  • The battery may be running low. Replace the battery if the pointer speed lights are blinking rapidly whenever the mouse is moved.
  • The mousing surface may be too reflective for the sensor. Try a non-reflective mouse pad.
  • The receiver may be suffering from signal interference due to proximity to other USB devices or cables. Use another USB port farther away from other USB devices or plugs, or use an USB extension to position the receiver even farther away.

VerticalMouse 4 Right Mac and Bluetooth models do not have receivers. They connect to Mac computers via the computers’ built-in Bluetooth function.

The lights blink rapidly when the battery is low. Replace the battery.

On VM4, VMC and VMD models:

  1. Press and hold the top thumb button.
  2. Turn on the power switch. The lights will flash on, off, and on again.
  3. Quickly insert the receiver into a USB port. The lights will flash twice when pairing is successful.
  4. Release the thumb button.

VM4 with a small pairing hole on the bottom above the signature:

  1. Slide the power switch under the mouse to the On or green position.
  2. Insert the receiver in a USB port.
  3. Download the receiver pairing utility here (for Windows only). Click Run. When it finishes downloading, click Run again to start the utility and follow its instructions.
  • Windows enables the mouse to wake the computer from sleep by moving it. The setting is in Control Panel, Device Manager, Mice and other pointing devices, Evoluent VerticalMouse, Power Management.
  • Slight vibrations to the desk may result in the mouse moving enough to unintentionally wake the computer. This issue may be prevented by disabling the wake feature in Power Management.
  • Windows always enables this feature again whenever the mouse is plugged in, when the driver is first installed, or when the driver is reinstalled. To prevent the mouse from inadvertently waking the computer, disable the feature again after plugging in the mouse or installing driver updates.
  • This task may be made more convenient by creating and running a simple file that disables the wake setting.
    1. On the desktop, right click and select New, Text Document.
    2. Double click on the file to open it. Copy and paste the following one line of text into it:

      powercfg /devicedisablewake “Evoluent VerticalMouse”

    3. Save and close the file.
    4. Rename the file extension from .txt to .bat (to see the file extension, you may have to uncheck “Hide extensions for know file types” in system folder options)
    5. To run the file, right click the file and click Run as Administrator.
    6. After it is run, VerticalMouse will not wake the computer when it is moved, until the next time it is plugged in again or the driver is updated.

The shortcut on the top row are supported by Windows. They may not work in other operating systems.

Mouse Friendly Right Handed Keyboard (R3K)

Undo – undo the last action or Ctrl Z.
Cut – cut item to clipboard or Ctrl X.
Copy – copy item to clipboard or Ctrl C.
Paste – paste item to clipboard or Ctrl V.
Web – open the default web browser.
E-Mail – open the default email program.
Comp – open my computer to see all the drives.
Prev – go back one track in the media player if there is a previous track.
Play – play or pause the media player.
Next – go back one track in the media player if there is a next track.
Volume- – reduce the sound volume.
Volume+ – increase the sound volume.
Mute – mute the sound output.
Sleep – put the computer on sleep mode.
ShutDn – shut down the computer.
Note: eject key for Mac is F12.

Essentials Compact eject key for Mac is F12Keyboard (EKB)

Undo – undo the last action or Ctrl Z.
Cut – cut item to clipboard or Ctrl X.
Copy – copy item to clipboard or Ctrl C.
Paste – paste item to clipboard or Ctrl V.
Web – open the default web browser.
E-Mail – open the default email program.
Comp – open my computer to see all the drives.
Mute – mute the sound output.
Volume- – reduce the sound volume.
Volume+ – increase the sound volume.
Sleep – put the computer on sleep mode.
Turn Off – shut down the computer.
Note: eject key for Mac is F12.

If you have any other issues or questions, please contact us. We will be happy to help you!

Email:
Phone: 650 871 1365