SMSL DO100 Pro Advertises DSD512 and 384 kHz — But No ASIO Driver Exists

[mkammer]

I’m posting this to document a serious issue with the SMSL DO100 Pro and to warn Windows/JRiver users who rely on ASIO for high‑rate PCM and Native DSD.

I recently upgraded from an older Topping DAC — a less expensive model — which included a proper Thesycon/XMOS ASIO driver. JRiver recognized it immediately, Native DSD worked, and PCM rates up to 384 kHz were accessible without any problems. Everything functioned exactly as advertised.

The SMSL DO100 Pro, despite being marketed as a more advanced DAC with DSD512 and high‑rate PCM support, does not include an ASIO driver at all. SMSL quietly removed ASIO support from their entire product line, yet they continue to advertise full DSD and high‑rate PCM capability on Windows. Without ASIO, JRiver cannot access anything beyond 192 kHz PCM or DSD128 (DoP). Native DSD is completely unavailable.

In short:My older, cheaper Topping DAC delivered the advertised functionality.My newer, more expensive SMSL does not.

This is not a minor omission — it’s a critical missing component that prevents the device from performing to its published specifications. SMSL’s marketing claims are misleading for Windows users, and the lack of disclosure is unacceptable.

To gauge community sentiment, I’m including a poll:

Poll: Should SMSL restore ASIO driver support for their Windows DACs?​

• Yes — SMSL should provide ASIO drivers for all XMOS‑based DACs
• Yes — at least for models advertised with DSD512 / 384 kHz PCM
• No — WASAPI is enough for my needs
• No — I don’t use Windows

 

[Ruediger]

This package is listed for many DACs at SMSL, incl. yours.

https://www.smsl-audio.com/upload/portal/undefined/SMSLUSBAudioDriver.zip

I can't speak to the function you seek or to JRiver (foobar user here), but you did try that already?

 

[mkammer]

This package is listed for many DACs at SMSL, incl. yours.

https://www.smsl-audio.com/upload/portal/undefined/SMSLUSBAudioDriver.zip

I can't speak to the function you seek or to JRiver (foobar user here), but you did try that already?

I did try ASIO4ALL initially — it worked perfectly with my Topping DACs. Unfortunately, ASIO4ALL doesn’t work with the SMSL DO100 Pro because it isn’t a true ASIO driver. It’s only a WDM wrapper, and Windows doesn’t expose the DAC’s high‑rate PCM or Native DSD USB endpoints through WDM. My older, cheaper Topping DAC included a proper Thesycon/XMOS ASIO driver that accessed those endpoints, but the newer and more expensive SMSL provides no such driver.

With the SMSL, ASIO4ALL never appears in JRiver’s ASIO device list at all, while it showed up and functioned correctly with the Topping units. The default SMSL Windows driver only supports WASAPI, which is fine for basic PCM playback, but JRiver cannot play my SACD ISO files at full resolution — they’re limited to reduced‑rate DoP — whereas the Topping DACs handled them properly via ASIO.

My core issue is that SMSL advertises ASIO‑dependent features (DSD512, 384 kHz PCM) but does not provide the ASIO driver required to access them on Windows.

 

[Ruediger]

I currently have no USB to the DAC of that PC, but this driver installed.

It shows up as "USB DAC Asio" in foobar and presents the little tray app.

That's with the DO400. But the driver package is the same.

 

[mkammer]

I currently have no USB to the DAC of that PC, but this driver installed.

It shows up as "USB DAC Asio" in foobar and presents the little tray app.

That's with the DO400. But the driver package is the same.

Thanks for checking that driver package. The DO400 does seem to load an ASIO device from SMSL’s ZIP, but unfortunately the DO100 Pro doesn’t expose the same USB endpoints, so the driver never binds to it. That’s the core of the problem: SMSL’s driver distribution isn’t consistent across models. Some units (like the DO400) include the proper Thesycon/XMOS ASIO support, while others—like the DO100 Pro—don’t provide any ASIO-capable driver at all, despite advertising features that require it. So the driver installs, but the DO100 Pro simply has nothing for it to attach to. When I install the installation package, my SMSL DO 100 does not expose the ASIO driver. (I am used to watching for it, as my Topping unit did). NOTE: I did cleanly remove the prior ASIO4ALL driver. I am aware that it interferes.

Did you install the ASIO separately, or was it part of the DO400 install package (just verifying)

 

[Ruediger]

I don't use the DAC that way (USB from streamer). But had it connected, checked the Win audio device, installed the driver, checked the devices in foobar.

Saw the second asio device there (first is my ADC) and it all looked like expected. But did no test with DSD or alike.

I read there was some confusion with the SMSL downloads and new site structure. But when I check back today, I see that same package for almost all DACs (same URL).

Anyway, there must be some def. info about which DAC has asio support and which hasn't. Or it's a driver problem.

 

[mkammer]

