Plugin Development Tutorial

Prerequisites ¶

• Familiarity with C++, although creating Rack plugins is a great way to learn programming and C++. Rack plugins are written in C++11.
• Familiarity with navigating the command line (cd, ls, etc).
• Familiarity with modular synthesizers. Digital signal processing (DSP) knowledge is only required if creating sound generators and processors.
• Download and install VCV Rack.
• Follow the steps to set up your build environment for your operating system. You do not need to build Rack from source if using the Rack SDK.

In your terminal, run

export RACK_DIR=<Rack SDK folder>

to specify the absolute path of the extracted Rack SDK. You may wish to add this line to your ~/.bashrc or other shell environment, so you don’t have to define it every time you open a terminal.

Creating your template plugin ¶

The helper.py script included in the Rack SDK is an easy way to create a plugin template. You can run it with no arguments to show documentation.

Choose a slug for your plugin, a unique string containing letters, numbers, -, or _. We will use MyPlugin for this tutorial. Run

$RACK_DIR/helper.py createplugin MyPlugin

to create a folder called MyPlugin/ in your current directory. Example session:

Plugin name [MyPlugin]: My Plugin
Version [1.0.0]:
License (if open-source, use license identifier from https://spdx.org/licenses/) [proprietary]: CC0-1.0
Brand (prefix for all module names) [My Plugin]:
Author []: VCV
Author email (optional) []: support@vcvrack.com
Author website URL (optional) []: https://vcvrack.com/
Plugin website URL (optional) []:
Manual website URL (optional) []:
Source code URL (optional) []:
Donate URL (optional) []:
Manifest written to MyPlugin/plugin.json
Created template plugin in MyPlugin/
Initialized empty Git repository in /home/VCV/MyPlugin/.git/

You can change this manifest later by editing plugin.json. (See Manifest).

To test your build system, you may run make in the plugin directory. If it succeeds, an “empty” plugin will be built containing no modules. However, this is an good opportunity to check that your build environment is set up correctly.

Creating panels ¶

For each module you wish to create, follow the Panel Guide to design an SVG panel graphic.

For this tutorial, we will create a module with the slug MyModule and panel file MyModule.svg. Save this file to res/ and run

$RACK_DIR/helper.py createmodule MyModule res/MyModule.svg src/MyModule.cpp

This will create a C++ file automatically from components in the SVG file. Example session:

Module name [MyModule]: 
One-line description (optional) []:  Simple sine oscillator
Tags (comma-separated, case-insensitive, see https://vcvrack.com/manual/Manifest#modules-tags for list) []: VCO
Added MyModule to plugin.json
Found 1 params, 3 inputs, 4 outputs, 4 lights, and 0 custom widgets in "components" layer.

To enable the module, add

	extern Model* modelMyModule;

to plugin.hpp, and add

	p->addModel(modelMyModule);

to the init() function in plugin.cpp.
Source file generated at src/MyModule.cpp

Add the Model to plugin.hpp and plugin.cpp as stated by the helper script.

Implementing the DSP kernel ¶

Rack modules have four basic components, as we saw in the Panel Guide.

• Param: Read with params[...].getValue()
• Input: Read with inputs[...].getVoltage()
• Output: Write with outputs[...].setVoltage(voltage)
• Light: Write with lights[...].setBrightness(brightness)

In this tutorial, we will implement a simple sine oscillator with a PITCH param, 1V/octave PITCH input, SINE output, and a BLINK light that flashes at 1 Hz.

Open the generated src/MyModule.cpp source file and add the following member variables to the Module class.

	float phase = 0.f;
	float blinkPhase = 0.f;

These variables store the internal state of the module. Then add the following code to the process() function, which is called every audio frame (e.g. 44,100 times per second if the sample rate is 44,100 Hz).

	void process(const ProcessArgs &args) override {
		// Compute the frequency from the pitch parameter and input
		float pitch = params[PITCH_PARAM].getValue();
		pitch += inputs[PITCH_INPUT].getVoltage();
		// The default frequency is C4 = 261.6256f
		float freq = dsp::FREQ_C4 * std::pow(2.f, pitch);

		// Accumulate the phase
		phase += freq * args.sampleTime;
		if (phase >= 1.f)
			phase -= 1.f;

		// Compute the sine output
		float sine = std::sin(2.f * M_PI * phase);
		// Audio signals are typically +/-5V
		// https://vcvrack.com/manual/VoltageStandards
		outputs[SINE_OUTPUT].setVoltage(5.f * sine);

		// Blink light at 1Hz
		blinkPhase += args.sampleTime;
		if (blinkPhase >= 1.f)
			blinkPhase -= 1.f;
		lights[BLINK_LIGHT].setBrightness(blinkPhase < 0.5f ? 1.f : 0.f);
	}

Compile your plugin with make. If the build succeeds, you can generate a distributable plugin package with make dist, which places it in dist/.

You can automatically install the plugin package to your Rack user folder with make install. You should now be able to test your plugin by opening Rack and choosing your module in the Module Browser.

If you don’t see your plugin in Rack’s Module Browser, check the log.txt file in your Rack user folder. This file contains warnings about plugins that fail to load and error messages if your plugin crashes.

Beyond the tutorial ¶

The Rack API is very flexible for creating custom DSP algorithms and custom interactive widgets handling many types of events from the keyboard, mouse, etc. See the Rack API headers or the Rack API documentation for the full reference, or review the source code of the many open-source plugins if you prefer learning by example.

The Voltage Standards article defines the behavior for handling signals in a consistent way.

You can find a wealth of information on the Developer category of the VCV Community forum by searching or creating a new thread.

Releasing ¶

Eventually you may want to release your hard work.

See Plugin Licensing for information about following Rack’s license, particularly if developing a commercial plugin. It is recommended to add a LICENSE.txt file to your plugin’s root folder that specifies your preferred license (whether open-source or proprietary).

Review your plugin.json manifest file for correctness, spelling, and capitalization. Finally, submit your plugin to the VCV Library to allow users to easily download your plugin from their VCV account.