Add a readme section on plugin formats
This commit is contained in:
parent
b209c9caf3
commit
8c63cebc07
|
@ -17,6 +17,7 @@ functionality.
|
||||||
- [Framework](#framework)
|
- [Framework](#framework)
|
||||||
- [Current status](#current-status)
|
- [Current status](#current-status)
|
||||||
- [Building](#building)
|
- [Building](#building)
|
||||||
|
- [Plugin formats](#plugin-formats)
|
||||||
- [Example plugins](#example-plugins)
|
- [Example plugins](#example-plugins)
|
||||||
- [Licensing](#licensing)
|
- [Licensing](#licensing)
|
||||||
|
|
||||||
|
@ -52,6 +53,14 @@ of the plugin:
|
||||||
cargo xtask bundle gain --release
|
cargo xtask bundle gain --release
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Plugin formats
|
||||||
|
|
||||||
|
NIH-plug can currently export VST3 plugins, with CLAP support being worked on
|
||||||
|
right now. Exporting a specific plugin format for a plugin is as simple as
|
||||||
|
calling the `nih_export_<format>!(Foo);` macro. The `cargo xtask bundle` commane
|
||||||
|
will detect which plugin formats your plugin supports and create the appropriate
|
||||||
|
bundles accordingly, even when cross compiling.
|
||||||
|
|
||||||
### Example plugins
|
### Example plugins
|
||||||
|
|
||||||
The best way to get an idea for what the API looks like is to look at the
|
The best way to get an idea for what the API looks like is to look at the
|
||||||
|
|
Loading…
Reference in a new issue