New Web Based control app for DACs with PEQ

[JanL]

It's an open source project that looks to be vibe coded using AI, but it works fine on a few my USB DACs like the Black Pearl and Fiio JA11. I find it easier to use than the original manufacturers apps plus there is no need for registration. If your DAC uses WalkPlay it will work with this app as well.
Another cool feature is that you can also install the web app for local use off line.

https://github.com/mandy321/Audiocular-Aura
Live Web App: https://mandy321.github.io/Audiocular-Aura/

 

[JanL]

For those who might have previously downloaded the app for use locally, or had issues connecting to various DACs, the author has made some updates to it. for example It will now work with the Moondrop Dawn Pro 2 whereas the last version didn't. Also, if your DAC connects only after you manually enter the USB VID and PID numbers for it, that info will update the database and that will enable others to connect automatically to the same type of DAC.
See the updated Readme file on GitHub.

 

[Mandy007]

Hello

I am developer of the project
Think of this software like a universal TV remote.

You don't need a name-brand device to access premium hardware-level Parametric EQ. Because this tool communicates via the universal WebHID API and standard USB Audio Class 2 (UAC2) protocols, it bypasses brand restrictions completely.

If your unbranded or cheap dongle uses a compatible DSP chip (such as Savitech CB5100, Comtrue CT7601, or KT02H20), this software can directly read and write to the chip's internal registers. This lets you flash custom AutoEQ profiles and control a full 10-band hardware PEQ directly through your browser—giving your $15 generic dongle the superpowers of a $100+ audio device!

Just plug it in, hit Connect, and see if it unlocks. (Note: The DAC chip itself, like CS43131, doesn't handle EQ – it's the USB bridge/DSP chip that matters.)

 

[somebodyelse]

WebHID is hardly universal - it's not supported by Firefox, Safari, or most mobile browsers. On linux it usually needs changed permissions even with supported browsers - like adding a udev rule. It's about the closest we've got to a cross-platform method though.

 

[Mandy007]

WebHID is hardly universal - it's not supported by Firefox, Safari, or most mobile browsers. On linux it usually needs changed permissions even with supported browsers - like adding a udev rule. It's about the closest we've got to a cross-platform method though.

For Linux Users: Build a "udev Rule Generator" - This can be done. if anyone tried please do reply if it works​

Linux users are often technical and willing to perform a simple terminal command.
lsusb in terminal to find VID and PID

echo 'KERNEL=="hidraw*", SUBSYSTEMS=="usb", ATTRS{idVendor}=="VID", ATTRS{idProduct}=="PID", TAG+="uaccess", MODE="0660", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/99-aura.rules && sudo udevadm control --reload-rules && sudo udevadm trigger

• Replace VID and PID in the rule with the actual hexadecimal values (e.g., 35d8 for VID, 011d for PID – without the 0x prefix).
• Ensure they have sudo rights.
• After running both commands, unplug and re‑plug the DAC for the new rule to take effect.
  

For Firefox Users: Create an Official Firefox Extension - If anyone tried can update if it worked as i don't have windows.​

There is already a community project called "WebHID for Firefox" that bridges the gap.
https://addons.mozilla.org/en-GB/firefox/addon/webhid-for-firefox/
https://github.com/Sainan/WebHID-for-Firefox/releases

WebHID for Firefox​

A WebExtension & server that work together to provide WebHID APIs on Firefox.

Installation​

1. Get the extension on addons.mozilla.org.
2. Download the WebHID-for-Firefox-Server.exe from the latest release.
3. Optionally, if you want the server to start with your PC, move the executable to the %appdata%\Microsoft\Windows\Start Menu\Programs\Start-up folder.
4. Double-click the executable to start the server.
   • Note that the server is designed to run in the background, so it will not do anything noticable once started. If you want to be sure it's running, you can check the task manager.

For Safari​

​

 

[somebodyelse]

That udev rule seems to be mixing approaches - the uaccess tag adds user access, so doesn't need the mode and group which were commonly used before the uaccess tag existed. Also the 'plugdev' group doesn't exist on all distros, so if users need to check what group works on their distro if going the mode/group route.

