• WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required as is 20 years of participation in forums (not all true). Come here to have fun, be ready to be teased and not take online life too seriously. We now measure and review equipment for free! Click here for details.

Review and Measurements of Topping DX3Pro DAC and Headphone Amp

Joined
Jan 16, 2019
Messages
11
Likes
1
Foobar, SoX resampler, just type in 768000 and it will resample to that rate. Select 'very high quality'/best, and wasapi or asio output device.
Your device should receive it if capable. A driver is likely necessary.
Thank you!!!!!!! Yeah, it works! :) Thank you! Such a easy way and I googled for many hours for a sample file... and couldn't find any.
 
Joined
Jan 16, 2019
Messages
11
Likes
1
Ok, now another problem. I got a DSD 256 file of a classical music and was able to play it.
But after 6, 7 minutes, suddenly I get the notification that there was a error and the device was not able to understand that signal.
Did anyone have a same experience? When I restart and move the timebar to that point, there's no problem and continues to play.
 

Veri

Major Contributor
Patreon Donor
Joined
Feb 6, 2018
Messages
1,435
Likes
1,275
Ok, now another problem. I got a DSD 256 file of a classical music and was able to play it.
But after 6, 7 minutes, suddenly I get the notification that there was a error and the device was not able to understand that signal.
Odd. Finnicky usb connection or power plug that wiggled the tiniest bit can cause such a thing, especially if your set-up makes it possible of touching the wires by accident.

Otherwise it might be your player that stuttered but even then I wouldn't expect a driver crash the likes you just experienced.
 
Joined
Jan 16, 2019
Messages
11
Likes
1
Odd. Finnicky usb connection or power plug that wiggled the tiniest bit can cause such a thing, especially if your set-up makes it possible of touching the wires by accident.

Otherwise it might be your player that stuttered but even then I wouldn't expect a driver crash the likes you just experienced.
Fine. It could be the cable cause I am using a "long" cable.
But it only happens on DSD256 file and not flac or mp3. ^^;
Thanks for the comment. I think no problem with the device. (I'm testing a few things so if there's a problem, I can claim it before claim period is gone.)
 
Last edited:

TiborG

Member
Patreon Donor
Joined
Feb 18, 2019
Messages
10
Likes
7
Fine. It could be the cable cause I am using a "long" cable.
But it only happens on DSD256 file and not flac or mp3. ^^;
Thanks for the comment. I think no problem with the device. (I'm testing a few things so if there's a problem, I can claim it before claim period is gone.)

I'd check the processor's performance, enough to take over the resampling. I had already eaten it once before when it was resampled to DSD 256 using JRiver. DSD 64 and 128 processed smoothly - about 20% CPU load. The old computer can easily get on your knees
 

nathanm

New Member
Joined
Apr 11, 2019
Messages
2
Likes
0
Guys, has somebody noticed how much the 24bit/32bit format settings in the Topping USB Audio Device Control Panel affects the sound?
After many hours of critical listening, I can say for sure that with the default 32bit setting, the sound is round, kind of veiled, lacks bass extension and dynamic range. When set to 24bit, it is the exact opposite and better overall. In theory, this shouldn't affect the SQ in any way, but...
My setup and settings are: Windows 10 Pro -> USB -> iFi Audio iPurifier 3 -> Olimex USB isolator -> DX3Pro -> Sennheiser HD6XX, powered with iFi Audio iPower 15V power supply. Low Gain and PCM filter at F-4.
Amir, it is interesting if this can be backed by your measurements - the difference is very clearly audible to me.
 
Last edited:

Veri

Major Contributor
Patreon Donor
Joined
Feb 6, 2018
Messages
1,435
Likes
1,275
Guys, has somebody noticed how much the 24bit/32bit format settings in the Topping USB Audio Device Control Panel affects the sound?
After many hours of critical listening, I can say for sure that with the default 32bit setting, the sound is round, kind of veiled, lacks bass extension and dynamic range. When set to 24bit, it is the exact opposite and better overall. In theory, this shouldn't affect the SQ in any way, but...
24-bit sounds juat a bit louder for me :rolleyes: which could explain 100% of what you're hearing.
 

nathanm

New Member
Joined
Apr 11, 2019
Messages
2
Likes
0
It is not only louder. Try to lower the volume and it will not be the same as 32bit.
For example listen to Eric Clapton Unplugged (Remastered) - the bass is much more extended and precise in 24-bit.
Note that with the stock PSU and without USB filtering it is less noticeable.
 

Veri

