Signed-off-by: falkTX <email@example.com>
|1 year ago|
|.github||1 year ago|
|cmake||1 year ago|
|dgl||1 year ago|
|distrho||1 year ago|
|examples||1 year ago|
|lac||9 years ago|
|tests||1 year ago|
|utils||1 year ago|
|.gitignore||1 year ago|
|.gitmodules||2 years ago|
|CMakeLists.txt||2 years ago|
|FEATURES.md||2 years ago|
|LICENSE||2 years ago|
|LICENSING.md||2 years ago|
|Makefile||1 year ago|
|Makefile.base.mk||1 year ago|
|Makefile.plugins.mk||1 year ago|
|README.md||2 years ago|
|dpf.doxygen||1 year ago|
|dpf.kdev4||9 years ago|
DPF is designed to make development of new plugins an easy and enjoyable task.
It allows developers to create plugins with custom UIs using a simple C++ API.
The framework facilitates exporting various different plugin formats from the same code-base.
DPF can build for LADSPA, DSSI, LV2 and VST formats.
All current plugin format implementations are complete.
A JACK/Standalone mode is also available, allowing you to quickly test plugins.
Plugin DSP and UI communication is done via key-value string pairs.
You send messages from the UI to the DSP side, which is automatically saved in the host when required.
(You can also store state internally if needed, but this breaks DSSI compatibility).
Getting time information from the host is possible.
It uses the same format as the JACK Transport API, making porting some code easier.
DPF is released under ISC, which basically means you can do whatever you want as long as you credit the original authors.
Some plugin formats may have additional restrictions, see LICENSING.md for details.
Bug reports happen on the DPF github project.
Online documentation is available at https://distrho.github.io/DPF/.
Online help and discussion about DPF happens in the kx.studio chat, DPF room.
Checking the github “DPF” tag can potentially bring up other DPF-made plugins.
Plugin examples are available in the
example/ folder inside this repo.