• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Topping DX5 II

After updating to the new firmware I just noticed that the display showed HP DC abnormal and stopped the audio while listening to one specific track in my electronic music playlist. Does this mean the DC protection is working? This was the first time that this happened.

Music that caused it to show up: https://tidal.com/browse/track/402060193?u
I also get the abnormal warning both with and without exclusive mode the volume just has to be loud enough. I guess it's because of the clipping at the red lines shown here in Audacity. I marked a few points in the song at the bottom where it happened to me

1753297159897.png
1753297207601.png
 
I downloaded the "Bloc Party - Blue Light (Engineers 'Anti-Gravity' mix)" mentioned earlier in the thread as FLAC from Tidal and as soon as it reaches the ~26.5 seconds (first image) where I think the DC offset starts the sound cuts out and it just says "HP DC abnormal" on the screen and doesn't disappear. It only continues playing and shows FFT display again at ~2:29.6 (second image) where DC offset ends. So I guess our ears and equipment is safe with the DX5 ii? This happens for me even with -99 dB low gain playing in Tidal with exclusive mode enabled. Without exclusive mode (same gain on DX5 ii) but maxed out volume in Tidal it happens at 70 volume level in Windows mixer.

1753299801695.png

1753299858848.png
 
Last edited:
Good, hopefully it works now
 
I downloaded the "Bloc Party - Blue Light (Engineers 'Anti-Gravity' mix)" mentioned earlier in the thread as FLAC from Tidal and as soon as it reaches the ~26.5 seconds (first image) where I think the DC offset starts the sound cuts out and it just says "HP DC abnormal" on the screen and doesn't disappear. It only continues playing and shows FFT display again at ~2:29.6 (second image) where DC offset ends. So I guess our ears and equipment is safe with the DX5 ii? This happens for me even with -99 dB low gain playing in Tidal with exclusive mode enabled.

View attachment 465249
View attachment 465250
Yep, I think we can check this out of the list.

Edit: what would be really cool, is if someone could measure its output with a DMM the moment DC kicks in (and in general)
 
I am still communicating with topping support about a jitter problem that causes the audio to stutter every few seconds when using the optical input connected to my LG C2 and PS5. They are responding very fast (12-24h) and they even bought a LG C2 and PS5 to test this!

PEQ also seems to work correctly now. So PEQ configs dont disappear after restart. The changelog also mentions some more fixes.

Changelog:
V1.49 (July 17, 2025)

*Fixed: After detecting abnormal headphone amp DC, the main interface no longer displays "HP DC abnormal".
*Fixed: Audio distortion when switching sampling rates via USB DoP input.
*Fixed: Display lag when rapidly adjusting volume in FFT and VU meter interfaces.
*Optimized: The 5 system preset PEQs can now be edited (parameters and names) or deleted directly via Tune.
*Optimized: EQ entries in the menu are now shown as "number + name" instead of just a number.
*Added: Option to retain PEQ configurations when restoring factory settings.
*Added: In the FFT interface, when adjusting volume, switching inputs, or switching outputs,
a large-font display will appear for 3 seconds before returning to the normal interface.
*Fixed: Several other known issues.

edit: I wonder what the fixed 'Several other known issues' are. But sounds good haha
 
I am still communicating with topping support about a jitter problem that causes the audio to stutter every few seconds when using the optical input connected to my LG C2 and PS5. They are responding very fast (12-24h) and they even bought a LG C2 and PS5 to test this!

PEQ also seems to work correctly now. So PEQ configs dont disappear after restart. The changelog also mentions some more fixes.

Changelog:
V1.49 (July 17, 2025)

