Dplug is a library for creating audio plug-ins as simply as possible.
- Create VST 2.4 plug-ins for macOS, Windows, and Linux (to distribute VST2 plug-ins be sure to sign a VST2 Licence Agreement with Steinberg)
- Create Audio Unit v2 plug-ins for macOS
- Create AAX64 Native plug-ins for macOS and Windows
- Build plug-ins faster and with less pain: D language, plug-in bundling, color correction, performance tests...
- Small binaries with (optional) rendering
- Support major DAWs
- Small, tight-knit community
Community and ecosystem
These products use Dplug:
- Couture by Auburn Sounds
- Entropy by Cut Through Recordings
- Graillon by Auburn Sounds
- M4 Multiband Compressor by Cut Through Recordings
- Panagement by Auburn Sounds
- Tarabia Distortion by SMAOLAB
Increase quality and reduce time-to-market with commercial audio DSP in the DSP Asset Store.
Keep up with major changes here: Release Notes
- Does Dplug support the creation of synthesizer plug-ins?
- Am I forced to use the PBR rendering system?
No. And if you don't use it, you don't pay for it.
- What is the oldest supported Windows version?
- What is the oldest supported OS X version?
OS X 10.8+.
What D compiler can possibly be used?
.travis.ymlfor supported compilers. The latest DMD or LDC should do.
What D compilers are recommended?
For releases it is highly recommended that you use LDC >= 1.8. When in development you can use DMD for faster compilation times.
Is Dplug stable?
Dplug has excellent stability.
Dplug documents all breaking changes in the Changelog and issues major SemVer tags for breaking changes.
If you don't want breaking changes, you can pin Dplug to a major version in your
But reality is complex, and bug fixes can be breaking too, (eg: "highpass FIR wasn't working"). In which case we have to make a judgment call as to whether it's a breaking fix, and whether the buggy feature was used.
Breaking commits, when they happen, are marked with BREAKING in the commit backlog. They are discussed on Discord to assess the impact.
- Will you add feature X?
You have to understand that Dplug is a part-time operation, from people who spend much more time working on and releasing plug-ins.
Dplug is there to support existing products and building commercial companies around them, not to be beta software and make empty promises. Being stable and bug-free is much more important to us than implement every possible feature.
Politically, it's very often than enhancements get postponed in favour of product development, so please be patient!
We're looking for ways to improve governance as more contributors have appeared with contrasted agendas.
- Where do I start?
Be sure to read the Wiki in depth.
Strengths of Dplug
- As lightweight as possible
- Public bugtracker
- Well-defined scope: for professional plug-in developers
- Maintained continuously, supported by sales for the foreseeable future
- Price is free, no personal support must be expected though
- PBR-style rendering lets you have a good visual quality with less disk space. If you don't use it, you don't pay for it.
- No dealing with resource compilers: D can
- Easy to install and update
- Constant push to fight complexity and minimize LOC
Dplug has different licenses depending on the sub-package you need. Please check individual source files for license information. Please respect the individual licences when releasing a plug-in.
Plugin format wrapping
Plugin wrapping is inspired by the IPlug library (best represented here: https://github.com/olilarkin/wdl-ol).
Some files falls under the Cockos WDL license.
Important contributors to IPlug include:
If you don't have the VST SDK, you can't make plugins with Dplug. Find the VST SDK there: http://www.steinberg.net/en/company/developers.html
If you don't have a licensing agreement with Steinberg, you can't distribute VST2 or VST3 plug-ins.
Other source files fall under the Boost 1.0 license.