Yes, it's ridicolous cheap but I am willing to pay 100€ more to get a) a proper driver and b) a balanced output for two Geithains. Going for the Schiit Modius most likely.
...now here is where it gets interesting...
Dear friend, Our Sonata HD PRO (Android version) has the latest firmware. If your product cannot work with Android phones, please update the firmware. When upgrading the firmware, please enter these two strings: 22E1 and E203 . In addition, we have a large-scale promotional event from August 24 to 28, 2020, looking forward to your attention. have a nice day ! TempoTec team.
... once I installed the driver it allowed to select ASIO but in foobar it is completely broken (only with ASIO the other methods still work perfectly fine), has buffering issues, plays at slightly lower speed and the Tempotec ASIO Control panel is really clunky, ...
I need to correct myself here, upon further testing I realized that ASIO was only causing troubles on foobar while being configured on any combination of either 32 bit and/or 100ms buffer. also the Tempotec ASIO control panel works fine, the issue was that it came without any instructions and doesn't make it clear that you should relaunch the audio player upon changing any configuration (I was used to others that instead encouraged us to launch the control panel from within the player)
View attachment 75989
the upper half of the Tempotec control panel is the one that control the settings of the device when used by the windows mixer that one is real time, the bottom half is the one that control the ASIO settings, you are right in that it is also real time, sort of, if you change a setting there it won't affect the currently playing file but one doesn't need to close and open the program as I previously stated, it is enough to stop the song (not pause) and play again or just play a different file. that been said I still have the issue on foobar where setting up the panel at 32bit and/or 100ms seems to slow down playback slightly but that could just be something wrong with my system, maybe sometime in the past I messed something up while playing with plug insStrange, I'm having no issues with ASIO playback at 32bit or 100ms buffer, or any other settings. And I can change anything in the Tempotech control panel on the fly and the changes are instantly reflected in the Windows sound control panel.
damn, have never even thought to go this far. Nice find to fix the issue, now I've gotten my popping gone too somewhat.On a W10 PC here is where it gets interesting, I went to the device manager and noticed that the SONATA USB Audio controller still was using a seemingly generic USB Audio 2.0 driver, so I manually selected the Tempotec folder created by the installer of the driver from the hidizd website and ask it to look for another one... which it did. however in order for it to work properly I had to enable authorization for unsigned drivers before selecting the driver update. after this, it enabled me to select Kernel stream, which woks perfectly on foobar
View attachment 75853View attachment 75854
damn, have never even thought to go this far. Nice find to fix the issue, now I've gotten my popping gone too somewhat.
Though now I have the small matter of the PC crashing every time I touch the Windows volume bar (which isn't an issue with speakers and headphones, but makes IEMs a pain). BSOD says SHDUAC.sys or such, so it should the the driver.
Maybe its because I updated the firmware to V3.0 before doing this fix. I'll try a bit more to see where it gone wrong.
Dear friend, Our Sonata HD PRO (Android version) has the latest firmware. If your product cannot work with Android phones, please update the firmware. When upgrading the firmware, please enter these two strings: 22E1 and E203 .
(update: I reflashed to the V1.0 firmware and used the driver fix above, no more BSOD when adjusting the Windows volume)
Interesting behavior I've discovered in my Tempotec HD Pro in Foobar2000. When running WASAPI (push) mode, when you play a new track it takes about three seconds for the music to start playing in all samplerates except 96k and 192k. This includes 44.1k, 48k, 88.2k, and 176.4k.
This makes me think that the device is resampling everything to either 96k or 192k in WASAPI (push) mode, which is odd behavior. As one would expect, this behavior persists no matter what I set the device to in Windows or in the Tempotec control software.
WASAPI (event) mode is very glitchy. Any 24bit track comes out garbled.
No apparent problems in ASIO mode. I also cannot reproduce the behavior on my Jriver on Windows.