Veri
Master Contributor
- Joined
- Feb 6, 2018
- Messages
- 9,515
- Likes
- 11,861
I believe the 9028Pro Benchmark utilises does not suffer from this problem in the first place iircSame goes for benchmark AFAIK: they use their own 200kHz asrc
I believe the 9028Pro Benchmark utilises does not suffer from this problem in the first place iircSame goes for benchmark AFAIK: they use their own 200kHz asrc
This hump has nothing to do with the I2C register setting and is a pure hardware issue.
If the layout of the I/V and LPF circuits is no problem, then only one or two key variables need to be adjusted to solve the problem.
But for work reasons, I can't disclose more details.
MysteriousWithout disclosing anything confidential can you tell us whether there’s any chance of this getting fixed via a firmware update or is it only possible via a hardware revision?
Secondly, do you have an opinion concerning the audibility of the hump? I’m just wondering if this whole debate is purely academic if the hump is well below the threshold of audibility.
They use ES9028PRO just like the Benchmark. The 28 chip seems immune to it.As far as I can tell the just reviewed Okto DAC8 doesn't seem to have any external ASRC on it:
![]()
For transparency reasons, could you tell us what is the company you work for?In short, only hardware revisions can remove this hump.
I didn't have time to try ABX before, but I simply compared the sound of two boards with or without hump.
The sound of the board without hump is obviously more natural.
When I have time, I will find a few different models of the PCBAs, adjust to the state of hump and no hump, and do some ABX.
The company I work for is currently an authorized distributor of ESS.For transparency reasons, could you tell us what is the company you work for?
That's why I'd think twice before doing business with ESS. Any decent chip maker would have put that information in the data sheet or an application note publicly available on their website.The company I work for is currently an authorized distributor of ESS.
Because of that, I provide technical support to some local audio equipment manufacturers.
As for the solution to remove this hump, I actually found it more than a year ago.
But these details are currently only available to our customers, I am not sure if this can be disclosed publicly.
I appreciate that but please convey to ESS that a lot of their implementers of their DAC are getting this wrong as a result of such secrecy. In the past, this didn't matter but now, we have put a huge spotlight on it so they need to change their strategy and address this. Perhaps they have noticed that some Chinese companies are already switching away to AKM. I see the term "ESS Hump" now used in other forums and pretty soon their brand will be hurt if they don't act and provide help to their manufacturers to remedy this.But these details are currently only available to our customers, I am not sure if this can be disclosed publicly.
Thank you for understanding that!I appreciate that but please convey to ESS that a lot of their implementers of their DAC are getting this wrong as a result of such secrecy. In the past, this didn't matter but now, we have put a huge spotlight on it so they need to change their strategy and address this. Perhaps they have noticed that some Chinese companies are already switching away to AKM. I see the term "ESS Hump" now used in other forums and pretty soon their brand will be hurt if they don't act and provide help to their manufacturers to remedy this.
And oh, they need to answer their emails when someone like me contacts them.I reached out to them twice I think and they would not even bother to answer my email.
Awesome !!Thank you for understanding that!
In fact, I am consulting the possibility of publicly disclosing these technical details.
If I can do this, I will post it as soon as possible.
Convince yourself it's not realAnd, for those of us with the hump? View attachment 23805
Convince yourself it's not real
in all seriousness, whether it's audible is heavily contested.
Thank you for understanding that!
In fact, I am consulting the possibility of publicly disclosing these technical details.
If I can do this, I will post it as soon as possible.