Where Does Cardinal Store Patches?
Cardinal keeps patches you save plus plugin settings in per-OS config folders. Keep samples beside patches for moves.
Last updated
Cardinal stores plugin settings in per-OS config locations. Patches are separate files you save by hand wherever you like. This covers Cardinal the DISTRHO modular synth, not similarly named tools.
Back up config for the workflow plus patches for the music. Exact filenames vary by release, so confirm inside the plugin when paths differ. Keep samples beside patches for clean moves.
Where Cardinal stores this, by platform
%APPDATA%\Cardinal (patches wherever saved)
Settings in per-OS config. Patches save wherever chosen. Copy both with the DAW closed for full moves.
~/.config/Cardinal (patches wherever saved)
Same split between config and saved patches. Confirm paths in-plugin across versions.
~/Library/Application Support/Cardinal
Same split. Keep samples beside patches when moving machines.
Frequently asked questions
How do I move Cardinal patches?
Copy your saved patch files plus the config folder to matching paths. Patches live wherever you stored them. Settings rebuild when missing.
Rack edits vanished. Why?
Save the patch explicitly before closing. Rack state alone does not persist. Keep .vcv style files beside their samples.
Notice an outdated path? Let us know.