VCV Rack Tips
This guide collects the things I use most in VCV Rack 2 and the questions people ask me about plugins. It starts with where Rack keeps its files, because most plugin problems are solved there, then covers the Library, plugins from outside it, key commands for patching, saving your own presets and templates, and the settings that change how much CPU a patch uses. Everything here applies to the free version of Rack. On a Mac, read Ctrl as Command (⌘) throughout.
Where Rack keeps its files
Rack keeps your plugins, settings, presets and the autosaved patch in one place, which VCV calls the Rack user folder. The quickest way to find it is Help, then Open user folder, in Rack's menu bar. Rack 2.5.0 moved it to the locations below. If you installed an earlier version of Rack 2, Rack moved your files there when it updated.
| System | Rack user folder | Plugins folder inside it |
|---|---|---|
| macOS | ~/Library/Application Support/Rack2/ | plugins-mac-arm64 or plugins-mac-x64 |
| Windows | C:\Users\<username>\AppData\Local\Rack2\ | plugins-win-x64 |
| Linux | ~/.local/share/Rack2/ | plugins-lin-x64 |
The plugins folder is named for the operating system and the processor, so on a Mac with Apple
silicon it is plugins-mac-arm64. A Mac running the Intel build of Rack through
Rosetta reads plugins-mac-x64 instead, which is why a plugin can appear to vanish
after switching between the two builds. Each plugin has its own folder in there, named by the
plugin's slug, such as SignalFunctionSet.
The user folder also holds autosave.vcv, which Rack writes every 15 seconds and on
quitting, and template.vcv, which loads when you choose File, then New. Your own
module presets live in presets/, and log.txt records what happened at
the last launch, including any plugin that failed to load and why.
Managing plugins from the VCV Library
Rack installs plugins from the VCV Library through your VCV account rather than through downloads. On the Library website, each module has Add and Remove buttons, and adding a module adds its plugin to your account. In Rack, log in from the Library menu and choose Update all, which downloads every plugin and update added to your account. Rack has to be restarted to load what it downloaded.
The Module Browser shows the individual modules you added, not every module in each plugin, so adding only the modules you use keeps the browser short. Rack still loads each installed plugin when it starts, so a very large collection makes start-up slower. The browser can also show only the modules you have marked as favourites, and it has several sort orders.
If you open a patch that uses modules you do not have, Rack offers to show them on the Library and then loads the patch without them, so you can add them and reopen it. A computer with no internet connection can be given plugins by copying the whole plugins folder from another computer with the same system and processor, since the Library cannot be used to download plugin files directly.
Installing plugins that are not in the Library
Developers sometimes share builds outside the Library: beta and nightly builds, plugins that
have not been submitted, and builds for a processor the Library does not cover yet. These come
as .vcvplugin files, named in the form SLUG-VERSION-OS-CPU.vcvplugin. Download the one that matches your system and
processor, put it in your plugins folder while Rack is closed, and Rack unpacks and loads it at
the next launch. The first number of the plugin's version has to match Rack's, so a 2.x plugin
needs Rack 2. A plugin can run any code on your computer, the same as a VST plugin, so only
install builds from people you trust.
Rack only replaces a plugin from the Library when the
Library's version number is higher than the installed one. If you install a manual build
numbered above the current Library release, Update all leaves it alone until the Library
catches up, so delete the manual build when you want to go back to the Library version.
Some developers give their test builds a different slug so that they can sit beside the
Library version. My nightly builds appear as SignalFunctionSet-dev, for example.
A patch saved with a module from a test build refers to that build, so anyone opening it
without the same build sees the module as missing. Swap those modules for the Library versions
before sharing a patch.
To remove a plugin, close Rack and delete its folder and any matching .vcvplugin
file from the plugins folder. If the plugin is still in your Library account, remove it there
too, or the next Update all can install it again. If you build a plugin from source, make install in the plugin's folder installs it into your plugins folder in the
same way, and log.txt says why if it does not appear.
Key commands for patching
Most commands act on whatever is under the mouse pointer, so hover over a module before using a module command. These are the ones I use most.
The rack
| Keys | What it does |
|---|---|
| Enter, or right-click empty rack | Opens the Module Browser. |
| Ctrl+V | Pastes a copied module at the cursor. |
| F3 | Shows or hides the CPU meter on each module. |
| F4 | Zooms to fit every module in the window. |
| F11 | Enters or leaves fullscreen. |
| Ctrl+0 | Sets the zoom to 100%. |
| Ctrl+scroll | Zooms in and out. |
| Shift+scroll | Scrolls the rack sideways. |
| Middle-drag or Alt+drag | Pans the rack. |
Modules
| Keys | What it does |
|---|---|
| Ctrl+D | Duplicates the module. |
| Ctrl+Shift+D | Duplicates the module with its cables. Since Rack 2.5.2 this includes the cables on its outputs as well as its inputs. |
| Ctrl+E | Bypasses the module. A bypassed module passes certain inputs straight to outputs, if its developer specified which. |
| Ctrl+I | Initializes the module to its default settings. |
| Ctrl+R | Randomizes the module's settings. |
| Backspace or Delete | Deletes the module. Holding the key while moving the mouse deletes every module the pointer passes over. |
| Ctrl+drag the panel | Moves the module and pushes its neighbours aside to make room. |
| Shift+click the panel | Adds the module to the selection. Dragging a rectangle on empty rack also selects. |
| Ctrl+F1 | Opens the module's manual, if its developer supplied a link. |
| Ctrl+F4 | Zooms to fit the module. |
Knobs, sliders and switches
| Keys | What it does |
|---|---|
| Drag up or down | Changes the value. Ctrl slows it down, Ctrl+Shift slows it further, and Shift speeds it up. |
| Double-click | Resets the control to its default. |
| Right-click | Opens a field where you can type an exact value or an expression. |
The value field accepts arithmetic such as 1/3 and a few useful names. A note name
such as A4 enters its frequency in hertz, and since Rack 2.6.1 a note name followed
by v, such as C4v, enters its 1V/oct voltage, with C4 at 0 V. The functions ftov() and vtof() convert between hertz and 1V/oct, and dbtogain() and gaintodb() convert between decibels and gain.
Cables
Dragging from an output while holding Ctrl adds another cable from it, so one output can feed several inputs without a multiple. Since Rack 2.5.0 you can also stack cables on an input, and Rack adds their voltages together. Right-clicking a port opens a menu that starts a cable in a chosen colour, picks up any one cable from a stack, deletes the top cable, or picks up all of them at once. View, then Cable colors, edits the colour list and turns off the automatic change of colour for each new cable, and each colour can have a label.
Holding Ctrl while clicking a menu item keeps the menu open, which helps when stepping through a list of options. View, then Lock module positions, stops modules moving when you only meant to turn a knob.
Presets, templates and selections
A module's Preset menu saves its current settings as a .vcvm file. Presets saved in
the user folder under presets/<plugin slug>/<module slug>/ appear in that
module's Preset menu, including any in subfolders, and Rack rereads the folder each time the menu
opens. Preset, then Save template, makes the current settings the default for every new copy of
that module, which is useful for a mixer or a scope you always set up the same way.
For a whole patch, File, then Save template, saves the current patch as the one File, then New
opens, so your audio interface, MIDI input and favourite utilities can be ready in every new
patch. A group of modules can be saved on its own: select them by dragging a rectangle or
Shift-clicking, then export the selection as a .vcvs file from a selected module's
menu. File, then Import selection, adds it to another patch with its internal cables intact.
CPU and performance
Rack's CPU use is almost exactly proportional to its sample rate, which is set in the Engine menu, so 96 kHz uses about twice the CPU of 48 kHz. A higher rate makes each step of the engine shorter, which makes models of analogue circuits and some digital processes more accurate. Whether you can hear that depends on the modules in the patch, so try the patch at both rates before settling on the higher one.
The Threads setting in the same menu spreads modules across processor cores. VCV recommends starting with one thread and adding one at a time only while you hear dropouts, up to the number of physical cores. More threads let a bigger patch run, at the cost of more total CPU and power. F3 shows how long each module takes, which finds the expensive ones quickly, but the meter uses CPU itself, so turn it off afterwards.
A polyphonic module running several voices on one cable usually uses much less CPU than the same number of monophonic copies, because it processes four channels at once with the processor's vector instructions. VCV gives a figure of up to four times less. On the drawing side, View, then Frame rate, redraws the screen less often, and the GPU work drops in proportion, which helps on a laptop running a large patch.
When something goes wrong
If Rack crashes on launch, a plugin or the autosaved patch is the usual cause. Starting Rack from
a terminal with the -a or --safe option opens it with no plugins and
no autosave, which tells you whether either is responsible. Then read log.txt in
the user folder for the plugin that failed. Rack's menu bar shows its edition, version, system
and processor, which is the information a developer needs first in a bug report.
If a patch goes wrong while you work, Edit, then Undo, goes back through every change, and File, then Revert, returns to the last saved version. If Rack itself crashed, the autosave is at most 15 seconds old, so reopening Rack usually brings the patch back.
For the voltages that Signal Function Set modules use for keys and scales, see the Root and Scale CV reference, and for the modules themselves, see VCV Rack modules.