Also you shouldn't need to unplug and replug the DAC on linux if following those instructions - the 'sudo udevadm trigger' should have the same effect. The problem with running it without extra filters is that it will retrigger all the other udev rules again too, which may have unintended consequences depending on what other stuff you have. You should probably use the --attr-match option to include idVendor and idProduct so you only trigger the rule you just added, or just not run 'udevadm trigger' at all and stick to unplugging/replugging.

Assuming linux users are technical and know what they're doing is probably less safe recently than it has ever been, given the numbers of people trying linux because their hardware isn't officially supported by Win11.

Those variations, and needing to install a plugin and server to make it work in Firefox, underline the lack of universality. Then there's the mobile browser compatibility issue:
https://caniuse.com/webhid

Please don't take this as a criticism of your work - as I said WebHID is probably the closest we have to a cross-platform method. I just want people to understand the limitations to where it can be used. It's a similar situation to using WebSerial for ESP32 stuff, or Web Bluetooth. The reason other browsers don't support it is the same too - they consider it an unacceptable security risk, much like linux not granting that level of device access to users by default, hence needing a udev rule or similar to do it.

 

[Mandy007]

That udev rule seems to be mixing approaches - the uaccess tag adds user access, so doesn't need the mode and group which were commonly used before the uaccess tag existed. Also the 'plugdev' group doesn't exist on all distros, so if users need to check what group works on their distro if going the mode/group route.

Also you shouldn't need to unplug and replug the DAC on linux if following those instructions - the 'sudo udevadm trigger' should have the same effect. The problem with running it without extra filters is that it will retrigger all the other udev rules again too, which may have unintended consequences depending on what other stuff you have. You should probably use the --attr-match option to include idVendor and idProduct so you only trigger the rule you just added, or just not run 'udevadm trigger' at all and stick to unplugging/replugging.

Assuming linux users are technical and know what they're doing is probably less safe recently than it has ever been, given the numbers of people trying linux because their hardware isn't officially supported by Win11.

Those variations, and needing to install a plugin and server to make it work in Firefox, underline the lack of universality. Then there's the mobile browser compatibility issue:
https://caniuse.com/webhid

Please don't take this as a criticism of your work - as I said WebHID is probably the closest we have to a cross-platform method. I just want people to understand the limitations to where it can be used. It's a similar situation to using WebSerial for ESP32 stuff, or Web Bluetooth. The reason other browsers don't support it is the same too - they consider it an unacceptable security risk, much like linux not granting that level of device access to users by default, hence needing a udev rule or similar to do it.

WebHID isn't universal, and I acknowledge that. For now, that's the best we have.

 

[ICIETDIYEUR]

EQ Hangout.Audio par Crinacle -> https://eq.hangout.audio/

 

[john61ct]

Does this allow for batch uploading IIR biquads from REW, MSO etc?

I really like the idea of "as anechoic as possible" speaker corrections embedded in a cheap DAC right at the power amp driving it

separate from crossovers timing stuff, DRC

"Modularised DSP ™ "

 

[Deckard01]

Can we add more than 10 eq bands? Thanks

 

[JanL]

Can we add more than 10 eq bands? Thanks

No. Hardware limitation. 10 bands is the most for portable DACs so far. Many DACs have even less DSP horsepower. Maybe in the future there will be some DACs that can load Impulse Responses, which would be equivalent to a much higher number of bands, but less flexible for the user.

 

[john61ct]

Maybe in the future there will be some DACs that can load Impulse Responses

Impulse Responses has to do with convolving, FIR filters only, correct?

Could you please answer my question about importing IIR / PEQ coefficients? A lot could get done in 10 bands, but manually duplicating them over and over while testing gets very tedious.

The same text file format miniDSP accepts is probably a universal enough standard.

Note that I am asking @JanL specifically, but if someone else has the answer, that would be fine

 

[ICIETDIYEUR]

https://eq.hangout.audio/

have a test, you will get your answer

 

[john61ct]

https://eq.hangout.audio/

have a test, you will get your answer

I have no idea what this is about, please ELI5

 

[ICIETDIYEUR]

New Web Based control app for DACs with PEQ.

 

[john61ct]

I was asking specifically about Audiocular-Aura software.

I thought you were trying to answer my question sorry crossed wires!

But now I am asking, why do you mention this eq.hangout.audio website?

Does that have any relation to Audiocular-Aura?

I can't tell what one has to do with the other.

I am asking you to use more words.