Cnfox928

Driver Provider: EuMus Design HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Headset (Sound Blaster Tactic(3D) Alpha). The drivers are layered in a stack, and the conventional way to visualize the stack is with the first driver at the top and the last driver at the bottom. The stack has one function driver and can also have filter drivers. For a discussion about function drivers and filter drivers, see What is a driver? And Device nodes and device stacks. I have been having issues with my CPU not functioning properly lately, but whenever I open the task manager or process explorer, I see the CPU usage jump from 50-80% down to a normal 5-10%. I heard this can be a virus that hides when task manager is open. I have run Avira, SUPERantiSpyware, and M.

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

This topic lists the Microsoft-provided drivers for the supported USB device classes.

• Microsoft-provided drivers for USB-IF approved device classes.
• For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
• For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).

If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.

If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.

USB Device classes

USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.

Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.

For general information about USB-IF approved device classes see the USB Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

Device setup classes

Windows categorizes devices by device setup classes, which indicate the functionality of the device.

Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.

Two important device setup classes for USB devices are as follows:

• USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.

• USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.

The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.

Microsoft-provided USB device class drivers

Related topics

VAC driver has many configuration parameters. Some of them concern the entire driver and others are cable-specific, their value can be different for each cable.

Full version of VAC can be configured to create any valid number of Virtual Cables. Trial version is restricted.

Use the VAC Control Panel to easily configure driver and cable parameters.

VAC driver parameter tree is stored in the registry under the following key:

HKLMSOFTWAREEuMus DesignVirtual Audio Cable4

Driver parameter values are stored immediately under this key, cable-specific parameter values are stored under 'Cable N' subkeys. All parameters are specified as DWORD values unless explicitly specified. If a value is absent or zero, it means a default/automaric settings unless stated explicitly. Value names are the following (literally, all spaces are meaningful, but case insensitive):

Drivers Eumus Design Software

Driver parameters

• Number of cables (1..256).
• Maximum worker threads (0..32 in 32-bit systems, 0..64 in 64-bit systems).
• Maximum worker thread priority (0..31).
• Maximum number of channels (1..32) supported by the driver, for all Virtual Cables.
• Event log level (0..9).
• Timer resolution in percents of event period (10..100).
• Number of cables to restrict KMixer thread affinity - number of cables beginning from which VAC will restrict affinity of System Audio Engine worker threads. If actual number of cables is greater or equal than this value, thread affinity will be restricted to run only on a first (number zero) CPU/core. It eliminates concurrent PortCls request processing in WavePci mode and will solve some problems like this. This parameter is ignored if PortCls engine is not used.
• Number of cables to restrict client thread affinity - number of cables beginning from which VAC will restrict thread affinity of any client process (including System Audio Engine). It may be useful to solve problems like this. This parameter is ignored if PortCls engine is not used.
• Format attribute support policy - code of globalformat attibute policy: 0 - default, 1 - process, 2 - ignore.

Cable parameters

• Maximum instances (1..100).
• Milliseconds per interrupt (1..20).
• Minimum sampling rate (1000..384000).
• Maximum sampling rate (1000..384000).
• Minimum bits per sample (8..32).
• Maximum bits per sample (8..32).
• Minimum number of channels (1..8).
• Maximum number of channels (1..32).
• Stream format limiting (0 - 'None', 1 - 'Cable range', 2 - 'Cable format').
• Volume control (0 or not present - disabled, nonzero - enabled).
• Source line types mask - a bit mask that represents cable source line set. Bit 0 (value 1) means a microphone line, bit 1 (value 2) means an analog line connector, and bit 2 (value 4) means a digital line connector. You can combine them by the addition (1+2=3, Mic and Line inputs). This source line set means which lines are exposed by the cable's topology filter. Default value is 7 (all three line types).
  Don't change this parameter unless really needed.
  Under Windows 6.x, you need to restart System Audio Service or even reboot the system after changing this parameter. Driver restart is not enough to propagate it.
