TOPPING D90 III、TOPPING D50 III

[Rja4000]

Spoiler: Spoiler alert

D50 III.
To be continued...

D50 III
SINAD 44.1 kHz 4V TRS output TosLink input
measured with RME ADI-2/4 Pro SE and E1DA APU, using Audio Precision APx 500 Flex software.
This is left channel. Right channel measures 0.14dB lower.

(Not an APx555B of course, and not sure conditions are exactly the same than Amir's. So don't compare this directly to Amir's figures. )

 

[Rja4000]

At 5V, values are flirting with 126dB

(This matches Topping's values)

 

[Palladium]

Why no @amirm review yet? He usually does new Topping products on day 0

Judging by the preliminary measurements from Rja4000 its not hard to guess why a vendor would want to downplay their newest product when it obliterates their existing lineup on value...

 

[Bleib]

At 5V, values are flirting with 126dB

(This matches Topping's values)

View attachment 362195

So as expected, likely fully transparent

 

[Rja4000]

For some other measurement, I see some weird results though.
May be me.
I'm investigating...

 

[DLS79]

Judging by the preliminary measurements from Rja4000 its not hard to guess why a vendor would want to downplay their newest product when it obliterates their existing lineup on value...

I'd bet it has more to do with some of the forum "members" here being so hostile, that they decided not to send samples to Amir to review unless he specifically requested them!

 

[Rja4000]

For some other measurement, I see some weird results though.
May be me.
I'm investigating...

EDIT: Issue fixed with firmware 1.21
https://www.tpdz.net/newsinfo/904685.html
(Thanks to @yys310 )


When using SPDIF input (Coax or Toslink), the sound gets broken on mine around -5dBFS.
I've seen that with IMD sweep initially, but I see the same with a pure sine wave, of course.
Above that level (closer to 0dBFS) or below that level, it works fine (see measurements above)
But the sound is completely distorted around that level. Not "listenable".

Could anyone with the D50 III try that, please ?
(@SloPoke , @BladerunnerSC50,...)
I'd like to know if only mine is broken. (That could be a -very weird- hardware issue).
I rather think it's firmware related though.
@JohnYang1997

I don't have that with USB.
So I thought I could go on measuring through USB,
BUT ASIO4All doesnt show the Topping as an output, so I can't test that completely right now..

 

[DLS79]

How did you upgrade ? Mine has 1.16.

it's on the official topping website.

Download - TOPPING

 

[Rja4000]

it's on the official topping website.

Download - TOPPING

Just saw it
Thanks

Doesn't fix my issue, unfortunately.

 

[Sokel]

Just saw it
Thanks

Doesn't fix my issue, unfortunately.

I would suspect some weird EQ interaction IF it applied on these inputs but it doesn't.
That's really weird.

 

[Rja4000]

That's really weird

It is.

 

[Bleib]

It is.
View attachment 362333

Seems to be a faulty unit, I'd return it to have it replaced.

 

[zdykstra]

How is the firmware upgrade performed for the D50 III ? I took a quick look through the documentation and if it's described in that PDF, I missed it.

 

[Bleib]

How is the firmware upgrade performed for the D50 III ? I took a quick look through the documentation and if it's described in that PDF, I missed it.

Should be done like any Topping DAC. Disconnect other Topping devices (or power off), connect USB cable. Run the exe file and it's done in a few seconds

 

[DLS79]

How is the firmware upgrade performed for the D50 III ? I took a quick look through the documentation and if it's described in that PDF, I missed it.

from the readme in the download zip.

English

Important note:

1, This firmware upgrade utility supports PC running Windows 10 and above with driver installed.
2, Never turn off or pull out power/USB cable during the update.


Firmware upgrade steps

1, Install drivers of this product (pass this step if you had already install drivers successfully)

2, Connect the product to your PC and turn on.

3, Run the exe file of this folder.

4, Click Browse.. and select the bin file of thie folder.

5, Click Start and wait for "Firmware upgrade finished successfully".

6, Check current firmware is already changed and click Exit and finish.

*****************************************************************************************

 

[yys310]

When using SPDIF input (Coax or Toslink), the sound gets broken on mine around -5dBFS.

View attachment 362294

I can confirm this problem. It happens to mine also with toslink input. I don't have coax output now so I only tested on toslink.
I happened at around -3.8dB to -5.2dB in my case with 44100Hz sampling rate input. I don't see this happening at 48, 88.2,96, and 192kHz input.

No wonder there's no review from ASR yet.

Edit: Attached picture is 1kHz sine via toslink input at -3.8dB, 44100Hz.
Both TRS and RCA out show the same behavior. Filter and PLL settings didn't change this behavior.
FW is 1.20

 

[Rja4000]

I can confirm this problem. It happens to mine also with toslink input. I don't have coax output now so I only tested on toslink.
I happened at around -3.8dB to -5.2dB in my case with 44100Hz sampling rate input. I don't see this happening at 48, 88.2,96, and 192kHz input.
View attachment 362399
No wonder there's no review from ASR yet.

Edit: Attached picture is 1kHz sine via toslink input at -3.8dB, 44100Hz.
Both TRS and RCA out shows the same behavior. Filter and PLL setting didn't change this behavior.
FW is 1.20

Many thanks for this confirmation !
I didn't try other sampling rates, but that's pretty interesting.
Volume on the DAC doesn't matter for this issue.
Only SPDIF input level does.
if it's working at 88.2kHz, that's even more weird.
Good news, somehow: it's most probably firmware related.

Thanks again !

 

[yys310]

I feel strange too...Unfortunately the motherboard toslink output doesn't support 176.4kHz for more testing.

 

[Rja4000]

I tested IMD with various sampling frequencies.
As you see above, it failed for all sf below 96kHz.
From 96kHz and above, it's OK.
It seems the level the issue occcurs varies with sampling frequency.
(The incident at -60dBFS 48kHz is not relevant)

 

[gvl]

It is.
View attachment 362333

I think it's showing you the middle finger, makes sense.