Topping DX5 II

[ziggurcat]

well, seems like I'm buying one then lol

thanks a lot.

They've removed the latest FW update because it was apparently bricking people's units. It probably won't be too long before they put it back up on the website, though.

 

[cmld]

They've removed the latest FW update because it was apparently bricking people's units. It probably won't be too long before they put it back up on the website, though.

They’ve removed all versions, so it’s more likely an issue with the update process itself rather than with a specific version.

 

[Berwhale]

They’ve removed all versions, so it’s more likely an issue with the update process itself rather than with a specific version.

It's also possible that they don't want people who had a problem with 1.62 trying to flash earlier versions and making things worse.

 

[cmld]

v1.62: Occasionally, after turning on the device, the message 'BT version abnormal' appears. I have to turn the device off and on again to get rid of it. Bluetooth is disabled in the settings.

 

[Timbo2]

v1.62: Occasionally, after turning on the device, the message 'BT version abnormal' appears. I have to turn the device off and on again to get rid of it. Bluetooth is disabled in the settings.

View attachment 473290

I’ve not gotten that message, but I have had to hard power cycle it to get Bluetooth to properly connect to my Nvidia Shield TV.

Bonus trivia the latency on the preferred highest quality LDAC codec is 150ms. That’s about 90ms more than AptX HD that I was using before. It’s easy enough to adjust, but when I switch back to the AVR I need to dig into the settings to change it.

 

[Berwhale]

v1.62: Occasionally, after turning on the device, the message 'BT version abnormal' appears. I have to turn the device off and on again to get rid of it. Bluetooth is disabled in the settings.

View attachment 473290

I had this message after installing 1.62, turning BT off and having only USB input enabled. I turned BT back on and i've not seen the message since.

Note that I only have USB enabled as an input in the 'Input Option' menu. So, even though BT is enabled in the 'Input Settings' menu, I can't select it as an input on the DX5 II and the DX5 II doesn't appear as a BT device on my phone. So it appears that the disabling BT in the 'Input Option' menu trumps having it enabled in the 'Input Settings' menu does actually turn BT off (and also removes the 'BT version abnormal' message.

 

[ziggurcat]

v1.62: Occasionally, after turning on the device, the message 'BT version abnormal' appears. I have to turn the device off and on again to get rid of it. Bluetooth is disabled in the settings.

View attachment 473290

I can't say I have ever seen that, not even after updating to v1.62. I also don't turn the device off, I let it go to sleep/go into standby mode on its own.

The only weird thing with the updates has been that even though I correctly "ejected" the DX5 II after the update was finished, and I powered the device off/on again to complete the process, I got a pop up on my Mac that said that it hadn't been removed properly. I didn't do that properly when I updated to 1.57 (which had only been released a day or two before I got my unit), so I made sure to eject the device for 1.62, and I still got the message.

I’ve not gotten that message, but I have had to hard power cycle it to get Bluetooth to properly connect to my Nvidia Shield TV.

One of the first things I did was disable BT, and remove it as an input option in the settings. I just enabled, and added it to the input options, and my computer detected it right away without any issues. No BT abnormal message, either.

 

[Bleib]

After this DAC is hopefully fully fixed I'm not going to buy another one in ages

 

[ziggurcat]

After this DAC is hopefully fully fixed I'm not going to buy another one in ages

The only thing that would maybe cause me to buy a new device is if they come out with a new iteration of their MX5 all-in-one so I can further reduce the clutter of wires behind everything. I don't think there are any more proverbial dragons to chase.

 

[boiwotl]

The unit I bought last week was on v1.3, so I updated it to the latest which was v1.62 at the time. Now that firmware version is gone and I'm reading about it bricking units. Everything seems to be fine, except I once got FFT display abnormal when waking it up from standby-mode (I don't remember the exact message). It disappeared after turning the unit on and off again.
Should I revert to v1.57 to be safe or just leave things how they are, considering it already flashed successfully and nothing serious has happened yet? Thanks!

 

[Berwhale]

The unit I bought last week was on v1.3, so I updated it to the latest which was v1.62 at the time. Now that firmware version is gone and I'm reading about it bricking units. Everything seems to be fine, except I once got FFT display abnormal when waking it up from standby-mode (I don't remember the exact message). It disappeared after turning the unit on and off again.
Should I revert to v1.57 to be safe or just leave things how they are, considering it already flashed successfully and nothing serious has happened yet? Thanks!

