• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Review and Measurements of WesionTEK Khadas Tone Board DAC

I inquired them on Facebook which purchase option should be the fastest to ship to my country and they said ordering directly from the website should take 15 days at most to arrive (with the free shipping option) and I did just that. But somehow the shipment lingered around China for 2 weeks before it actually being shipped out lul. I made a complaint to their customer support and their follow-ups were very thorough. They called my local courier company, kept me updated on the shipment thru email, Facebook and even WhatsApp. I'm really impressed with their customer service. I should be receiving the shipment within a week.
Yeah I'm sure it'll be fine. Fact that it lingered in China was probably single's day and black friday's fault. Probably millions of orders lol
 
Yeah I'm sure it'll be fine. Fact that it lingered in China was probably single's day and black friday's fault. Probably millions of orders lol
Yeah that's probably the reason. :)
 
Got the Khadas board in a week ago or so. Looked around the house for a case, found an old Water Testing Kit that came in a clear plastic box. Couple of notches and some 3M mounting squares later.. the board is no longer naked!

No probs using spdif from allo digione. I powered the board with an allo 5V ps which worked great. Then I plugged board into a free pi3b usb port and setup MPD to output to both digione and usb. Idea was some A/B testing against my tda1543x4 dac. Anyways, 16 bit unprocessed via usb was fine. Higher bits (32) I was getting pops and crackles. Also the pi3b usb dumps processing noise unlike the 5v ps.

Few days later I setup the board on a win7 box with Thesycon drivers. I saw the board is using the same idents as the xmos dj kit. This means finding v4 licensed drivers are out. Latest I found was v3.34 (2016). The win7 box usb was much cleaner than the pi, similar to direct 5v. However the popping issues remained when playing 16 bit with DSP processing on fb2k (Sonarworks). fb2k does internal 32bit. Setting output to 24bit improves the clicking.. I installed a dsp called smart dither and got decent results limiting the stream to 21 bits. I will have to experiment some more to determine the max rate. As you window the rate down. the clicking/popping volume drops.

Suffice to say I’m running into issues with usb, both via linux in pi, and windows with drivers. I tried a different usb-c cable with similar results. DSD via usb is perfect (DoP, DSD64 and DSD128). Unprocessed 16bits perfect. Higher, issues appear. Same results too with the v2.24 (2014) Khadas linked drivers btw.

As for sound - biggest takeaway I found is how “right” my tda1543 is. No big differences in tonality against Khadas. Though I felt I “enjoyed” the tda more.

mcgo
 
Anyone else having problems with the Khadas DAC on Mac? Sometimes I get static noise that increases. It also happens when switching resolution. I'll try other cables tomorrow, so I'm hoping for the best.

By the way, anyone out there who could give any pointers on upgrading the firmware? I have the .bin files, but not the upload application.
 
Just a heads up on the firmware posted here. I upgraded and now the card won't output audio, either in Windows or Mac OS. I've planned to test the THD compensation tomorrow, but that went down the toilet. Anyone got the original firmware?
 
Just a heads up on the firmware posted here. I upgraded and now the card won't output audio, either in Windows or Mac OS. I've planned to test the THD compensation tomorrow, but that went down the toilet. Anyone got the original firmware?
There’s a bug in the firmware, they are going to fix it in one or two days....
 
Hi,
What causes the annoying click and the end of every music track when using this Khadas dac Board and how to stop this or is nobody else experiencing it?
 
Seems to be only when playing DSD files must be the way its being converted
 
The new driver for windows 10 (XMOS-Stereo-USB-Audio-Class2-Driver-3033_v2.26.0) can't be installed, it gives installation error.
There is no installation problem with previous driver (Thesycon-Stereo-USB-Audio-Driver-v224_Win7_win10).
 
Re: my usb high-bitrate issues -- I was hoping someone with a Khadas board and using usb would throw some 32bit stuff at their unit and see if they can duplicate. For example, some 32bit Vinyl rips or what have you. I'm playing with it now, and at 32bit the unit pops pretty frequently, multiple times in the first 10 seconds, so it should be immediately noticeable to you. At 24bit it is not as frequent. I suggested 21bit in my previous post as the level which clears things up -- it may actually be 20bit. At 21bit I can hear the odd click or pop every now and then. If confirmed, this may be an xmos firmware issue fixable via an update so it would be nice to check while it is still being worked on.
 
Thus far I have experienced absolutely no popping and/or clicks with my Tone Board using 16-Bit 44100 Hz, 24-Bit 44100 Hz, or 32-Bit 44100 Hz.
 
The new driver for windows 10 (XMOS-Stereo-USB-Audio-Class2-Driver-3033_v2.26.0) can't be installed, it gives installation error.
There is no installation problem with previous driver (Thesycon-Stereo-USB-Audio-Driver-v224_Win7_win10).

I had to turn off the driver signature protection in Windows 10 to install. Here's how to do it. You should reenable it after installing. You need to reboot windows after doing the disable command: https://windowsreport.com/driver-signature-enforcement-windows-10/
 
BTW: I am still using the older driver "Thesycon-Stereo-USB-Audio-Driver-v224" what added benefits/corrections does the new driver "XMOS-Driver-V2.26.0-for-Normal-Use" bring us? I was hesitant to update as it was new and maybe rightly so as per @helloworld bug report.
 
Thus far I have experienced absolutely no popping and/or clicks with my Tone Board using 16-Bit 44100 Hz, 24-Bit 44100 Hz, or 32-Bit 44100 Hz.
Thanks for the confirmation. It gave me the impetus to disconnect everything, uninstall the driver, reboot, ensure all the tusb*.* files were actually "deleted", then reinstall v2.24 and connect when prompted. Guess what? The gremlins are gone! No problems now with 32bit stuff. Why isn't everything this easy? :)
 
Back
Top Bottom