Thanks for the follow‑up — your experience actually helps clarify what’s happening. It looks like you may still have one of the older SMSL driver packages that included the full Thesycon/XMOS ASIO stack. Those earlier ZIPs contained the xmosusbaudio.inf file and the ASIO DLL, which is why Foobar shows the second ASIO device for your DO400.

The current SMSL downloads are different. They’re smaller, missing the ASIO components, and only include the generic UAC2 driver. That’s why newer units like the DO100 Pro no longer expose an ASIO device in Foobar or JRiver — the ASIO driver simply isn’t in the package anymore.

If you still have that older driver bundle, it would definitely be worth keeping a backup of it. It may be one of the last versions SMSL published with full ASIO support. And if you’re able to share the version number, ZIP contents, or even the driver package itself, that could help determine exactly which models had proper ASIO support before SMSL changed their downloads.

Also, SMSL’s site has become harder to navigate since the redesign. Apos support sent me this direct contact link, which might be useful if you want to ask SMSL about the driver changes:

https://www.smsl-audio.com/portal/about/contact.html

Your experience is valuable here — it shows the ASIO driver did exist and did work, but SMSL’s current downloads no longer include it.

 

[Ruediger]

I actually did the steps described above last week. The driver package is also a week old. I grabbed it from the support -> driver page of their english section.

But! I can unpack and check it tomorrow, no problem.

 

[mkammer]

If your DO 400 works on the supplied drivers (that appear to be the same for all devices now), I will go to my Windows and do a complete manual rip-out of all available ASIO drivers in the registry. I understand that the DO 100 works fine on Linux with JRiver. I have a JRiver License for both Windows and Linux. That will really not tell me much, however, as I already see 384 come up on Windows. It is just that I am not seeing ASIO drivers for JRiver 36; that is the issue.

If I did not have an extensive SACD ISO collection, I would not mind, but being to limit the data rate is Irritating (Especially since the failed Topping DAC played them at full resolution on a DAC that cost half as much)

 

[Ruediger]

I took a look at the driver package, unpacked it - it's just an msi in there.

Connected USB to my production PC (two other ASIO devices there), looked into foobar, got the asio device, can configure it's channels, played something.. this works. Looked into device manager to see what handles it. It's some oem6.inf, nothing hints at ASIO specifically there. The app shows ASIO active (pcm mode) when I play from foobar.

So I ran the VB ASIO tester. It sweeps & tests successful.
The ASIO Signal Generator also tests successful up to 768khz.
Seems to be all there.

But I can't speak to JRiver. I never used it. Does it make sense to install without purchase, does it give the functionality?

 

[Ruediger]

Just out of curiosity, installed JRiver with test period. The "USB DAC (ASIO)" shows up like my other ASIO devices. DoP disabled.

Played some DSD512 .dsf files - initially I get PCM. Setting bitstreaming to on for all DSD formats changes that to DSD512 received by the SMSL.

So the driver package currently listed by SMSL is what it was, all there.

I'd say you have to dig into the driver topic. Something is missing/not showing up properly at your system. If you need recommendations for tools to do so, let me know.

 

[mkammer]

Thanks again for running those tests — the screenshots and JRiver trial results are genuinely helpful. What you’re seeing on your system is consistent with what SMSL used to distribute: some of the older MSI driver packages included a full ASIO component inside the installer, even though Device Manager didn’t explicitly show anything labeled “ASIO.” In those earlier releases, the ASIO DLL and registration entries were bundled inside the MSI and silently registered during setup.

The current driver package for the DO100 Pro, however, behaves differently. After a full clean reinstall (including removal of JRiver, removal of the SMSL driver, and a complete registry purge of ASIO/XMOS/Topping entries), the DO100 Pro package does not register any ASIO endpoint at all. JRiver, Foobar, and ASIO‑capable test tools all confirm the same result: only WASAPI devices appear, and no ASIO device is created.

So your system is behaving correctly for the driver version you have — but the DO100 Pro package simply doesn’t contain the same ASIO components anymore. That’s why your ASIO tests succeed while mine (and others) show no ASIO device at all.

If you still have that older driver package, it would be extremely helpful to know the version number or MSI contents — and if you’re comfortable sharing it, even better. It may help identify exactly when SMSL stopped including the ASIO driver in their downloads.

Thanks again for checking — your results help narrow down the difference between the older and newer SMSL driver packages.

 

[mkammer]

For reference, my previous DAC was a Topping model that used the standard Thesycon/XMOS driver package, and JRiver detected its ASIO endpoint immediately. ASIO playback worked perfectly there — PCM and DSD — with no special configuration needed. So JRiver’s ASIO behavior is known‑good on my system, and ASIO support has functioned correctly with other DACs.

 

[Ruediger]

The driver package on the SMSL site is the same for the DO100 Pro, DO400, and most other models. I use the same for a D-6S too.