Welcome ASR! I think you should leave your unit on 1.62, as I am, until we know more about the issues that caused Topping to pull the firmware.

 

[boiwotl]

Welcome ASR! I think you should leave your unit on 1.62, as I am, until we know more about the issues that caused Topping to pull the firmware.

Thanks for the greeting and advice! I emailed topping asking a similar question about being on 1.62 and whether I should revert and have now received this response:

It is recommended that you use the 1.57 version of the firmware. We are now updating the new firmware to solve these problems. It will be available for download in a few days.

Kind of interesting, intuitively I stay away from firmware updates unless something is broken, at least with computers. Only reasons I can think of is 1.57 -> new firmware is somehow a safer process or being on 1.62 is itself a potential risk (seems unlikely). My guess is probably doesn't matter too much, I just hope there aren't issues upgrading from 1.62 to whatever new version there is.

 

[Timbo2]

https://dl.topping.audio/usermanual/DX5_II_FW1.66.zip

6. What's updated​

• Fixed: System crash caused by switching C1/C2.

• Fixed: The problem that the Bluetooth version is misjudged with a certain probability, resulting in the device failing to boot up normally.

• Fixed: an issue that the transient being cut off when going from zero output to large signal.

• Fixed: Several other known issues.

 

[Berwhale]

https://dl.topping.audio/usermanual/DX5_II_FW1.66.zip

6. What's updated​

• Fixed: System crash caused by switching C1/C2.

• Fixed: The problem that the Bluetooth version is misjudged with a certain probability, resulting in the device failing to boot up normally.

• Fixed: an issue that the transient being cut off when going from zero output to large signal.

• Fixed: Several other known issues.

Thanks, the update to Toppings download page was picked up by both VisualPing and Distil chrome add-ins, but I was too busy with my day job to notice!

I've installed 1.66 with no issues, although it does wipe all your settings. The PEQ memory appears to be working more consistently in Topping.Tune, so i'm hopeful my issues with settings being lost may be resolved.

 

[Musictech77]

Where can I find some instructions that are missing from the manual? For example:
-connecting with bluetooth
-procedure for using topping tune and loadimg the settings in the unit
-all the firmware updates new functions amd changes.

I tried the various filters and I liked most f4, f8. Is found also f3 the most suitable for a smoother sound.

 

[Timbo2]

Where can I find some instructions that are missing from the manual? For example:
-connecting with bluetooth
-procedure for using topping tune and loadimg the settings in the unit
-all the firmware updates new functions amd changes.

I tried the various filters and I liked most f4, f8. Is found also f3 the most suitable for a smoother sound.

Topping Tune has its own manual.

https://dl.topping.audio/um/TOPPING_Tune_V1.3.pdf

From memory on Bluetooth the pairing was all done on the source device side. So the instructions depend on how that device pairs devices.

 

[malaire]

Bluetooth pairing is very simple with DX5II. There is no pairing mode, pin or passcode. DX5II is always ready for pairing (as long as bluetooth is ON) and you just do pairing from source device and that's it.

As for firmware updates, I think the only thing missing from manual is description of the added SPDIF mode which is: 1 (default, high-performance mode); 2 (high-compatibility mode)

 

[Yersinia Bestmate]

They've removed the latest FW update because it was apparently bricking people's units. It probably won't be too long before they put it back up on the website, though.

...and then pull it again. Hopefully not though.

 

[ziggurcat]

Thanks, the update to Toppings download page was picked up by both VisualPing and Distil chrome add-ins, but I was too busy with my day job to notice!

I've installed 1.66 with no issues, although it does wipe all your settings. The PEQ memory appears to be working more consistently in Topping.Tune, so i'm hopeful my issues with settings being lost may be resolved.

I really hope this update works better for you. Good to hear that there's been no issues so far.

 

[boiwotl]

Thanks, the update to Toppings download page was picked up by both VisualPing and Distil chrome add-ins, but I was too busy with my day job to notice!

I've installed 1.66 with no issues, although it does wipe all your settings. The PEQ memory appears to be working more consistently in Topping.Tune, so i'm hopeful my issues with settings being lost may be resolved.

Thank you for testing it out. I have updated to 1.66 now and also no issues other than settings being wiped.