secret sauce
In one of their talks they chatted about listening to audiophiles and making changes to the design. I wonder if this is one of the consequences.
secret sauce
If you use dietpi on Pi, it has native Roon (RAAT) support so you will see it as an networked device in Roon. Volumio also works but only supports airplay which truncates down to 16 bits.Is there any way of sending the audio to the Raspberry Pi with Roon?
1 kHz. It is visible with other frequencies too but the shape varies.@amirm what frequency did you use for the THD measurement?
http://efu.jp.net/soft/wg/wg.html is amazing little program. Can generate signals real time or save to WAV.
Hehehe....didn't happen! But I was still very impressed!I'm going to over-explain everything so even if you don't have the knowledge of electronics or how it works; you will still be able to follow along.
18/38 pro chips have it too. Oppo-205 showed it the least, near negligible. They figured it out... but alas they might 'take it to the grave'I would be very surprised if the problem goes away by changeing these registers. Surely Topping, SMSL etc must have tested this?
Does any dac with the latest ESS PRO chips have this problem, or is it only the mobile chips?
In that case, it could maybe be a deliberate detuning of the mobile chip by ESS to differentiate them. I.e to make the PRO chips sound better than the mobile ones.
18/38 pro chips have it too. Oppo-205 showed it the least, near negligible. They figured it out... but alas they might 'take it to the grave'
I think it has to do with buffer/IV stage though, besides the obvious chip parameters.
I post this in March audio dac1 one thread but belongs here. I ran a level sweep versus THD, i.e. excluding the noise, and the problem appears plainly there:
It is remarkable in how they give up 20 dB of distortion the moment levels get beyond -40 dB. It seems like a design problem but how would a company like ESS let this get out this way???
Yes, using Roon. They won't appear as Windows devices otherwise.Yeah, I have DietPi installed with RAAT and AirPlay, but is there any way of getting the output from my Windows machine streamed via RAAT?
But I think that creating different test files at the required levels and use Roon to playback is the easiest route.
The issue is appearing in so many implementations with different approaches with the exception of Benchmark. It has to be a flaw of sorts that Benchmark discovered due to them analyzing it.Since the I/V stages appear to be single-ended followed by a quasi-differential buffer to single-ended, any tiny mismatches in gain and phase can lead to large reduction in common-mode rejection and apparent increases in distortion. >100 dB CMRR is very tough to achieve.
The issue is appearing in so many implementations with different approaches with the exception of Benchmark. It has to be a flaw of sorts that Benchmark discovered due to them analyzing it.
I don't know that John wanted to teach people how to fix the problem. He may have even misunderstood which issue we are talking about as we thought it was an IMD only issue at the time. Clearly though, John is very good at micro analyzing audio performance and likely enjoys very good support from ESS so has found and fixed this issue. Or avoided it somehow.Exactly. But the explanation from Benchmark guy doesn't quite explain it as he implied that the hump problem should only be visible in unbalanced variant. or I got him wrong..?
I don't know that John wanted to teach people how to fix the problem. He may have even misunderstood which issue we are talking about as we thought it was an IMD only issue at the time. Clearly though, John is very good at micro analyzing audio performance and likely enjoys very good support from ESS so has found and fixed this issue. Or avoided it somehow.
I think our effort here to keep analyzing it is good in figure out what is going on. We can get help then from our friendly manufacturers and possibly another push to ESS to listen.