Audio Equalizer and Amplifier An easy-to-use web audio equalizer and amplifier
Support Development
PayPal ● 
Bitcoin Address: 1sM2BrTH8BRgt3quiASK8TmYSafutNvDo
 ● 
Ether Address: 0xCf9eaAc56992e12EB61fD46342172d4EEff5C8e4

Advertisement
Screenshot
"Audio Equalizer and Amplifier" extension adds a toolbar button to your browser which controls the output of all media elements that are responsible for generating sound. There are basically four sections in the toolbar popup area of this extension. You can enable and disable the audio equalization on the top section. In the middle section, there are two subsections. One for pre-amplification and one for per-frequency amplification which is known as audio equalization. In the bottom section, audio profiles can be managed. You can have as many audio profiles as you like and you can switch between profiles easily. There are two extra buttons in this area to add new profiles and to delete the currently active profile. All profiles except the default one are removable. Each profile stores pre-amplification level and all per-frequency amplification levels. Note that the pre-amplification can be used to increase the volume of the media element even more than what the element is offering (this is similar to the volume control on each player but acks globally for all tabs). The enabling state dictates whether the controlling script is being injected to the browser tabs or not. When the extension is disabled, the controlling script is not being injected at all. This means that there is no control over media elements at all. If you enable the extension after a tab is loaded, you will need to refresh the tab for the extension to be able to control the media elements. This method is implemented to make the extension completely inactive when it is disabled from the toolbar popup (whereas other similar addons, no resource is used what so ever in this state).

Features

  1. What is the "Audio Equalizer and Amplifier" extension and how does it work?

    This extension is used to have control over audio playing of your browser. It can control the volume level as well as per-frequency amplification levels. The extension offers presets for "Classical", "Club", "Custom", "Default", "Live", "Laptop Speakers/Headphone", "Rock", "Pop", "Full Bass and Treble", "Full Bass", "Full Treble", "Soft", "Party", "Ska", "Soft Rock", "Large Hall", "Reggae", "Techno" categories. The "Default" leveling can be used to only control volume since there is no amplification per frequency range. There is a "Custom" level that basically stores what levels the user adjust in the UI. These levels are persistent per user profile. If you need to have multiple custom levels use profiling section to create different profiles. Currently, the extension supports adjusting levels for 60, 170, 310, 600, 1K, 3K, 6K, 12K, 14K, 16K frequency ranges which is equal to what VLC media player offers.

  2. I am a heavy YouTube user and I need to only control YouTube's player. Is it possible to limit the controller to YouTube?

    There is an exact same extension which is only limited to YouTube. Basically when the extension is enabled from the toolbar area, it only injects the controlling script into the YouTube and YouTube Music pages. This way only YouTube player is controllable. If you are only interested in YouTube player, use this extension instead. Note that these add-ons are conflicting with each other. You can only have one installed.

  3. What's new in this version?

    Please check the Logs section.

  4. Can I have multiple user-defined leveling for frequency bands?

    Yes, there is an "Add" button next to the profile selection. Use that button to duplicate the current profile in a new name. Note that the name of each profile needs to be unique. Now adjust the levels manually or from the default presets. You can also adjust the volume level for each profile as well. There is no save button. The extension stores your settings when there is a change in the configuration. When a profile is changed, if the extension is enabled, the changes will be applied to the active players.

  5. What is the difference between keeping the extension enabled when the "Default" profile (falt one) selected and disabling the extension from the popup?

    When the extension is disabled from the toolbar popup, the extension will not monitor web navigation anymore. It means that the controlling script is not being injected to the browser tabs or in other words there is no control over the audio playing. However, when the extension is enabled and the default profile is selected, the script is being injected to all tabs while it practically does nothing. This is useful to control the volume level (pre-amplification level) only. Note that if for instance the extension is in the disabled mode, and you want to change the volume, you will have to first enable the extension from the popup and then refresh the tab to allow the controlling script to be injected first.

  6. Should I keep the extension disabled from the popup when I am not using it or keep it enabled and use the default flat profile?

    It really depends on your usage. If you don't mind refreshing the active tab for the changes to be applied, it is recommended to disable the extension from the toolbar area. This way the extension is not monitoring your web navigation at all and hence does not use any resource since it uses a non-persistent background script. However, if you prefer to be able to control the volume while the player is playing without the need to refresh the tab, you need to keep the extension enabled and to prevent audio equalization, use the flat profile (the default profile).

  7. Can I use this extension when I already have another extension that globally controls audio equalization or audio volume?

    Nope! you can only have a single add-on that controls audio equalization. This is the limitation of the JavaScript API. There is only one allowed media node that can control each media element. So if a website has already had a media node, neither this extension nor other similar extensions cannot control the media playing of this page.

  8. Why does this extension not work on some websites?

    There are two cases where the extension cannot function as expected. 1) When you have another extension that generates audio node and this audio node is created before this extension sets its own node. In this case, the former extension is in control. In general, it is not recommended to have multiple extensions that do the same or similar jobs since they can conflict. 2) When a webpage has its own media node and this node is in control. Again since only one node is accepted, there is no way to get the control.

  9. What is the meaning of the persist checkbox in the popup window?

    If you want to keep the extension enabled after a restart, this option must be checked, otherwise, the extension disables itself after a relaunch.

Matched Content

Reviews

Please keep reviews clean, avoid the use of improper language and do not post any personal information.
  • <a> Defines an anchor.

    Example: <a href="http://add0n.com">a sample link</a>

  • <pre><code> Syntax Highlighting (Supported languages: Bash, JSON, HTML, JavaScript, and CSS).

    Example: <pre><code class="javascript">var foo = 'bar';</code></pre>

  • <strong> Defines bold text
  • <blockquote> Defines a long quotation
  • <caption> Defines a table caption
  • <cite> Defines a citation
  • <em> Defines italic text
  • <p> Defines a paragraph
  • <span> Defines a section in a document
  • <s> Defines strikethrough text
  • <strike> Defines strikethrough text
  • <u> Defines underlined text
  • <br> Defines a single line break; can be used alone and don't need an ending tag

What's new in this version

Version--
Published--/--/--
Change Logs:
    Last 10 commits on GitHub
    Hover over a node to see more details

    Need help?

    If you have questions about the extension, or ideas on how to improve it, please post them on the  support site. Don't forget to search through the bug reports first as most likely your question/bug report has already been reported or there is a workaround posted for it.

    Open IssuesIssuesForks

    Permissions are explained

    PermissionDescription
    storageto keep user preferences such as volume level and per-frequency amplification levels
    webNavigationto be able to inject controlling script to the browser tabs when the extension is enabled
    <all_urls>to be able to control audio equalization for both local and remote resources

    Recent Blog Posts on add0n.com