• Connected source lines mask - a bit mask that represents currently connected source lines. Unlike the 'Source line types mask' parameter, this bit mask means which exposed lines are reported as 'connected' (plugged in) and must be a subset of the line types mask (all bits set in this value must be also set in the 'Source line types mask' value). Default value is 2 (only the Line Input is connected).
• Clock correction - cable clock correction ratio multiplied by 1000000000 (10E9). Default value is 1000000000 that represents 1.0 ratio. Note: VAC versions prior to 4.11 use a different multiplier format that is not accepted by later versions so a default value is loaded if an old-format multiplier is found.
• Enable channel mixing (0 - disabled, nonzero or not present - enabled).
• Use standard PortCls engine (0 or not present - disabled, nonzero - enabled). Applicable to WavePci mode only.
• Enable speaker pin type (0 or not present - disabled, nonzero - enabled).
• PortCls capture port type, PortCls render port type - PortClsport/miniport types for capture (recording) and render (playback) pins (0 - auto, 1 - WaveRT, 2 - WavePci, 3 - WaveCyclic).
• Disable cable signal level (0 or not present - cable signal level calculation/display is enabled, nonzero - disabled).
• Disable stream signal level (0 or not present - stream signal level calculation/display is enabled, nonzero - disabled).
• Restrict client thread affinity (0 or not present - disabled, nonzero - enabled).
• Restrict KMixer thread affinity (0 or not present - disabled, nonzero - enabled).
• Format attribute support policy - code of per-cableformat attibute policy: 0 - default, 1 - process, 2 - ignore.

Almost all of these parameters can be controlled by VAC Control Panel and are explained there. Some parameters that are rarely used, can be added, modified or deleted manually. For this, you can use standard Windows tools (RegEdit application, or 'reg' console command) or helper scripts provided in the 'tools' subfolder of VAC installation package. All these tools must be ran under an administrative account.

Drivers Eumus Designjet

After creating, modifying or deleted some parameters manually, you need to restart VAC driver to propagate them.

When parameter value is changed by VAC Control Panel, its value is automatically copied to the HKLMSYSTEM CurrentControlSetServicesEuMusDesignVirtualAudioCableWdmParameters key to allow driver boot-time access. If you create/change a parameter under 'Software' branch manually, you should ensure its creation/changing under 'System' branch. Otherwise, the driver will be incorrectly configured on a next boot because there is no access to the 'Software' branch at a boot time.

However you could propagate parameter change to 'System' branch by hand, it's better to simply restart the driver that propagates parameter values automatically.

Saving and restoring VAC driver configuration

You can save VAC driver configuration by simply exporting the 'Software' registry subtree (the main key with all subkeys) mentioned above, using interactive RegEdit utility or the following console command (can be issued from a non-privileged account):

reg export 'HKLMSOFTWAREEuMus DesignVirtual Audio Cable4' '%HOMEPATH%documentsvaccfg.reg'

This command exports VAC driver configuration subtree to the 'vaccfg.reg' file located in your 'My Documents' folder.

To restore VAC driver configuration, first close VAC Control Panel if it is open, and delete both 'Software' and 'System' settings subtrees, using 'delsettings' command file located in VAC installation folder (usually 'C:Program FilesVirtual Audio Cable'). Locate VAC installation folder in File Explorer, right-click 'delsettings' and select 'Run as administrator'.

Drivers Eumus Designer

Then import previously saved .reg file, using RegEdit or the following console command executed under an administrative account:

reg import '%SystemDrive%users<user>documentsvaccfg.reg'

replacing the '<user>' with actual user account name under which settings were exported.

After that, open VAC Control Panel and restart the driver to propagate boot-time parameters.

You can create as many configurations as you want, keeping them in different files.

To reset all VAC driver settings to their defaults, just delete configuration subtrees without importing any configuration.

Please be careful with registry manipulations, any mistake would cause serious system malfunction.

Please don't confuse VAC driver settings shown in VAC Control Panel with Audio Repeater application settings that can be specified in its command line.