Fosi Audio DS2 Portable DAC & Amp Review

[HalSF]

There are several, most, if not all of them are with Windows. My specific issue is that it cuts out randomly.

Thanks. I’m using Apple products so this tracks.

 

[vornez]

I archived the "Bravo" driver officially provided by Fosi's official site as it might be taken down any day. >> Driver link <<

 

[pioterd]

My specific issue is that it cuts out randomly.

Only with default cable or with other cables as well? Was that issue from the very beginning of using it or after some time?

 

[PristineSound]

A

Only with default cable or with other cables as well? Was that issue from the very beginning of using it or after some time?

always existed any any cable.

The issue does not exist with non Intel and Windows computer.

No issues with AMD/windows not android.

I believe there is either an hardware issue with the USB chipset for a specific series of Intel on Window.

 

[pioterd]

but I think it may now be solved by using Sound Keeper v1.3.5

I use DS2 on windows 11 pro. I installed both:

- Bravo audio driver (Savi Audio driver for DS2); DS2 works as well without it but I installed it
- Sound Keeper 1.3.5 - it solves "issue" with ramp-up fade-in volume; there are no any clicks/pops/crackling, it works as it should IMO

 

[PristineSound]

Final update on Fosi DS2 playback in Windows 11.
Now finally everything is working perfectly fine, 32bit/384khz without any dropouts, random fade-ins in the middle of the game or song, clicking or noise or any other problems.

TL;DR: ASMedia SATA3 driver wasn't installed, 30k ACPI.sys DPC calls in 30 seconds. Installed the driver - no dropouts on any settings.

Didn't you noticed this in the device drivers ahead of time?

 

[PristineSound]

Final update on Fosi DS2 playback in Windows 11.
Now finally everything is working perfectly fine, 32bit/384khz without any dropouts, random fade-ins in the middle of the game or song, clicking or noise or any other problems.

TL;DR: ASMedia SATA3 driver wasn't installed, 30k ACPI.sys DPC calls in 30 seconds. Installed the driver - no dropouts on any settings.

Since my last post I've tried many different configuration changes on my PC: disabled USB host controllers, reinstalled Bravo-HD drivers, disabled Ethernet/Bluetooth/Wi-Fi in BIOS, deleted all unused devices with drivers in Device Manager, cleared my system, edited power plan settings (even hidden ones using PowerSettingsExplorer), debloated Win11 and sooo many more. Nothing helped me achieve uninterrupted playback on DS2.

Yesterday I decided to run LatencyMon again and inspect every tab and every piece of information this beautiful software provides. And what I found was ACPI.sys was generating ~30k DPC calls in 30 seconds. Keep in mind that all of this was happening on a pretty modern PC (Ryzen 7700, 32Gb CL30 6000MHz RAM, X870 motherboard, almost empty 990 Pro SSD, 80 Plus Platinum PSU plugged in a pretty good voltage stabilizer and so on) with a fresh Win11 install.

Immediately after this I've completely uninstalled chipset and GPU drivers using Revo Uninstaller + DDU + AMD Cleanup Utility under safe mode and installed newest stable drivers from AMD website. But to my surprise ACPI.sys was still making too many DPC calls... Then I decided to install/update all motherboard drivers from ASRock (my MB's manufacturer) website. I've installed every driver available except SATA driver since I don't have any SATA devices. Nothing changed, ACPI.sys was flooding my PC with DPCs...

After another 4 hours of searching, I returned to drivers and decided to install SATA drivers. The only driver available was "[Beta] ASMedia SATA3 driver ver:3.2.3.0000". Without rebooting PC after installation I immediately launched LatencyMon. A SINGLE DPC CALL FROM ACPI.SYS when I ran LatencyMon for 30 minutes...

Today I have Bravo-HD driver installed, 32bit/384khz set in Windows for DS2 and I haven't had a single dropout or click for the whole day. I still have that fade-in effect when something starts playing in my IEMs after the system was idling for some time, but I think it may now be solved by using Sound Keeper v1.3.5. At least now I have it running for 15 or so minutes while I'm writing this post and listening to music on Spotify and I had zero dropouts or fade-ins.

Sorry for these huge posts I'm writing here, but I really wanted to document my attempts to solve playback problems with DS2 on Win11. I hope that someone who has similar problems with sound playback on DS2 in Windows will find a solution to their problem in the steps that I described in my messages

Aright. I spent the majority of this morning trying to figure out the issue. Using Windows Performance Analyzer from the Windows Assessment and Deployment Kit, the issue is with how the ACPI.sys interacts with USBXHCI.sys. There are many significant latencies with this drivers.

I was able to mitigate this to a certain degree by messing with power management. But the short of it is that, the drivers and/or computer firmware needs to be fixed to address this issue. I know this as fact because when I did a clean Windows install before I installed any drivers, the DS2 and all other USB DACs works perfectly fine.

My guess is that these drivers and firmware will not be updated because population using an external USB are far and few in between.

I'm moving on.

 

[CochinealCactus]

Hi, all. I'm interested in buying one of these and am hoping an owner of the current CS43131 version can answer a quick question for me. When the unit powers up, does it return to its previous volume or to some factory default? The current product webpage says

The device features independent 60-step volume control buttons, providing you with a seamless, stepless volume adjustment experience and supporting volume memory function.

but there's no mention of the feature in the owner's manual. Thanks in advance!

 

[pioterd]

does it return to its previous volume

Current version (CS43131) remembers volume. If you for example click down 6 times (-6dB, because each click means 1dB), device keeps that volume. Even if you switch between for example windows/android it keeps previously set volume.

 

[pioterd]

Listening to DSD files and/or using exclusive mode is very far from the dominant way of consuming music on the Windows OS. Your issues are an edge case. That doesn't mean they are not real, or that they are not a concern for you, but they are really not a concern for the vast majority of people who will buy the DS2.

It is not about what is for majority of people use or etc...it is about misleading customers - against the law. If spec says it can play DSD up to 256, and it is compatible with Windows - it should be. If there are problems with playing DSD on Windows - it should be clearly given in specification. Otherwise - product to be removed from the market.

 

[Berwhale]

It is not about what is for majority of people use or etc...it is about misleading customers - against the law. If spec says it can play DSD up to 256, and it is compatible with Windows - it should be. If there are problems with playing DSD on Windows - it should be clearly given in specification. Otherwise - product to be removed from the market.

Where does the manufacturer state that the device will play DSD256 when used with the Windows operating system under all configuration and usage scenarios? Good luck arguing your case in a court of law - Caveat emptor.

 

[pioterd]

Where does the manufacturer state that the device will play DSD256 when used with the Windows operating system under all configuration and usage scenarios? Good luck arguing your case in a court of law - Caveat emptor.

Information given by manufacturer sugests it will work, that is enough to argue. If there was such information like "some configurations or usage scenarios may cause troubles...etc" it would be ok as a backup for manufacturer.

But in case of DS2 there is no problem I think - if you install Bravo Audio driver, and for foobar2000: ASIO output component and DSD components (SACD decoder and DSD processor) - everything work as it should, no issues ( I have Win11pro 25H2)