I was trying all output devices in Foobar2000, all of them are working perfect. I think the sound is more clear than before when I am using DSD device, the odd is need to use volume control on the preamp/receiver.
Try to listen a few songs before you run update the FW to see if the sound is better or not. Glad that itās final come out, I thought we have to wait until Black Friday or Xmax ā¦lolā¦
Anyway, I am waiting to get Tone2 for new preamp project. Hope, itās under $200
To support Native DSD on Linux, still need to apply the patch for Khadas PID, weāve committed the patch to upstream linux kernel but still take time to be merged.
For the Linux Khadas 4.9.224 @numbqq or @hyphop will commit the patch next week.
Have you tried ALSA? I remember ALSA was working excellent. I lost my linux usb, I will build again and test later. So far itsā great that all the device output in windows is working.
I built this Linux audio in March, the Tone1 work with DSD64 without problem by using ALSA. I havenāt figured out how to play SACD ISO with this linux version yet so not sure if the ISO works like in Windows10
the ānewā sound is decidedly less wonderful - using either the wharfedale 10 speakers (10.1ās + 10.gx sub) via a nad d3020 amp (previously gorgeous, now profoundly disappointing), or the focal elear headphones (as above)
itās not totally crap, but it is significantly less musical - a combination of harsh upper register and muddy bass
yes, iām hearing some frequencies that were masked before, but a lot of the detail i liked is missing, like listening from behind a curtain compared to before
my advice ? donāt go there, unless khadas can confirm the āupgradeā can be easily reversed - which in my experience in the last day suggests is not (easily) possible - in fact so far = impossible
Khadas controversy! Could you post your REW (Room Acoustics Software) measurements for both v1.04 and v2.00 firmware and what MIC you used for the audio measurements e.g Dayton Audio EMM-6 etc
Subjectivism is an involved discussion with regard to audio reproduction one persons perception can be different to the next.
Wiithout actual data, measurements and evidence your post simply becomes an opinion, I am not attempting to derail your own experience simply trying to get to actual evidence if there are changes between the 2 firmwares.
With regard to downgrading the firmware v2.0 to v1.04 having tested this successfully this is a simple process. If anyone on this post could post there measurements for different drivers i.e Windows UAC 2.0 driver, Khadas_Tone_Driver_V4.86.0_201118 etc this would be most helpful.
my board is recognised by windoze as tone1 and plays, but there is no recognition by either version of tusb (current and the original) on either computer i have tried (both win10 - pro and standard)
agree on perception being individual; the fact that it sounds crap to me is the important issue for me - if it sounds good to you, then enjoy !
please post explicit instructions on reversing the flash, as the failure to even see the device in tusb makes it rather problematic
I think you can use this to flash it back old FW since itās the only one can detect the device after flash
Khadas_Tone_Driver_V4.86.0_201118: Install the driver in order to run step 2
Khadas_Tone_DFU_Tool:
My bass is pretty much the same and more musical in midrange. Maybe depend on what equipment we have. I connect Tone1 directly to this integrated tube amp. At first, itās kinda strange but after a while, I really like it.
I could take a little offence at your passive agression (I am British) I was simply stating the process from my own experience was not difficult.
As Alashikita has posted launch Khadas_Tone_DFU_Tool_V4.86.0_201118 open the KHADAS_XMOS_80B_PID000A_DFU_20190409 (v1.04).bin file and flash. Windows will auto configure and you should see XMOS DFU in device manager.
somehow i neglected the Khadas_Tone_DFU_Tool_V4.86.0_201118 part, probably the consequence of frustration and despair
donāt take offence at (your perception of my) passive aggression - understandable as iām australian and less inclined to accept being patronised (especially by the mother country) when iām annoyed already - not that you meant it to be patronising i guess
like most things, simple to fix if you have done itā¦ and now itās simple
as for perception bias, i am well aware
however, i am also a creature of habit, and my review reflects that the music i sampled is so well known to me that i was aware of differencesā¦ that i found gratingā¦ maybe it is ābetterā with the new drivers, but being accustomed to the old one means itās music as i expect it to sound; neither is superior (maybe it is to acoustic science as numbers), but one is preferred
apologies for any perceived slight, which was not aimed at you, but reflective of the hours i had wasted when too tired for that to be sensible
thanks sincerely to thd0*1 and Alashikita for fixing it
fwiw, it sounds ābetterā to me, and iām the one that has to listen to it here
itās my repeated experience with sound set ups that there is definitely superior synergy with some chains of components, and i guess by the same token, firmwares, where what appeals to personal taste is accentuated and thus makes it magical
Are we compare the British, Australian, and US? I thought Australian and British have similar accentā¦lolā¦j/k
I mean strange in more tones than I heard before. So I started playing couple more songs to see if theyāre different and they did. I was listened with high biterate songs.
Not sure which driver you use with v1.04 but I like XMOS driver instead of Thesycon for windows 10 while ALSA for archive linux.