• 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

TOPPING TUNE

1111.jpg
 
Who wants to see what breaks now?
I'm running the new version. It seems to work a little better than the previous version, but it still 'forgets' the custom PEQ i've copied to the DX5 II after I power cycle the DX5 II (the custom PEQs are still on the DX5 II and it still switches between them when I change output).
 
I'm running the new version. It seems to work a little better than the previous version, but it still 'forgets' the custom PEQ i've copied to the DX5 II after I power cycle the DX5 II (the custom PEQs are still on the DX5 II and it still switches between them when I change output).
Thanks!
 
1763485037915.png


Whoever thought that automatic update checker that you cannot disable, that still runs even if you block the app from connecting to the internet needs to be shot.
 
Not available on macOS yet.

One issue I’ve encountered is with the Gain setting. When I use my Meze Alba in SE mode, I’ve set the gain to Low. Everything works as intended. However, when I switch to Balance mode and listen with the Sundara, the Gain is set to High ( I've got the GAIN written under dB on the LCD screen), but it’s not actually High. I have to manually adjust the gain again to set it properly. Do you experience the same problem?
 
Last edited:
I’m considering the DX5 ll along with Ollo X1 headphones, which come with a calibration file. What increments can the PEQ be cut/boosted on the Topping please?
 
I’m considering the DX5 ll along with Ollo X1 headphones, which come with a calibration file. What increments can the PEQ be cut/boosted on the Topping please?
I hope 0.1 dB will be available soon, right now it’s bugged, so for the moment I’m using 0.5 dB with Fw 1.72
 
I’m considering the DX5 ll along with Ollo X1 headphones, which come with a calibration file. What increments can the PEQ be cut/boosted on the Topping please?
Works fine for me with 0.1 increments. I am on the latest firmware
 
The newest Topping Tune is much HEAVIER than the previous versions, it looks like most of the bugs have been fixed...
but there is one bug they haven't fixed yet.



tune.jpg
tune.jpg

and it's constantly doing something..... I wonder if it's sending any data to CHINA?
 
Last edited:
1.78? Doesn’t it mess up all the values by ±20 when you turn it off and then back on? What hardware version do you have? You can see it in Topping Tune
Yes,1.78. According to release notes, then 0.1 adjustments were fixed in 1.73, and the DB boost in 1.76.

My case is different from some others, that topping tune has been in an inactive VM since I decided on final PEQ settings. In other words no interaction with the DAC from TT.

I experienced the DB boost before upgrading firmware.
 
Hi! As of today, when using macOS, can I just store a EQ profile on headphone out and one for the XLR out? Or is this what is referred here as "forgotten" on power cycles?
 
Hi! As of today, when using macOS, can I just store a EQ profile on headphone out and one for the XLR out? Or is this what is referred here as "forgotten" on power cycles?
Assigning PEQs configs to outputs is the 'PEQ Memory' feature. I don't recall anyone ever having a problem with this feature.

The 'loss' of PEQ configs refers to what the the Topping Tune application reports as present on the DX5 II. If I power cycle my DX5 II (with the rear power switch), Topping Tune will report that the 5 default device PEQ configurations are on the DX5 II and not any custom PEQs input directly or copied from the Local PEQ configs. It shows the 5 default configs, even if I deleted them before the power cycle.
 
The newest Topping Tune is much HEAVIER than the previous versions, it looks like most of the bugs have been fixed...
but there is one bug they haven't fixed yet.



View attachment 491623View attachment 491625
and it's constantly doing something..... I wonder if it's sending any data to CHINA?
I wonder if this version has been released with debugging enabled (which would usually be a mistake, rather than something nefarious). I see the same jump for the versions of Setup that I kept...

1763579351538.png


FWIW - I have submitted the screen grab above to Topping and asked if the 5x increase in size is expected.
 
OTOH, "telemetry" to know where exactly the fault lies can be a good thing
 
Maybe there it's just taken for granted... :)
 
Back
Top Bottom