Topping DX5 II

[Mario1969]

Yes, I tried turning the switch off and on again, and the memory worked.

It seems different for me. I'm using the default settings.

Example: Would you try turning off the EQ?

This patch saved the EQ to the memory, but it might not be saving the volume.

Did the engineer focus so much on the EQ that they forgot to patch the volume saver? ^^

Anyway, it seems like there's a problem with the EQ or something. I think it would be best to send the video to Topping.

It doesn't matter if the EQ is on or off. I wrote this to warn that such a situation can happen.... I reported the problem to TOPPING! It's a software issue

 

[RHO]

some of you don't understand the problem.... at the beginning I wrote the rear switch....!!!!

It says 0dB, but is it actually able to output any sound at this point? You stop the video right after it shows 0dB. But you say that it attenuates to the correct value (-37dB in your case) later.
At what point is the device capable of outputting sound? When it's still at 0dB or when it's back at -37dB again.
My SMSL doesn't output any sound before it has run trough the whole start-up. I would expect it to be the same on the Topping. In that case it doesn't matter what number there is in the display. If the outputs are only switched on AFTER the volume is corrected to -37dB I wouldn't worry about it one little bit.
If the outputs are switched on BEFORE the volume is corrected to -37dB there is an issue in the startup procedure and Topping needs to correct it.
Can you make a video where audio is playing from the source while you are switching on the device. And don't stop the video before the device has corrected the volume to -37dB again. You can attenuate the audio at the source so that it will play at a moderate level even if the DX5 II would output sound at 0dB. Once the level is adjusted to -37dB it will be quite soft.
This would make clear if the startup procedure is programmed in the correct way.

 

[Nicosea]

I am trying to save the following PEQ filters for the HD 660S headphones:

Preamp: -6.2 dB
Filter 1: ON LSC Fc 105 Hz Gain 6.2 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.7 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2.3 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1.3 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.6 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1.1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1.1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1.3 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1.4 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain -0.2 dB Q 0.7

But when I save it and check again, on the DAC all gains are rounded up or down, in step of 0.5 db, like below:

Preamp: -6 dB (instead of -6.2dB, etc.)
Filter 1: ON LSC Fc 105 Hz Gain 6 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.5 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.5 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain 0 dB Q 0.7

I have hardware version 0.15 and the latest firmware, version 1.69 (I had the same problem with earlier firmwares as well).

 

[jodrim]

I am trying to save the following PEQ filters for the HD 660S headphones:

Preamp: -6.2 dB
Filter 1: ON LSC Fc 105 Hz Gain 6.2 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.7 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2.3 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1.3 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.6 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1.1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1.1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1.3 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1.4 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain -0.2 dB Q 0.7

But when I save it and check again, on the DAC all gains are rounded up or down, in step of 0.5 db, like below:

Preamp: -6 dB (instead of -6.2dB, etc.)
Filter 1: ON LSC Fc 105 Hz Gain 6 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.5 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.5 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain 0 dB Q 0.7

I have hardware version 0.15 and the latest firmware, version 1.69 (I had the same problem with earlier firmwares as well).

Yeah apparently it's normal behavior for the device and always rounds down the dB value to the closest 0.5 dB. Even if it says 6.2 dB in Topping Tune for example it uses 6 dB at least when I measured the output.

 

[Berwhale]

I am trying to save the following PEQ filters for the HD 660S headphones:

Preamp: -6.2 dB
Filter 1: ON LSC Fc 105 Hz Gain 6.2 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.7 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2.3 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1.3 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.6 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1.1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1.1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1.3 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1.4 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain -0.2 dB Q 0.7

But when I save it and check again, on the DAC all gains are rounded up or down, in step of 0.5 db, like below:

Preamp: -6 dB (instead of -6.2dB, etc.)
Filter 1: ON LSC Fc 105 Hz Gain 6 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.5 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.5 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain 0 dB Q 0.7

I have hardware version 0.15 and the latest firmware, version 1.69 (I had the same problem with earlier firmwares as well).

Mine has always done that...

Post in thread 'Topping DX5II Balanced DAC and Headphone Amp Review'

Aug 25, 2025

Firmware V1.62 was just released: https://www.toppingaudio.com/download/dx5-ii-version-v1-62-firmware-update

Awesome! I was getting DC abnormal dropouts playing Portal 2 with my son yesterday!

After upgrade...

Not so awesome! The DX5 II looses all it's settings after the flash to 1.62 Fortunately, I knew all the old settings by heart and had my PEQ stored in Topping Tune.

I hope this FW fixes my PEQ memory issue!

*Update*

I'm beginning to wonder if Topping Tune is the problem, rather than the DX5 II. I have the PEQ for my iLoud MTMs (calculated in...

• Berwhale

• 

 

[Nicosea]

Yeah apparently it's normal behavior for the device and always rounds down the dB value to the closest 0.5 dB. Even if it says 6.2 dB in Topping Tune for example it uses 6 dB at least when I measured the output.

That is really a shame...
Well, I will continue using CamillaDSP on my Raspberry Pi 4 for PEQ.

 

[Minato]

