LowCut Audio Toggle von Andreas Fleckl

LowCut applies a gentle 330 Hz low-cut filter to any tab’s audio.
Toggle it on/off from the toolbar to tame boomy bass instantly.

Description
LowCut gives you quick control over your tab’s low end.
Flip the toolbar button to run a 330 Hz low-cut filter across every <audio> and <video> element on the page,
or switch it off to hear the original mix. It uses a single high-pass biquad filter per media element—lightweight,
transparent, and easy on system resources.

What it does
Toolbar toggle: One click enables the filter, one click restores the unprocessed audio.
Automatic coverage: Newly added media is detected via MutationObserver, so the filter stays applied even on dynamic pages.
Fallback support: If Web Audio can’t hook into a media element (e.g. CORS-restricted streams), LowCut requests tab capture as a backup route.

Why you’ll like it
Clean listening: Dial down muddy or rumbly bass instantly—great for podcasts, lectures, or background playlists.
Zero setup: No sliders or advanced UI to learn; the toolbar title clearly shows LowCut: ON/OFF.
Open source: MIT-licensed code, with icons under CC‑BY‑4.0. Source available on request at bubuit.net.

Key Features
High-pass filter at 330 Hz using Web Audio.
State sync across tabs via lightweight messaging in extension/background.js.
Automatic reconnection for new media in extension/content/content.js.
Optional tab-capture fallback to maintain effect even when direct node attachment fails.

How to Use
Install the add-on and look for the LowCut icon in your toolbar.
Click once to enable the low-cut filter on the current tab’s audio. The title updates to LowCut: ON.
Click again to disable and return to the original sound.
Works automatically on any site that allows Web Audio processing.

Permissions
Tabs & activeTab: Needed to send enable/disable messages to pages.
Storage: Persists your ON/OFF preference between sessions.

Support & Source
Author: Andreas Michael Fleckl (https://bubuit.net)
Need help or want to report an issue?
Reach out via the site or open an issue on the project’s repository (include a link when you publish publicly).