Major Contributor
Patreon Donor
Joined
Feb 6, 2018
Messages
1,435
Likes
1,275
It is not only louder. Try to lower the volume and it will not be the same as 32bit.
For example listen to Eric Clapton Unplugged (Remastered) - the bass is much more extended and precise in 24-bit.
Note that with the stock PSU and without USB filtering it is less noticeable.
Note this is not the kind of forum where publicising your personal non-verified, sighted and fallible personal experiences will be regarded as a 'truth'. There is absolutely zero proof upgrading your PSU, 'USB filtering'(what filter?) or bit depth will have a measurable effect on the DAC output. None. This is not head-fi where this kind of 'sounds much better!' circlejerk is applauded or encouraged....

https://www.audiosciencereview.com/...o-you-need-linear-power-supply-for-dacs.7021/
https://www.audiosciencereview.com/...-measurements-of-schiit-wyrd-usb-filter.5717/
https://www.audiosciencereview.com/...s-of-intona-usb-isolator-for-audio-dacs.2616/
 
Joined
Feb 3, 2019
Messages
47
Likes
34
Today after more than week of using my new DX3 Pro from "new batch" I experienced unit going to standby on its own first time. After powering it back on it is again working fine. So there is still some work to be done on Topping side. Just note I have disabled USB automatic power on / power off.
 
Joined
Feb 3, 2019
Messages
47
Likes
34
So update after few hours, my new DX3PRO died - again permanent standby issue. I lost confidence in quality and flawless design of this unit. This is already my second unit which broken exactly the same way. Contacted topping really interesting what they will respond.
 
Joined
Feb 3, 2019
Messages
47
Likes
34
@Pavel what is your opinion in question of replacing OPA2140 to OPA1612 as you have done, will resolve my standby issue permanently? I'm really disapointed and starting my confidence in Topping products and their quality/design. I do not believe that I could receive two units which will from some reason have either bad batch or inappropriate processing of OP2140. Thanks for any inputs.
 
Joined
Jan 18, 2019
Messages
46
Likes
45
Location
Russia
@Pavel what is your opinion in question of replacing OPA2140 to OPA1612 as you have done, will resolve my standby issue permanently?
I can not answer you. Because I bought a DX3 for experiences. Now my copy is changed 70% of the factory design. OPA1612 worked well instead of OPA2140. But now NE5532 stands there and I don’t hear the difference.
 
Last edited:
Joined
Feb 3, 2019
Messages
47
Likes
34
I can not answer you. Because I bought a DX3 for experiences. Now my copy is changed 70% of the factory design. OPA1612 worked well instead of OPA2140. But now NE5532 stands there and I don’t hear the difference.
What are you using as op amp instead of OP1612? Instead OPA2140 you have now NE5532 right?
 
Joined
Jan 18, 2019
Messages
46
Likes
45
Location
Russia
Yes, installed NE5532. This OP is old but stable and time-tested. I did not hear the difference in sound between OP1612 and NE5532 (OPA2140 burned out) in the headphone amplifier.
I do not want to risk my hearing and expensive headphones.
In line output, instead of OPA1612, MUSES02 is now installed.
NE5532 and MUSES02 have low bandwidth. Аnd I like the way they sound.
 
Last edited:
Joined
Feb 3, 2019
Messages
47
Likes
34
Yes, installed NE5532. This OP is old but stable and time-tested. I did not hear the difference in sound between OP1612 and NE5532 (OPA2140 burned out) in the headphone amplifier.
I do not want to risk my hearing and expensive headphones.
In line output, instead of OPA1612, MUSES02 is now installed.
NE5532 and MUSES02 have low bandwidth. Аnd I like the way they sound.
Do you know why your original OPA2140 burnet out? Did you experienced the permanent standby issue with it as well? After replacement of all compomnents you mentioned did you ever experiences that device goes to standby itself?
 
Joined
Jan 18, 2019
Messages
46
Likes
45
Location
Russia
Do you know why your original OPA2140 burnet out?
Just in one channel of a linear output DC +5V appeared. I was lucky that at this moment the headphones were not connected. After removing the OPA2140 from the DX3, the output line is working again.
After replacement of all compomnents you mentioned did you ever experiences that device goes to standby itself?
No, I had no standby problems. The power system has changed a lot.
I have replaced many components and a circuit diagram. Enumeration of all takes a lot of time.
 
Joined
Feb 3, 2019
Messages
47
Likes
34
Just in one channel of a linear output DC +5V appeared. I was lucky that at this moment the headphones were not connected. After removing the OPA2140 from the DX3, the output line is working again.

No, I had no standby problems. The power system has changed a lot.
I have replaced many components and a circuit diagram. Enumeration of all takes a lot of time.
I had something similar with first unit after I somehow managed to power it again on from permanent standby there was permanent 5v on one channel on headphone output. For how long are you running it with MUSES + NE5532? Is it perfectly stable?
 
Top Bottom