ASIO4ALL Official Home

Universal Windows ASIO Driver

Debug Build With Trace Output

The debug build completely replaces the “a4ainfo.exe” debug utility and its usage procedure. Please do not complain that the “a4ainfo.exe” download link from further down this page redirects you up here, now!

Install and run normally, until the error happens, which you would like to report. Then exit your audio application. The debug build will have created a trace log file on your Windows desktop (in plain text format). This can be used to submit problem reports per email – along with a meaningful error description, of course 📧 feedback@asio4all.com!

The debug version can generate an awful lot of trace data over time. Therefore, run only for as long as necessary!

📁 ASIO4ALL Debug Build

Posted

in

, , ,

by

Michael Tippach

Tags:

Comments

4 responses to “Debug Build With Trace Output”

  1. Angel Emiliano Contreras Sánchez Avatar
    Angel Emiliano Contreras Sánchez

    como arreglo esto

    Reply
  2. ryan Avatar
    ryan

    FL STUDIO asio error Error: pAudioCapturClient->getDevicePeriod() failed. Code:-2004287480

    Reply
    1. admin Avatar
      admin

      Not an ASIO4ALL issue.

      This is a message from the Fl Studio ASIO driver, which sits on top of WASAPI. The error is returned by WASAPI, the Windows Audio engine.

      ASIO4ALL doesn’t need that.

      Reply
  3. Radoslav Ivanov Avatar
    Radoslav Ivanov

    Sorry we couldn’t connect to audio device!
    How to fix that??

    Reply

Leave a Reply to admin Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Copyright © Michael Tippach

Imprint | Privacy

Powered by WordPress

ASIO is a trademark of Steinberg Media Technologies GmbH.  All other trademarks are the property of their respective owners, used for product identification purposes only.

  • Advanced configuration

    Advanced configuration

    Once the control panel has been switched to advanced mode, things begin to look a little more complicated. The device list is now expandable and you can enable more than one item at a time. The device list contains Devices, Device Interfaces and so called “Pins”. Devices are independent hardware units most of the time.

    more

  • Device aggregation

    Device aggregation

    Using the button next to each entry, you can now selectively enable/disable each particular item in the device list. This way, you can also create multi-device-setups (“aggregate devices”). Multi-device-setups require that all the devices involved are running from the same clock source. You can achieve this by daisy-chaining devices via S/PDIF etc. On-board devices usually

    more

  • Latency Compensation

    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

    more