*Fixed: After detecting abnormal headphone amp DC, the main interface no longer displays "HP DC abnormal".
*Fixed: Audio distortion when switching sampling rates via USB DoP input.
*Fixed: Display lag when rapidly adjusting volume in FFT and VU meter interfaces.
*Optimized: The 5 system preset PEQs can now be edited (parameters and names) or deleted directly via Tune.
*Optimized: EQ entries in the menu are now shown as "number + name" instead of just a number.
*Added: Option to retain PEQ configurations when restoring factory settings.
*Added: In the FFT interface, when adjusting volume, switching inputs, or switching outputs,
a large-font display will appear for 3 seconds before returning to the normal interface.
*Fixed: Several other known issues.

edit: I wonder what the fixed 'Several other known issues' are. But sounds good haha

What's the connection chain from the PS5/TV to the DX5 II? Have you tried different optical cables?

I only ask because I just observed some pretty bad stuttering from an optical connection in my current desktop system and a D10s (using it as a USB DDC to fix a popping issue from my Mac), but only if I set it to 24/192 in my Mac's MIDI app (despite 24/192 being within the D10s' spec'd capabilities). And it doesn't stutter if I use a different, specific optical cable.
 
Hello. I am choosing a DAC/AMP for headphone Dan Clark Aeon 2. Initially I was thinking of buying a Topping e50 + l50 bundle, but when I saw the price of the DX5 ii, I didn't understand what the catch was. It sounds like a very good deal without any significant drawbacks. I'm most interested in the sound, since I don't have the opportunity to listen to it personally, so I ask the owners to share the details. And if anyone has encountered this e50 + l50 bundle, how does it compare to them?
 
What's the connection chain from the PS5/TV to the DX5 II? Have you tried different optical cables?

I only ask because I just observed some pretty bad stuttering from an optical connection in my current desktop system and a D10s DAC/bridge, but only if I set it to 24/192 in my Mac's MIDI app (despite 24/192 being within the D10s' spec'd capabilities). And it doesn't stutter if I use a different, specific optical cable.

Thanks, I will order a second cable and try that. Are there big differences in the quality of optical cables with higher priced ones?
 
Hello. I am choosing a DAC/AMP for headphone Dan Clark Aeon 2. Initially I was thinking of buying a Topping e50 + l50 bundle, but when I saw the price of the DX5 ii, I didn't understand what the catch was. It sounds like a very good deal without any significant drawbacks. I'm most interested in the sound, since I don't have the opportunity to listen to it personally, so I ask the owners to share the details. And if anyone has encountered this e50 + l50 bundle, how does it compare to them?

After reading some stuff here I learned that the difference in sound or tonality between DACs should be almost non existend, they should be transparent. But I did compare the DX5 II to the SMSL RAW-MDA1. The difference was minimal but I did like the sound more on the DX5II, it sounded more detailed to me. But its quite hard to properly compare DACs (volume matching etc.). I did return the SMSL afterwards, the DX5II sounds fantastic and has enough power to power most headphones.
 
Thanks, I will order a second cable and try that. Are there big differences in the quality of optical cables with higher priced ones?

I don't think you need to spend much money for a cable. Also, I suspect that if you're using it with a TV/PS5 that the sample rate will be something like 48kHz, which shouldn't be a problem at all.

My stuttering issue only happens if the D10s is set to 24/192 in my Mac -- dropping it down to 24/96 completely gets rid of the stuttering (also, non-existent if I use the coax out instead of optical). It also is not an issue if I use a SMSL PO100 Pro instead of the D10s (even at 24/192). Even though I use a D50 III DAC, I have to have a USB DDC between my Mac and D50 III to fix a popping issue caused by my Mac's USB output.
 
Just updated firmware 1.39 > 1.49 without any issues. Process is as smooth as can be.

I did it too, I even messed up by putting in the Zip file in the 1st attempt lol. All I got was a "unrecognised file type" error but nothing bad happened, it even removed the file from the folder by itself. Then put in the correct file it did it first try.
 
I did it too, I even messed up by putting in the Zip file in the 1st attempt lol. All I got was a "unrecognised file type" error but nothing bad happened, it even removed the file from the folder by itself. Then put in the correct file it did it first try.

And has it resolved all/most of the issues you mentioned last month?
 
