juzio
Member
Well said. I'm in the same position as you.
-
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
- Thread starter Matias
- Start date
ziggurcat
Major Contributor
It might be fine if you never launch the Home web app, but you may also run into what @juzio encountered (though they didn't say which version of Windows they run on their computer?). Unfortunately, I think the only way to really know is to have a back up of your PEQ files, and launch Topping Tune. Last time I launched Topping Tune after checking out the web app, I lost all of my PEQ profiles, and ran into a weird issue where -- despite there being no PEQ profiles listed in Topping Tune or the web app -- my DX5 II itself showed 5 DevConfig profiles, and I had to do a factory reset to fix the problem.
juzio
Member
I'm using windows Server 2025 as as my main operating system and before I upgrade DX5 II to the latest version of driver, Firmware and Topping tune - all was working fine. Now topping Tune showing that Device is not connected.
juzio
Member
Managed to recognize DX5 II by Topping Tune. First I uninstalled from my system everything pointing to DX5 II, (driver and Topping Tune). at that point Device manager was showing only default Microsoft driver for DX5 II. Next I Start installing latest version of Topping Tune, during installation I was ask if I want to install a Driver for the device I skip that Driver installation. Next I did factory reset. At this point DX5 II was recognize by Topping Tune, but switching between PEQ is sketchy. I loaded couple PEQ filters but not every one can be switched ON.
I think Topping have taken a great responsibility. Issuing a firmware version that not only breaks what was their standard maintenance tool but to add insult to injury making it impossible to rollback to a previous version. I wanted to buy a second one for my main audio set the moment the problems were ironed out. But I fear my DX5 II will have to stay on firmware 1.93 with a reduced functionality that actually does perfectly what I expected from the device. When I buy a second one it will be on the 2.xx firmware generation, so I hope Topping makes amends, otherwise I will have to look for something different for the other audioset.
Would it be an idea to create a sticky post that just contains the issue list and the progress of the developments. I really did hope that Topping would concentrate on fixing the issues in stead of adding untested new functionality.
BTW. I also don't want any of my devices to be totally dependent on external services. Certainly not when they act as a simple filter in my audio chain.
Last edited:
My assumption is that Topping didn’t intentionally make this firmware no longer able to revert to earlier versions.
Since I’m already working with them trying to fix my Shield issues, does somebody else who is unhappy with the recent firmware’s bugs want to reach out to Topping support and complain? At the very least Topping should note in the firmware change log that you can’t revert (assume this was intentional).
juzio
Member
Already sent e-mail to the support team.
Do they monitor this forum ?
Usually only the reviews and only for a while.
They are good at responding to support although usually it takes 48 hours or so.
I certainly didn't suggest that Topping is shipping subpar software on purpose.
Worldwide trade of industrial goods is possible only in the case of a worldwide support network or when only perfectly functioning hard and software is shipped.
When I look around I see that an audio device is supposed to function for 15 years at least.
I think Topping does ship software with known bugs. However, they aren't unique. That's the new world of "minimal viable product" we live in. It's also the world Topping has to compete in. I wish consumers demanded more, but they don't and are willing to accept this.
In the case here with the inability to revert back to earlier versions firmware - I don't think Topping knew about this before they released this firmware.
somebodyelse
Master Contributor
- Joined
- Dec 5, 2018
- Messages
- 7,047
- Likes
- 7,044
On the bright side, at least with it using a browser you can probably see exactly how it works, and/or host it on your own machine.
Explain how I could host a site that I don't have.
I am quite content with an executable load module, nowadays called an app, like Topping Tune.
somebodyelse
Master Contributor
- Joined
- Dec 5, 2018
- Messages
- 7,047
- Likes
- 7,044
Assuming everything is running entirely in the browser (not certain, but a fair chance, at least for the core functionality) all the necessary files are available. You download them and host them in the same paths on your own server. It may be necessary to make some changes. If it's not something you're familiar with then it's probably best to wait for someone who has the necessary skill to document the process for this instance. I'm suggesting it as a possibility to keep things working should Topping stop hosting it at some point. Better yet Topping could include a manifest file so your browser can keep a local instance for offline use - they don't at the moment. Having the javascript code also makes it easier for people to write a 3rd party control app - not quite as good as API documentation but the next best thing. That's another route to keeping control working should Topping decide not to support it any more at some point in the future.
I don't think you can download a dynamic web app by saving the web page and you won't have access to the code behind the website to host this yourself.
Well you can have static websites that implement all their functionality via client side calls. My devicePEQ codebase is ultimately a static set of JS files that interacts with devices connected to the users PC/MAC via the USB-c (or bluetooth or network) connections.
FYI: I am adding support for this Topping (and the 2 other Toppings that I have with PEQ - even though each one has a very different implementation ) but that will be a few weeks away.
ziggurcat
Major Contributor
I don't think they monitor this thread at all, but they are pretty good with responding to any e-mails you send them. It might take a day or two for them to respond, but they do actually respond. I have a months-long thread with them in my inbox for reporting issues.
ziggurcat
Major Contributor
Depending on the platform you're on, I would at least update the FW to v2.39 (that one you can still roll back if you want) because there are actually some pretty nasty issues in v1.93 that have since been fixed.
If you're on MacOS, I can send you any of the FWs via PM.
So is it possible to run Topping.Home locally then?
Hmmm, Gemini Pro thinks it's possible:
TL;DR
- Running a local copy of Topping's web application (home.toppingaudio.com) depends entirely on what you want to achieve, as it functions primarily as a cloud-backed companion app for physical audio hardware rather than a standalone website.
- What you can copy/host locally: You can easily clone or self-host the static frontend interface (HTML/JS/CSS assets) if you inspect the page sources, but it will be a dead shell.
- What you cannot run locally: The core functionality relies on proprietary cloud backends for user accounts, cloud sync, community PEQ (Parametric Equalizer) presets, and direct hardware communication via browser APIs.
Feasibility Analysis
- Frontend (User Interface):
The app is a standard single-page web application (running web v1.10.0 as per their footer). You can scrape or save the static frontend assets and serve them via a local web server (like Nginx, Apache, or Python's http.server). - Hardware Communication (WebHID):
The site uses WebHID (Web Human Interface Device API) to communicate directly with connected Topping DACs/amplifiers through supported browsers like Google Chrome or Microsoft Edge. If you host the frontend locally on localhost or via a local IP, the browser's security model will permit WebHID access, provided your browser has USB/HID permissions for that origin. - Backend & Cloud Services:
Features like user authentication, syncing PEQ presets across devices, community sharing, and firmware update repositories rely on Topping’s proprietary cloud infrastructure and databases. You cannot run a local copy of these backend services because Topping has not open-sourced them.
What Works vs. What Breaks Locally
- Will work locally: The static UI layout, client-side math/logic for PEQ filters, and direct WebHID commands sent straight to a plugged-in Topping device (if the device protocol is entirely client-driven).
- Will break locally: Account logins, syncing settings to the cloud, fetching community Auto-EQ presets, and checking for official firmware upgrades.
With Gemini's help in Antigravity IDE, I ran up a simple local Node.js HTTP server, but the page is static and none of the UI elements work (not that I know what i'm doing
)
Last edited:
juzio
Member
"Thank you for the detailed report. After the firmware upgrade, the DX5 II is now compatible with Web EQ, making it easier and more convenient to set and modify EQ on the web, and it also provides an Auto EQ function."
This is the respond from them for my complain that latest firmware make Topping Tune not working.