Your DX5 trivia for today is that the display actually doesn’t turn off. Just the backlight turns off.

I was cleaning the smudges off the display and shined my phone flashlight at the panel and realized it was displaying my current settings and volume level. If you turn the switch at the back off it turns the display off as you’d normally expect.

I tried it with the iPhone flashlight and can confirm: the display always stays on, only the backlight turns off!
It's nonsense. This is one of the reasons why it consumes so much power on standby. I don't understand Topping's logic in keeping the display on all the time. Maybe it's yet another firmware bug, as usual...

 

[Minato]

My DX5 ii came with firmware v1.67, and so far I haven’t had any issues with it. I’m really reluctant to update it lol, and might just leave it at the current version.

It's always recommended not to update if you are not experiencing any problems. Especially when the change log does not even mention what has been corrected (->V1.69) and there is always the risk that something will be broken.

 

[Mario1969]

I'm wondering if I can go back to version 1.66 after updating to 1.69 ????

 

[JIW]

It doesn't matter if the EQ is on or off. I wrote this to warn that such a situation can happen.... I reported the problem to TOPPING! It's a software issue

Does it also do it with Line out mode being Preamp? For me it only does it when that is set to DAC.

 

[JIW]

I'm wondering if I can go back to version 1.66 after updating to 1.69 ????

Yes. If you no longer have the files, go to the download link and change 1.69 to 1.66.

 

[Mario1969]

Yes. If you no longer have the files, go to the download link and change 1.69 to 1.66.

I just did it, and everything works fine again...

 

[Sensation]

I just did it, and everything works fine again...

It's strange. Everything works fine after the 1.69 update. Why is this happening? Does it vary by device? I received DX5LL 7 days ago.

I'm silver ^^;; Topping's firmware is very confusing.

 

[jmdesignz2]

It's strange. Everything works fine after the 1.69 update. Why is this happening? Does it vary by device? I received DX5LL 7 days ago.

I'm silver ^^;; Topping's firmware is very confusing.

maybe we should start putting last 4 digits of serial numbers along with the issues?
Mine is on FW1.67, that fixed my issue with retaining last input used ( it would always switch to COAX which is not even connected to anything LOL)

 

[Timbo2]

I tried it with the iPhone flashlight and can confirm: the display always stays on, only the backlight turns off!
It's nonsense. This is one of the reasons why it consumes so much power on standby. I don't understand Topping's logic in keeping the display on all the time. Maybe it's yet another firmware bug, as usual...

It's only milliamps to energize LCDs with no backlight, but it is rather odd.

 

[JIW]

It's strange. Everything works fine after the 1.69 update. Why is this happening? Does it vary by device? I received DX5LL 7 days ago.

I'm silver ^^;; Topping's firmware is very confusing.

Do you use it in Preamp or DAC mode?

 

[Minato]

It's only milliamps to energize LCDs with no backlight, but it is rather odd.

The LCD is connected to the MCU, which remains on at all times since the display is always on. It's simply crazy!
I really wonder what turns off.

 

[chill]

Stopped working today
It was running FW v1.67.
Symptoms: black screen, not recognized message by Windows via USB.
DFU mode does not appear after powering on with the knob hold.
Really frustrated, as it's only been two weeks since I bought it.
Is there any way to perform a hard reset?

 

[jmdesignz2]

It's only milliamps to energize LCDs with no backlight, but it is rather odd.

Don't think it is a bug, just what they decided to do to reduce lag time on start up / restart

 

[ziggurcat]

I am trying to save the following PEQ filters for the HD 660S headphones:

Preamp: -6.2 dB
Filter 1: ON LSC Fc 105 Hz Gain 6.2 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.7 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2.3 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1.3 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.6 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1.1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1.1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1.3 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1.4 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain -0.2 dB Q 0.7

But when I save it and check again, on the DAC all gains are rounded up or down, in step of 0.5 db, like below:

Preamp: -6 dB (instead of -6.2dB, etc.)
Filter 1: ON LSC Fc 105 Hz Gain 6 dB Q 0.7
Filter 2: ON PK Fc 44 Hz Gain 0.5 dB Q 3.59
Filter 3: ON PK Fc 138 Hz Gain -2 dB Q 0.58
Filter 4: ON PK Fc 1383 Hz Gain -1 dB Q 1.3
Filter 5: ON PK Fc 4766 Hz Gain 5.5 dB Q 2.41
Filter 6: ON PK Fc 3184 Hz Gain -1 dB Q 3.71
Filter 7: ON PK Fc 4465 Hz Gain 1 dB Q 5.9
Filter 8: ON PK Fc 5193 Hz Gain -1 dB Q 6
Filter 9: ON PK Fc 6416 Hz Gain 1 dB Q 4.98
Filter 10: ON HSC Fc 10000 Hz Gain 0 dB Q 0.7

I have hardware version 0.15 and the latest firmware, version 1.69 (I had the same problem with earlier firmwares as well).

Topping Tune has always done that. It's not the DX5 II, so it won't matter what FW version you're on. It has to be resolved with a separate Topping Tune update, and I have a feeling they won't fix that.