I purchased mine a month ago and it seemed all right to me, but I hadn't run any tests on Windows. I did notice that my OnePlus 12R did not recognise the DAC, and needed a different cable, which I borrowed from my USB SSD. Since then it seems many users have been having issues with Windows. After reading some of the feedback here, gave it a whirl again, this time on Windows.
I tried three different systems, two running Windows 11 and one running Windows 10. Foobar 2000 was used for the tests. Control software was SM Player and control device was AK4377-based SevenHertz 71. Using HD600 for the tests, though audio quality is not the subject of the investigation.
1. Asus Zephyrus G15 running in low power mode
2. Ryzen 3600XT desktop.
3. HP laptop running in full power mode, Windows 10
The stock cable was tried, as well as the alternate cable from my SSD. Ports were 10gbps, so no issues on the power front. All tracks were 44.1KHz, as I didn't want resampling to affect the results. I will say that I got poor results on all systems, with both sets of cables.
WASAPI/exclusive: unusable. Stalls for three seconds while seeking, unpredictable pauses in the middle of songs, balance shifts between ears as the fade-in happens, and takes about 4 seconds to actually start the song. I tried multiple tweaks, setting the buffers to 5ms in the advanced menu, setting the process to realtime priority, and enabling and disabling Event mode. I think what this needs is the old KS driver, but I'm not sure if it works on W10 and 11. As it is WASAPI is unusable.
ASIO: Also unusable. First phrase of all songs are lopped off completely. Regardless of sample rate and buffer settings - you can actually see the visualisation start a second before hearing any sound, sort of like lightning. Seeking behaves the same way as exclusive, silence for two seconds and then starts with a fade in and the two channels come in at different times.
Shared mode: Very interesting in that Foobar seems to work properly with none of the above issues. SM Player, on the other hand, has a noticeable delay in starting at all. No pauses noted in either software in shared mode.
Control device did not exhibit any anomalous behaviour is shared mode or exclusive mode. Worked perfectly during seeking and played the first note of each song perfectly..
On Android One Plus tablet, using stock cable (also using Foobar 2000)
First note of songs are occasionally lopped off, just like Windows. Seeking is fine even while micro-seeking to provoke stupid behaviour regardless of cable used and resampling. No skipping or pausing observed at any samplerate. Sanity check was carried out on alternate device at 176k samplerate, again it was OK with no issues.
I have not run any tests with the iPad yet, but maybe I'll do that later.
I'm happy to blame Microsoft for the WASAPI issues because Windows is a messy codebase - but ASIO at least should work properly. Interestingly ASIO driver does not seem to recognise the device fully. The ASIO control panel shows this when device is connected:
And this when unconnected:
Fosi dropped the ball and should simply state the device is not compatible with Windows, because it isn't. It does not exhibit any traits of Windows compatibility in its current form. A friend of mine bought one on my recommendation and his is unusable because he only uses Windows. I've offered to buy it from him to offset his loss - we live in a country where customer support is poor to non-existent, and the manufacturer has stopped replying here, one of their prime target markets. It is much worse for us but it's a lesson learnt, never trust these small manufacturers. I made the same mistake with the DX3 Pro, which was also a lemon and a half. Had much better luck with Gustard, and I'm beginning to think they're the exception.