[Beta Testing] Seeking Audiophile Feedback for New System-Wide Android DSP Engine

[Chrispy]

Great question! AudioMatch adjusts for playback volume with its Equal-Loudness Compensation feature.

Human hearing naturally loses sensitivity to bass and treble as sound gets quieter — that's why music sounds "thin" or flat at low volume. Equal-Loudness counteracts this automatically:

• The app continuously tracks your device's media volume, so it reacts instantly when you use the volume keys.
• You set an anchor volume (default 75%) — the level where the sound is considered "correct." At or above the anchor, no compensation is applied.
• As you turn the volume down below the anchor, the app progressively boosts the bass (centered around 100 Hz, up to a limit you choose, 7 dB by default) and the treble (around 4.5 kHz, up to 3.5 dB). The quieter you listen, the more it compensates, so the tonal balance you hear stays the same at any volume.
• You can also adjust the overall strength (0–200%) to make the effect subtler or stronger, and all changes are ramped smoothly so nothing jumps audibly when you change volume.

And don't worry about the added boost causing distortion — AudioMatch's auto-headroom and brickwall limiter sit at the end of the chain and guarantee the output never clips, even at higher volumes with heavy boosts.

You'll find it under Effects → Equal Loudness (it's a Premium feature).

Nice non-answer.

 

[Zinda]

My post was deleted by me , I didn't realize which site this was posted on !

 

[Zinda]

Nice non-answer.

Kinda sounds like the presence will be distorted (in a reality sense, but not in THD) since purposely recorded quieter portions will be louder than intended and quiet passages will be brick walled and stopped from reaching intended output levels. This is key in reproducing realistic sound.

I'm sure people that are into AV systems know all too well what -00db means to recorded play back and how important it is to form the most realistic output as possible that mimics real life "being there" even if the sound is not perfect, it's the impact and sudden changes of real sounds that makes the sound part of what matches on screen and puts you directly in the action.

 

[Chrispy]

Kinda sounds like the presence will be distorted (in a reality sense, but not in THD) since purposely recorded quieter portions will be louder than intended and quiet passages will be brick walled and stopped from reaching intended output levels. This is key in reproducing realistic sound.

I'm sure people that are into AV systems know all too well what -00db means to recorded play back and how important it is to form the most realistic output as possible that mimics real life "being there" even if the sound is not perfect, it's the impact and sudden changes of real sounds that makes the sound part of what matches on screen and puts you directly in the action.

Not sure what your post is saying either.

 

[Adamant11746]

Thanks for the new code, I was finally able to test the full PEQ. However, there is a massive difference between Audiomatch and my PC. I can't tell you exactly what's wrong, but it likely spans the entire frequency range. I think you really need to find a way to measure the output and compare it to the expected result. The UI is decent, and the device detection works well, but the EQ is the main feature and it just isn't ready.

I have given up on this app. In addition to the problems I found, the developer seems to have stopped posting completely once the problems were pointed out. I ended up just spending the money on a Qudelix 5k because at least that's proven to work.