In my particular case, I have horrible aliasing and clipping of sound that I can hear in the normal music with SE846.All,
I'd like to share some ES100 data measured using Audio Precision 2722 right next to my desk.
[Test condition]
- No load
- AK4375a / sharp roll-off / 1x
aptX (with Galaxy S8 source device)
USB (lossless, with iMAC USB)
It shows the baseline performance of ES100 HW.
Unfortunately, ES100 USB supports 16-bit only, the overall THD+N is limited by the 16-bit PCM (-96dB), not by H/W.
Please take a look at them all above.
You will find there's no such a design flaw or HW defect as SubMash insist.
If ES100 have any H/W issue, all the BT codecs, and USB would result in the same defect.
Because all of them use the same H/W resource including DSP, DAC, and Power.
SubMash mentioned AAC & USB sounds OK.
Then it's not an H/W issue.
And if we have the problem with aptX,
how could we have ES100 in the Qualcomm's official aptX product list?
They have their own qualification and certification process for aptX enabled products.
We sent ES100 to them for their testing and finally had ours on the list.
https://www.aptx.com/products/radsone-earstudio-es100-bluetooth-receiver-headphone-amplifier
Lastly, I just took a look at the SubMash test results and graphs from his mobile phone screenshot.
It seems that he ran the test with his mobile phone.
Anyway, as I see them, those results are showing the tremendous and unacceptable noise.
If those graphs are indeed real and represent ES100 output,
the sound would be considerably worse than the expected,
and everyone would definitely notice the defect right at the start.
We can't deceive many thousands of ES100 users.
The users are not fools and would notice the that much of conspicuous defect very easily.
Thanks and Regards,
WS
I guess I'm the only one yet who used it with high-resolution low impedance earpieces.
And they should work if you have 0.5Ohm claimed OI.
Let's go through your points:
I never insisted (moreover I hope for the opposite) that it's design or H/W issue. So, that's not true.
THD+N doesn't show aliasing or clipping. I already know it from RMAA. And you choose to measure only this by showing exactly same figures I got from RMAA.
It is NOT some kind of ultimate test that shows there is no issue at all. You intentionally not addressing the issue I'm talking about and instead post charts that are masking issue.
Issue decreases without load - exactly what you have done - you removed any load (well, because it's easier - why bother to put any work on your product...).
I assumed that oversampling might be bringing issue - and you turned it off in your tests.
I already have shown that dirt cheap APTX receivers do not exhibit aliasing or clipping at such levels as your product.
Bringing names of Qualcomm is NOT answering the issue I have - you do not search for the issue at all.
A company that you paid for certification is not certifying your product claims.
Reviewers that you asked to do review did no measurements or synthetic tests at all and we have no idea if they were even paid or not (and from my experience - that's how they make money).
You have few people here who ok with what they got. And you have 1 who is not.
Meanwhile: this is the test I'm asking to do by those who have 16Ohm and below earphones on EarStudio:
http://www.audiocheck.net/audiotests_mosquito.php "Mosquito Tone 2" test on this page - set normal maximum volume and run it - if you hear anything clearly - you should not be. Check with and without oversampling.
I can barely hear anything from Nokia and I hear plenty off-tones and grinding noise from ES.
And that is clear indication that it should not be like that - it's not a codec inherent issue.
Last edited by a moderator: