Fundamentals
Export Targets
Code Export
Patcher UI
Special Topics
RNBO Raspberry Pi OSCQuery Runner
Exporting to the Audio Plugin Target
The Audio Plugin Target is available from the Target Export Sidebar. It allows you to export your rnbo~ patcher as a VST or AudioUnit to use in your DAW.
Audio Plugin Export
With the rnbo~ patcher open, select the show export sidebar option to open the export target sidebar. Then select the Audio Plugin Export Target from the target list by double-clicking this option.
Configuration
The configuration window provides various configuration options related to the export.
Format and Platform Determines the Audio Plugin Format (VST3 or AU) and operating system for which the plugin will be built. RNBO can export an audio plugin for use on a Mac, Windows, or Linux system. It can generate .vst3
files or Audio Unit .component
files appropriate for a chosen platform, regardless of which platform you might be using to run RNBO.
Plugin Name The filename of the plugin.
Plugin Manufacturer Name and Plugin Manufacturer Code These settings determine the metadata associated with your exported plugin. Note: many DAWs group plugins together by Plugin Manufacturer Name—so you might want to give a recognizable name here. For the code, this can be any 4 letter code, but must contain at least one upper case character. This may be required by certain host DAW's.
Plugin Type:
- Instrument is a plugin that takes MIDI input and outputs audio. Note: unless you have a midiin object and an out~ object in your patch, RNBO will not attempt to build your Instrument plugin.
- Effect is a plugin that transform audio. Note: unless there is an in~ or out~ object in the patch, RNBO will not attempt to build your Effect plugin.
Output Directory By default your externals will be saved to the folder ~/Documents/rnboPlugins
. You can change this destination by selecting 'Choose' next to Output Directory to save your Max external to your preferred location.
Note: many applications, including DAWs, look to a standard Plugin folder when scanning your machine for audio plugins. You might want to move your plugin to this location after it is exported, so your plugins can be picked up by your DAW's scan of your machine's audio plugins.
For macOS, that folder is: /Library/Audio/Plug-Ins/
Note that there are folders within/Plug-Ins
for specific file formats, like/Components
for Audio Units and/VST3
for VST3. Note, also, that macOS may block you from writing files directly into this/Plug-Ins
folder from RNBO.
On a Windows machine, the standard location for VST3 plugins is: C:\Program Files\Common Files\VST3
If your RNBO patcher is in a Max project, by default the Ouput Directory will be set to a folder called /export/plugin
in your project folder.
Include Presets Max snapshots on the rnbo~ object will be included as selectable presets of your exported plugin. For more information on making presets in RNBO, visit our Presets with Snapshots article.
Package Sample Dependencies RNBO will copy audio files that have been referenced by the buffer~ object's @file
attribute into the plugin bundle.
Codegen: Polyphony Voice Settings:
- Linked Exports the number of voices set from the rnbo~ object with the
@polyphony
attribute . Uncheck if you want to export a different polyphony count than specified in the@polyphony
attribute in the rnbo~ object.
- Disabled Disables polyphony for the code generated from this export.
- Voice Count Sets the desired maximum voice count for simple polyphony. Note : This does not affect the behavior or voice count of any rnbo subpatchers that use polyphony.
Codegen: Expose per Voice Params Enable if you want to modulate the params of individual voices separately instead of as a group.
Open Export Directory Open a file dialog and navigate to the code export directory once the export is complete
Time to Export
With our plugin fully configured, it's time to export. The Export to Selected Target button is on the lower right-hand side of the export sidebar.
Now the export log view will appear, and you can enjoy some sips of coffee or tea while your plugin is built for you on the cloud. Once it has been built, the ouput directory you selected will open, revealing your beautiful plugin.
You can now load your plugin in your DAW of choice, and enjoy your instrument or effect! If you re-export your plugin with changes, you may need to restart your DAW to ensure that it finds the most recent version of your plugin.
You'll notice that your plugin is built using a default user interface. If you'd like to explore creating a custom UI for your RNBO plugin, you'll need to write some C++ code. Check out our article on designing a custom GUI with JUCE.
A note about distribution
This plugin export is designed for your own personal use, as opposed to making a plugin that you will sell or distribute widely. If you look at the exported .vst3 file, for example, you'll notice that next to the file there is a README file, which says:
These binaries are provided for personal use only. Any distribution of these binaries to other parties requires the registration and licensing of the VST 3 Technology from Steinberg. Please consult Steinberg for more licensing information: https://developer.steinberg.help/display/VST/VST+3+Licensing
It is possible to distribute your RNBO-exported VST with a license from Steinberg, or by open sourcing the project. In addition, you will need to follow some steps in order for your plugins to run on another macOS machine. For more information on both of these points and more, check out the RNBO Export Licensing FAQ.