They currently offer the build from 2025-12-02. If you get it there you have the exact same MSI.

Many possible reasons for the result on your PC not being the same as on mine. First the model of course, does it actually support these things (pretty sure it does). Next firmware, could be outdated, buggy and/or mismatching (!) the driver. Don't expect too much from these brands. Flash the newest firmware, use the newest driver. And the biggest area is the PC itself where a plethora of things can lead to a borked device install.

I think you will work it out and there is actually nothing missing.

 

[mkammer]

Thanks for the thoughts — I appreciate the perspective. I did want to share what I’m seeing on my end, because the behavior is very consistent and points to something model‑specific rather than a PC or driver‑install issue.

Even though SMSL distributes the same MSI for multiple DACs, the installer contains several driver profiles, and the DAC’s USB firmware determines which one is activated. On the DO400 (and some older SMSL models), the XMOS ASIO endpoint is exposed, and the Thesycon ASIO driver installs normally. On the DO100 Pro, that endpoint simply isn’t present. As a result, the ASIO driver never installs, the XMOS control panel doesn’t appear, JRiver and foobar never see an ASIO device, and Windows only loads the basic UAC2 driver.

This matches the USB descriptor behavior and is repeatable across software: no ASIO interface, no ASIO registry entries, no Thesycon components, and no ASIO visibility in any player. So while the MSI is the same, the DO100 Pro doesn’t seem to expose the ASIO‑capable interface that the driver expects.

If SMSL releases updated firmware that adds the ASIO endpoint, I’ll happily test it — but based on current behavior, the DO100 Pro appears to be a UAC2‑only device.

 

[Vincent Kars]

JRiver recognized it immediately, Native DSD worked, and PCM rates up to 384 kHz were accessible without any problems.

Wouldn't be surprised if you get the same results using WASAPI in Exclusive mode.

 

[mkammer]

Glad to hear JRiver recognized your DO100 Pro and that Native DSD and high‑rate PCM are working — that matches what I’m seeing as well. What I’m trying to confirm is whether anyone has actually been able to use ASIO with the DO100 Pro specifically.

On my system, the Thesycon/XMOS ASIO driver is installed globally, but the DO100 Pro never exposes an ASIO‑capable USB interface, so JRiver and foobar don’t show any ASIO device for it. Other SMSL models (like the DO400 and D‑6S) do expose that interface and ASIO works normally.

So I’m curious — were you able to select an ASIO device for the DO100 Pro in JRiver or foobar, or were you using WASAPI/Kernel Streaming?

Just trying to determine whether ASIO is actually supported on this model or if it’s UAC2‑only by design.

 

[Ruediger]

I see what you are suspecting. If the device only presents itself as a Win audio device, then there will be no ASIO driver taken from the package during install.

Do you get the tray app upon install and does it show you "(PCM mode)" no matter what you do? Or don't you get the app installed either?

Overall it makes no sense to me though. The DO100 Pro is a middleclass product from them with 2 x 9039Q2M, XMOS... I could understand with some very cheap DAC that lacks a component. But that's not the case here as far as I can see.

Did you ask SMSL about this? OK, good luck..

Don't want to post you AI slop, but a simple query about this says a) DO100 Pro supports ASIO and b) previous driver/device trouble is the most probable cause of it not installing properly. So I would unplug the DAC and clean up the system.

 

[mkammer]

Thanks for the replies — and just for context, I spent about 20 years as a software/hardware test engineer at Microsoft and elsewhere, so I’m very comfortable digging into Windows drivers and registry behavior.

After going through everything, here’s what I’ve confirmed:

The SMSL DO100 Pro simply doesn’t expose an ASIO endpoint. Even though the installer package includes the generic XMOS/Thesycon ASIO driver, the DAC only presents itself to Windows as a standard UAC2 audio device. When a device doesn’t advertise an ASIO‑capable interface, the ASIO portion of the installer never activates, and the tray app never appears. Cleaning the registry or reinstalling won’t change that because the hardware isn’t offering the ASIO interface in the first place.

The good news is that ASIO isn’t needed for this DAC.Once I disabled JRiver’s DSD output mode and set PCM sample rates manually, the DO100 Pro immediately accepted high‑rate PCM over WASAPI (Event Mode) — including 384 kHz for PCM sources and 352.8 kHz for DSD64 → PCM conversion. So the DAC is performing exactly as it should. (Thanks for that suggestion)

Conclusion: ASIO isn’t available on the DO100 Pro, but it’s also not required. WASAPI handles everything this DAC is designed to do, including high bit rates. At this point, I’m happy to forget about ASIO entirely and just enjoy the DAC with the current setup.

Thank you so much for your continued feedback on this.

 

[Ruediger]

I'll beat you on those job years. And I would not stop there and get to the bottom of it. But that's subjective.

If you have a solution now that is also good.

Question: is what JRiver does now in wasapi mode beyond what foobar could achieve with that DAC?