Where Does QjackCtl Store Config and Presets?
QjackCtl keeps server presets and options in an INI file under .config rncbc.org, with patchbay graphs as user-saved XML elsewhere.
Last updated
QjackCtl centralizes server control in one INI file. Presets with audio parameters stack beside options naming the active patchbay graph. Everything editable lives in that conf file under the rncbc vendor path.
Patchbays escape the scheme into user-chosen XML files. The jackdrc file beside it all is write-only telemetry for auto-start, never read back. Copy the conf plus referenced XML graphs and the rig moves complete.
Where QjackCtl stores this, by platform
~/.config/rncbc.org/QjackCtl.conf
INI presets with server parameters plus options naming the active patchbay XML. Patchbay graphs save to user-chosen paths referenced from here. The jackdrc neighbor is write-only.
Frequently asked questions
How do I back up QjackCtl settings?
Copy ~/.config/rncbc.org/QjackCtl.conf with the app closed. Preset sections carry server name, rate and driver choices while the options section names the active patchbay. Patchbay XML files travel separately from their referenced paths.
What is .jackdrc for?
It writes the auto-start command line but never reads it back under D-Bus operation. Quote it for process archaeology only. The conf file above is the settings source of truth.
Where are my patchbay files?
No fixed location exists. Patchbay definitions save wherever chosen and link through the active path key. Example dot-config paths in guides are illustrations, not defaults, so record your own location.
Notice an outdated path? Let us know.