Troubleshooting SST issues

Note: ASIO4ALL 2.15, including the betas, will deal with SST devices automatically. The following information only applies to releases up to and including 2.14!

“SST” stands for “Intel(R) Smart Sound Technology” and is integrated into many current on-board audio solutions. Unfortunately, it does not operate as seamlessly as Intel claim. Moreover, while Intel are making great hardware most of the time – except for the entire NetBurst(tm) architecture, though – their software might suck, at times.

Good news is, that in order to get ASIO4ALL working with your SST “enhanced” on-board audio, you do not have to wait for a new ASIO4ALL release (which will have a workaround for this) – you can fix this yourself for the time being.

How ASIO4ALL would have auto-configured your device:

This would not work. You get static, distortion, and it may even crash your system if you click on the wrong item.

Configure ASIO4ALL as follows:

If you uncheck the “Always Resample” – option and your project is 44.1 kHz, then may be you can witness the quality of their SST sample rate conversion.


Posted

in

, ,

by

Tags:

Comments

14 responses to “Troubleshooting SST issues”

  1. John Clement Avatar
    John Clement

    When I attempt to install ASIO4all. I get a message saying:
    Output folder: C:\Program Files (x86)\ASIO4ALL v2
    Extract: asio4all.dll… 100%
    Can’t write: C:\Program Files (x86)\ASIO4ALL v2\asio4all64.dll
    Please help.

    1. Driver still open by an audio application. Please close all applications using ASIO4ALL and then re-try!

  2. Hey I use Ableton Live 11 and I use asio 2.15 the problem is I can’t play both YouTube and Ableton at same time on my headphones for that I have to switch to mme/direct x which is time consuming.So my question is the asio4all only focus on single program rather than being a multi client asio ?

  3. mateo sposito Avatar
    mateo sposito

    hi, i used asio4all for a while. And now when I try to open it, my daw (flstudio 20) closes, it’s not a hardware problem because my pc is good enough and I already tried to reinstall it. I need a solution please.

  4. Hi,

    Firstly, thanks for such a great driver, I’m a long term user of over 15 years.

    Currently I’m wondering if there’s a fix for the Cirrus Logic CS4206B and similar cards.

    Asio4all recognises this card as having 2 separate sets of stereo outputs, however other drivers such DX primary sound driver and core audio (Mac) appears to automatically duplicates the output signal to both sets of outputs as these outputs are actually part of the built in speaker system on certain laptops and Macbooks / Macbook pros. One stereo outputs is the high frequencies speakers and the other set outputs the mid range and lower frequencies.

    Right now on these type of systems, if one want to use the built in speakers with asio4all (on a windows based system) they have to duplicate the output and send it to the second set of stereo outputs within the DAW, otherwise the sound is missing part of the frequencies.
    This ultimately means that on systems using this type of configuration, Asio4all initially doesn’t “sound as good” as other drivers on the built in speakers.

    A fairly trivial matter in the grand scheme of things I know, but something to consider.

    Kind regards

  5. My DAW (Reason 12) shows the logo, scan for plugins then, nothing. The last thing I remember is setting the latency way up, which I suspect is the reason behind my unfortunate circumstance. Now I’m locked out of the program and can’t undo this action. Tried reinstalling, but that hasn’t helped. Any ideas, anyone?

    1. If you simply uninstall ASIO4ALL and the problem still persists, ASIO4ALL is not the Reason – so to speak.

  6. Hi I have FL21 and Behringer UM2 interface. I wanted lower latency and decided to install asio4all driver. Installed it and when I restarted my PC the lights on the interface weren’t working/the interface isn’t working. I have Code 39 in Device manager on the interface. I’ve tried to install the driver as administrator but still same. I want to mention that this happend only after the installation of the driver. I have the latest version of windows 10 too. Need help please

    1. ASIO4ALL is not a hardware device driver and thus will never show up in Device Manager. Whatever driver gave you that Code 39 – it wasn’t ASIO4ALL.

      The UM2 is supposed to be USB Audio Class compliant, IIRC. Thus, it should work with the Windows in-box usbaudio.sys (ASIO4ALL then sitting on top of it).

      1. So I installed the ASIO4ALL driver and after that restarted my PC, and only then in device manager my Interface under USB-Controllers “BEHRINGER USB AUDIO 2.8.40” had yellow mark and Code 39.
        But when I uninstall the driver, restart the PC and in FLStudio switch to the default settings “FLStudio Asio” then it works but with 64ms latency.
        I have searched so much tutorials but none of them work
        Can I please get some private help cuz I cannot record anything. Btw behringer aren’t answering back so that sucks
        I got instagram – @pokerboyl
        discord – ghody#6192
        I appreciate your time

  7. Hi! I am a FL21 user and when i switch to my Asio driver, it crashes my daw. I have tried multiple different versions of this driver and the result is the same. I know many people experiencing the same Issue, So any help is welcome.

    1. That is not helpful. why show a picture of the asio settings if we cant even access it from the app crashing? why does asio just completely f*ck up my daw when my pc is more than capable of running this? people have goals and quotas and jobs why are you so g*d-d*mn unreliable???

  8. PHILIP blundell Avatar
    PHILIP blundell

    hi admin ive just downloaded 2.15 and when i change latency the blue bannd dose not move

Leave a 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.

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

  • Hardware Buffer on/off

    Hardware Buffer on/off

    Note: For WaveRT drivers, this box is labeled “Allow Pull Mode (WaveRT)” instead! 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…

    more

  • Kernel Buffers/Buffer Offset

    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…

    more