Support for per-channel (L/R) ParametricEQ.txt import? #441
VacTuzX-dot
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi! First off, thanks for FineTune — it's become part of my daily setup.
Question / Request: Does FineTune support importing a ParametricEQ.txt
that contains separate
Channel: LandChannel: Rsections?My headphones have a noticeable channel imbalance, so my measurement tool
exports an asymmetric EQ like this:
What I've observed: When I import this, it looks like the
Channel:lines are ignored and the filters get flattened into a single 10-band EQ
applied to both channels — so the L/R difference is lost.
What I'd love to see:
Channel: L/Channel: Rblocks into two independent filter chainsfor existing users), and when unlinked, separate tabs/columns for each channel
Why it matters: Channel imbalance is really common on both headphones and
speakers (room asymmetry, driver aging, etc.). Right now the only way to fix it
on macOS is dropping down to AU Lab / Audio Hijack, which is a lot heavier than
just using FineTune.
If per-channel EQ isn't on the roadmap, would it at least be possible to show a
warning on import when a file contains
Channel:directives, so users know theasymmetry is being discarded? That alone would prevent silent misconfiguration.
Happy to test builds. Thanks!
All reactions