Skip to content

Latest commit

 

History

History
104 lines (93 loc) · 8.91 KB

PLUGIN_APIS.md

File metadata and controls

104 lines (93 loc) · 8.91 KB
Raw

Plugin APIs

There are quite a few audio plugin API standards which allow your plugin be compatible with certain DAWs and hosts. I'll list the most relevant ones today and their advantages/disadvantages.

CLAP

  • Why?: A brand new fully free and open-source plugin standard with no licensing restrictions. It was started by an employee of the Bitwig DAW and has since gotten development support from several key players in the audio industry. It is built from the ground up by people with real-world experience developing audio software, and such it is designed to fit the needs of actual developers as much as possible. It is written in a stable header-only C API, making it easy to create bindings to it in any programming language.
  • Why Not?: It is still kind-of young, and only a handful of DAWs support this standard. But this is changing, so expect this standard to become more widespread in the next few years! (See cleveraudio.org for a list of currently supported hosts and plugins.)
  • License: MIT
  • Platforms: Linux, Mac, Windows, Android, iOS
  • Support: Currently only supported by a handful of DAWs such as Bitwig, MultitrackStudio, and QTractor, but more DAWs are currently in the works to adopt this standard.
  • Distribution - You can distribute open source and close sourced versions of your plugins (and host CLAP plugins) freely without restriction.
  • SDK source: CLAP SDK (also includes links to examples)
  • Website: cleveraudio.org

VST3 (aka VST version 3)

  • Why?: This plugin standard is widely used and has excellent support in most modern commercial DAWs.
  • Why Not?: Requires a signed license agreement with Steinberg in order to distribute commercial (closed source) VST3 plugins (or to host VST3 plugins in a closed source host). The standard is based on a complicated and messy C++ codebase with some weird design choices. Steinberg has also not been on-board with people distributing SDK bindings to other languages (like Rust).
  • License: Proprietary / GPLv3
  • Platforms: Linux, Mac, Windows
  • Support: Supported by most modern commercial DAWs (with notable exception of Apple's DAW Logic) and a few open source DAWs.
  • Distribution - If you are distributing your plugin with the GPLv3 open source license (or host VST3 plugins with your own GPLv3 host), then you do not need to have a signed license agreement with Steinberg. However, if you want to distribute your plugin closed source or create a closed-source host, then you need to get a signed VST3 License Agreement.
    • Also note that Steinberg has a history of changing their license agreements for however they see fit (like they did when they stopped giving out VST2 licenses). If you want to ever distribute plugins commercially, I would advise you to get a license agreement as soon as possible before Steinberg changes their mind.
  • SDK download: VST3 SDK

VST2 (aka VST, version 2)

  • Why?: It is the most well-known and mature format, supported by almost every DAW.
  • Why Not?: Unless you already have a signed license agreement from Steinberg, you're not even allowed to distribute your VST2 plugins or create a host for VST2 plugins.
  • License: Proprietary
  • Platforms: Linux, Mac, Windows
  • Support: Supported by pretty much every commercial DAW (with notable exception of Apple's DAW Logic) and by most open source DAWs.
  • Distribution: Must have a signed license agreement to distribute any VST2 plugin. If you don't already have a VST2 license, you're out of luck since Steinberg doesn't support it anymore (yeah it stinks).
  • SDK source: (Not available anymore).

Vestige (Reversed engineered VST2)

  • Why?: If you still really need to distribute or host VST2 plugins without a signed license agreement, this is another option.
  • Why Not?: Gray legal area.
  • License: Technically GPLv2/GPLv3, but again this is a gray legal area. It is technically legal since the author claims it to be cleanly and legally reverse engineered without reference to the official VST2 SDK. However, I don't believe this has been tested in court, so I wouldn't rely on it.
  • Platforms: Same as VST2 above.
  • Support: Same as VST2 above.
  • Distribution: You can only distribute your plugins or host as open source under either the GPLv2 or GPLv3 license. Though again, this is a gray legal area so I would be weary.
  • SDK source: Vestige Header File

AUv2/AUv3 (aka AU or Audio Units, version 2 and 3)

  • License: Apache 2.0
  • Platforms: Mac, iOS
  • Support: Main support is for Apple's own Logic DAW, but a few other DAWs that run on Mac support it as well. AU is the only plugin standard supported by Logic.
  • Distribution - You can distribute open source and close sourced versions of your plugins (and host AU plugins) freely without restriction.
  • SDK source: AU SDK

AAX

This is a proprietary plugin standard for use exclusively with Avid's DAW Pro Tools.

  • Why?: Pro Tools is pretty standard in the professional/corporate recording/mixing/mastering industry. Pro Tools only supports AAX plugins.
  • Why Not?: No other DAW supports it. Also, it requires a signed license agreement with Avid, and also requires joining Avid's developer program.
  • License: Proprietary
  • Platforms: Mac, Windows
  • Support: Only Pro Tools
  • Distribution: Requires a signed license agreement with Avid, and also requires joining Avid's developer program.
  • SDK source: (must register to download)

LV2

LV2 is a free and open source plugin standard created for use within the Linux ecosystem.

  • Why?: Even though support for it on Mac and Windows is rare, it is used by a lot of Linux software. There is also a growing community of music producers using Linux.
  • Why Not?: Lack of support in most major commercial DAWs, and the new CLAP spec pretty much makes this standard obsolete in my opinion.
  • License: ISC
  • Platforms: Linux, Mac, Windows (Although support for Mac and Windows is rare.)
  • Support: Supported by most open-source DAWs, but hardly any commercial DAWs support it (namely REAPER, Ardour, Harisson Mixbus, MultitrackStudio, Zrythm, and Tracktion Waveform).
  • Distribution - You can distribute open source and close sourced versions of your plugins (and host LV2 plugins) freely without restriction.
  • SDK source: LV2 SDK
  • sjaehn's LV2 Tutorial - A nice tutorial on developing LV2 plugins.

LADSPA

LADSPA is the precursor to LV2.

  • Why?: It is dead simple to work with.
  • Why Not?: Lack of support in most major commercial DAWs. Also, LADSPA only supports GUI-less plugins. Again, the new CLAP spec makes this standard obsolete in my opinion.
  • License: LGPLv2.1/LGPLv3
  • Platforms: Same as LV2 above
  • Support: Same as LV2 above
  • Distribution: Same as LV2 above
  • SDK source: LADSPA Header File

WAP (Web Audio Plugins)

An open source audio plugin standard for use with web browsers using WebAudio.

  • Why?: If you want to target web-based DAWs.
  • Why Not?: Only works in a web browser, so all native DAWs don't support it.
  • License: MIT
  • Platforms: Web
  • Support: Only web-browser based DAWs
  • Distribution: You can distribute open source and close sourced versions of your plugins (and host WAP plugins) freely without restriction.
  • SDK source: WAP SDK

VCV Rack / Cardinal Plugin

The audio plugin standard for use with the open source VCV Rack or Cardinal virtual synthesizers.

  • Why?: If you want to create plugins for VCV Rack / Cardinal.
  • License: GPLv3
  • Distribution: You can distribute freely if your plugin is GPLv3 or a multitude of other accepted open source licenses. You are allowed to sell closed-source versions if you get special permission from the author via email. See VCV Rack Licensing for more details.
  • SDK source: VCV Rack Plugin SDK
  • VCV Rack Plugin Tutorial - The official tutorial on making VCV Rack plugins.