And has it resolved all/most of the issues you mentioned last month?

I haven't noticed the same issue thus far. Also, I notice the VU meter needle is more "lively", before it was just "there", around the middle and hardly swing about like a real one would. Now it reacts to music a LOT better. Before it was so anemic that I don't even think there was a point, it was like looking at a jpeg of a VU meter rather than a representation of the sound.
 
I haven't noticed the same issue thus far. Also, I notice the VU meter needle is more "lively", before it was just "there", around the middle and hardly swing about like a real one would. Now it reacts to music a LOT better. Before it was so anemic that I don't even think there was a point, it was like looking at a jpeg of a VU meter rather than a representation of the sound.

There'd been a few people mention that the VU meter was "sluggish", so I suspect it had been reported, and fixed (possibly one of the "other known issues" in the change log).
 
More than 70 pages on finding all sorts of problems and edge cases, comparisons to devices costing 4x and everything in between, geopolitical analysis, dsp theory on digital eq, the indignation of releasing a broken/half engineered/prototype product, industry practices on qc and components, history of brands and so long and so forth and all it took was a software update to have everybody’s peace of mind :)

And sure some more edge cases will show up, and an actual small percentage of hardware defects might appear, which will be in turn patched and fixed by support and warranty, I mean the company is literally buying same equipment of users to try to replicate their issues, say what you want, but this proves the company cares and is well active and fast moving. This for me is all I need to see to green light the purchase. I’ll happily wait for stock of the silver and then buy the product. I saw and read enough.
 
For German users: I am selling my DX 5 II in black, as I got a good offer for a Luxsin X9.
If you are interested, drop me a private message.
Sold, please don't contact me further
 
V1.49 (July 17, 2025)

*Fixed: After detecting abnormal headphone amp DC, the main interface no longer displays "HP DC abnormal".

I Updated to 1.49 Today but Still get "HP DC Abnormal". I can trigger it on specific Parts on Songs.
Mostly Drum and Bass like Current Value.

I tried a second Flash but still get this Error.

How can i contact Topping to tell them the Issue ist still there?
 
I Updated to 1.49 Today but Still get "HP DC Abnormal". I can trigger it on specific Parts on Songs.
Mostly Drum and Bass like Current Value.

I tried a second Flash but still get this Error.

How can i contact Topping to tell them the Issue ist still there?

Which songs in particular? I get HP DC Abnormal if there's clipping or serious DC offset like below

I downloaded the "Bloc Party - Blue Light (Engineers 'Anti-Gravity' mix)" mentioned earlier in the thread as FLAC from Tidal and as soon as it reaches the ~26.5 seconds (first image) where I think the DC offset starts the sound cuts out and it just says "HP DC abnormal" on the screen and doesn't disappear. It only continues playing and shows FFT display again at ~2:29.6 (second image) where DC offset ends. So I guess our ears and equipment is safe with the DX5 ii? This happens for me even with -99 dB low gain playing in Tidal with exclusive mode enabled. Without exclusive mode (same gain on DX5 ii) but maxed out volume in Tidal it happens at 70 volume level in Windows mixer.

View attachment 465249
View attachment 465250
 
I Updated to 1.49 Today but Still get "HP DC Abnormal". I can trigger it on specific Parts on Songs.
Mostly Drum and Bass like Current Value.

I tried a second Flash but still get this Error.

How can i contact Topping to tell them the Issue ist still there?
Isn't this behaviour that the product is supposed to do... if the track has a significant DC component?

Several users were reporting that the headphone DC protection wasn't working, but after 1.49 it is.
 
Last edited:
I Updated to 1.49 Today but Still get "HP DC Abnormal". I can trigger it on specific Parts on Songs.
Mostly Drum and Bass like Current Value.

I tried a second Flash but still get this Error.

How can i contact Topping to tell them the Issue ist still there?

Pretty sure that's the expected behaviour? It wasn't doing that with v1.39, AFAIK.
 
Back
Top Bottom