User manual ASIO4ALL DRIVER FOR WDM AUDIO VERSION 2

[. . . ] Generally, you would always enter the audio configuration menu and select ASIO -> ASIO4ALL v2. Please consult the manual of your audio software for further assistance, if necessary!Sometimes, the audio software indeed would not provide an ASIO control panel option. For configuring ASIO4ALL with these applications anyway, you can launch the control panel by clicking on the ASIO4ALL status icon in the System Tray area . [. . . ] Note: If devices are not accurately synced, their audio streams are likely to drift apart over time!Latency Compensation Since ASIO4ALL does not have sufficient knowledge of the underlying hardware/driver architecture, it can only guess the actual latencies involved. With these sliders you can compensate for the latencies unknown to ASIO4ALL such that recordings in your sequencer Software are properly aligned with the rest. Note: In multi-device-setups the largest respective value of all devices will be used. Therefore, if different devices have different inherent latencies, audio placement will not be accurate for some devices! 6. Hardware Buffer on/off Note: For WaveRT drivers (Vista), this box is labeled "Allow Pull Mode (WaveRT)" instead!"Allow (WaveRT)" Enables the hardware buffer for the highlighted device. This only works for so called "WavePCI" miniports, as other types of WDM drivers do not usually allow direct access to the hardware buffer. Adjustment for best hardware buffer performance involves the "ASIO Buffer Size" slider and the "Buffer Offset" slider (see below). The biggest advantage of using the hardware buffer is that this method uses a lot less CPU. In multi-device-setups, it is possible to mix Hardware-buffered devices with devices that are not. If hardware buffering is not supported by a particular audio device, there will be an additional latency of a couple hundred milliseconds, which is clearly audible. "Allow Pull Mode (WaveRT)" There are two basic access methods for a WaveRT device, "pull-mode" (also called "event-mode") and "push-mode" (also called "polling mode"). "push-mode" is thought to be supported by all WaveRT drivers and (Vista) OS platforms, whereas "pull-mode" wasn't even officially documented by Microsoft until almost one year after Vista went RTM. As a consequence, "pull-mode" is still broken in a number of instances. If this box is left unchecked, ASIO4ALL will never use "pull-mode", otherwise it will use it whenever possible. If it works, "pull-mode" provides tighter timing and is generally thought to be technically better than "push-mode". Note: The old ASIO4ALL 2. 8 behavior for this option was as if checked!Kernel Buffers/Buffer Offset If hardware buffering is disabled, this control lets you add up to two more buffers to be queued for audio output. Each additional buffer increases the output latency of the device by the time it takes to play one buffer. Therefore, the initial setting of "2" should only be changed on less powerful machines, where reasonably small ASIO buffer sizes cannot be achieved with the default setting. If hardware buffering is enabled, this control determines the amount of clearance (in ms) between where ASIO4ALL will insert data into/read data from the hardware buffer, and the position where ASIO4ALL currently thinks the hardware read/write position is. [. . . ] This further allows having ASIO4ALL run in educational/computer lab type environments without "user666" being able to f**** things up for any user on the same machine, with the exception of "user666" him/her/itself. · The latencies displayed in e. g. Cubase SX 3 do not match the values that would result from the ASIO buffer size. ASIO4ALL supports the latency compensation features of ASIO hosts that perform latency compensation. This support is still a bit under development and will be improved as time passes. [. . . ]