Your library

Patches, Devices & sharing

A patch is everything on the canvas: modules, knob positions, cables, groups, step patterns, MIDI mappings, tempo. This page covers saving, browsing, reusing and sharing them.

Saving and opening

Cmd+S saves (Cmd+Shift+S for Save As) to ~/Documents/Resonode Patches/ as a .rnpatch file — human-readable JSON, if you're curious. Cmd+O opens the patch browser: search your library by name, with the factory examples folded in at the top, and rename or delete right there. Cmd+N starts fresh.

Devices: your own building blocks

Select any group of modules and save it as a Device (.rndevice) — a reusable block with its internal cables intact. Drop a Device into any future patch from the right-click menu. A tuned kick chain, a favourite delay-into-reverb tail, a whole generative melody brain: build it once, keep it forever.

Sharing patches as text

File → Copy Patch as Text puts the entire patch on the clipboard as a compact text blob. Paste it into a forum post, a Discord message, an email. Anyone with Resonode uses File → Paste Patch from Text to load it — line-wrapping and surrounding chatter are tolerated, so it survives most paste mangling.

Samples travel separately. A patch stores a reference to loaded sample files, not the audio itself. If your patch leans on a Sampler file, send the sample alongside the text — or resample into the patch's own recorded buffers before sharing.

What a patch remembers

Every module, its parameters and bypass state, and its position on the canvas
All cables and groups
Step patterns, probabilities, ratchets and lane lengths; Piano Roll clips; MSEG shapes; Notes text
MIDI Learn mappings
Transport tempo and sync settings

Autosave and recovery

Autosave runs every 30 seconds while there are unsaved changes. If Resonode didn't close cleanly, the next launch offers to restore — you lose half a minute at worst.