Skip to content

PeakEater is a free open-source cross-platform VST3/AU/LV2/CLAP wave shaper plugin

License

Notifications You must be signed in to change notification settings

vvvar/PeakEater

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PeakEater

Free open-source VST3/AU/LV2/CLAP wave shaping plugin for macOS, Windows and Linux.

Download · Request Feature · Report Bug

screenshot

Table of Contents

About

PeakEater is a free, easy-to-use wave-shaping plugin. PeakEater lets you choose between different wave-shaping functions to clip everything above ceiling level. Therefore, you can boost the overall volume of your track safely without worrying that some nasty peak would go above the maximum allowed volume level of your DAW. It supports various features such as multiple clipping types, oversampling and visualizations of a clipping process that aims to make clipping easy and fun.

Features

RMS Meters

input-rms-screen<--->output-rms-screen

See how loud the signal was before and after the plugin.

Input & Output Gain

input-gain-screen<--->output-gain-screen

Adjusts gain level before and after processing. Input Gain is useful when you're either working with too quiet or too loud a signal and Output Gain can be helpful to compensate for loss of gain.

Link Input with Output

link-in-out

Use linking to automatically set the Output Gain level to the opposite of the Input Gain. For example, if the Input Gain value is set to +5dB then the Output Gain value will be automatically set to -5dB and vice versa.

Ceiling control

link-in-out

Control your ceiling. Everything above this level would be "eaten". Build-in RMS meter would show you the signal level that comes into the clipper and help you set the threshold.

Visualizer

clip-visualizer

Displays magnitude(in dB's) so you can see how peaks were eaten over time.

Analyzer

clip-analyzer

Shows approximated RMS that was cut ("Eaten") in the last 2 seconds and current clipping algorithm. Double-click on numbers to drop them to zero and force them re-calculate.

Configurable Tick marks

switch-db-level-scales

Right-Mouse-Click on Visualizer to switch between different tick marks.

Configurable Scaling

switch-db-level-scales

Also, you can switch between linear and non-linear scaling.

6 Clipping Types

clip-type

Choose between 6 clipping functions, from Hard clipping to different types of Soft Clip (Up to Arctangent). Available clipping functions are:

  • Hard
  • Quintic
  • Cubic
  • Tangent
  • Algebraic
  • Arctangent

You can read more about the difference between Hard and Soft clipping here and here.

Oversampling

oversample

Choose between 2x, 4x, 8x, 16x and 32x oversampling to avoid signal aliasing. You can also turn off oversampling.

Note High values of oversampling may hurt CPU performance.

You can read more about oversampling here.

Dry/Wet

drywet

Control mix between original and clipped signal. Useful when the clipper is used as an exciter.

Bypass mode

bypass

Bypasses all plugin's processing. Useful when you need to make side-by-side comparisons before and after processing.

Resizing

bypass

Drag the corner to change the size of the window.

VST3, AU, LV2 and CLAP support

vst3 au lv2 clap

You can use either VST3, AU (macOS only), LV2 or CLAP type of plugin.

Warning LV2 and CLAP support is experimental and may be unstable.

Available on all major platforms

macOS windows linux

You can use it on macOS, Windows or Linux.

Warning Linux support is experimental and may be unstable.

Verified by Pluginval Pluginval

pluginval is a cross-platform plugin validator and tester application. It is designed to be used by both plugin and host developers to ensure stability and compatibility between plugins and hosts. GitHub Project Link

VST3 and AU versions are verified by Tracktion Pluginval for all platforms. Maximum possible strictness level 10 is used. For macOS and Linux - Headless Mode is being used and GUI Mode is used for Windows. Starting from v0.6.5, you may find proofs of Pluginval verification in the "Assets" section on the Release page(*.txt files are split by platform and plugin format).

Installation

  1. Go to the latest release page.
  2. In the Assets section choose the installer for your platform.

macOS

Supported formats are VST3, AU, LV2 and CLAP. Tested on: macOS 12.6.2 Processors: Intel(x86_64), Apple Silicon M1+(arm64)

Install the plugin via the .dmg file. Drag the plugin in a format of your choice into the folder with your plugins.

Note
Plugin is build as an Universal Binary. This means that same plugin supports both x86_64 and Apple Silicon(M1+). Just install it and it will automatically run natively with respect to your processor.

Note
Due to macOS restrictions, you cannot drag files into untrusted directories. Therefore, double click on directory shortcut, open it and drag it directly there.

Note
VST3 directory is /Library/Audio/Plug-ins/VST3
AU directory is /Library/Audio/Plug-ins/Components
LV2 directory is /Library/Audio/Plug-Ins/LV2
CLAP directory is /Library/Audio/Plug-Ins/CLAP

Windows

Supported formats are VST3, AU, LV2 and CLAP. Tested on: Windows 10 21H2

Extract the zip and copy the plugin in the format of choice into the folder with your plugins.

Note
Standard VST3 folder is C:\Program Files\Common Files\VST3
Standard LV2 folder is C:\Program Files\Common Files\LV2
Standard CLAP folder is C:\Program Files\Common Files\CLAP

Linux

Supported formats are VST3, AU, LV2 and CLAP. Tested on: Ubuntu 18.04

Extract the zip and copy the plugin in a format of your choice into the folder with your plugins.

Note
Standard VST3 directory is ~/.vst3
Standard LV2 directory is ~/.lv2
Standard CLAP directory is ~/.clap

Building from sources

Prerequisites

Note
It is recommended to use PowerShell on Windows

Building

just setup
just build

Build artifacts will be stored in the /build/Release/peakeater_artefacts.

Code signing on macOS

By default, code signing is turned off. To enable it:

  1. Make sure you have a valid Apple Developer ID, Apple Team ID and your signing certificate installed on your Mac(Use this guide as a starting point. Be aware - they are not free)

  2. Create a file called .env with the following content(replace the value with your Apple Developer ID, Apple ID, password from your Apple ID and Team ID):

MACOS_APPLE_DEVELOPER_ID="Developer ID Application: John Doe (XXXXX6XX42)"
MACOS_APPLE_ID="johndoe@gmail.com"
MACOS_APPLE_PASSWORD="jhnd-oejh-ndoe-jhnn"
MACOS_APPLE_TEAM_ID="JHNDO6E642"
  1. Setup the notarytool(used to notarize DMG):
just setup-notarytool

You should see something like this in the terminal:

xcrun notarytool store-credentials "APPLE_SIGN_PROFILE" --apple-id $MACOS_APPLE_ID --password $MACOS_APPLE_PASSWORD --team-id $MACOS_APPLE_TEAM_ID

This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name.

Validating your credentials...
Success. Credentials validated.
Credentials saved to Keychain.
To use them, specify `--keychain-profile "APPLE_SIGN_PROFILE"`

After this just run the build. CMake will automatically sign all binaries.

Contributing

If you found a bug, please report it using Bug Template. If you have any feedback, feel free to open a feedback ticket using Feedback Template. If you have a specific feature request, please create it using Feature Request Template. If you have a pull request, then just make it using common Fork & PR flow.

License

Distributed under the GPL-3.0 License. See LICENSE.md for more information.

Acknowledgments