Editing the settings as JSON

Everything the Preferences dialog writes ends up in one of two stored documents - the settings and the card profiles - and both can be opened directly, as text, from the Tools menu. It is the way to see the whole of your configuration at once, to copy a card between machines, or to change something the dialogs deliberately do not expose.

The JSON configuration editor open on the preferences document, with the completion list showing

Tools carries two submenus:

Menu item	What it opens
Preferences ▸ Current	The live settings document - everything on the five tabs of the Preferences dialog, plus the per-backend blocks and the remembered servers.
Devices ▸ Current	The live device store - your card profiles, their ranges and their measured full-scale values.
... ▸ Corrupt	Present only when a store was kept aside because it could not be read. Opens that copy read-only.

Editing

The document opens pretty-printed, and the editor knows its shape:

Completion. Start typing a key and it offers the ones that document actually allows, so you are not guessing at spelling or inventing keys the application will ignore.
Hover help. Point at any key and a sentence explains what it is and what its values mean - the same explanation for every setting, including the many that have no control in the Preferences dialog.
Nothing changes while you look. OK applies the document to the running application and writes it to storage in one step, so a colour, a sample rate or a whole card takes effect without reloading the page. Cancel discards it.
A mistake keeps the window open. Text that is not valid JSON is reported with the position of the fault and nothing is applied - your editing is never thrown away by pressing OK.

The window is movable by its title bar and resizable from its bottom-right corner, and it remembers where and how big you left it.

The one refused edit

One edit is refused, and it is the dangerous one. A device document with no audioDevices list at all is rejected rather than applied. It is easy to arrive at - deleting the block to "start clean", a mistyped audiodevices, or pasting back only the version header - and applying it would delete every card profile and every calibration in it while looking like a success. To empty the store deliberately, write an empty list: "audioDevices": [] is accepted and really does clear it.

The Corrupt copy is read-only and has no OK button. It is shown formatted when it can be parsed, and exactly as stored when it cannot - that text is the only record of what went wrong, so the editor never tidies it. Copy what you need out of it; the application will not write to it.

Editing the settings as JSON

Where it is

Editing

The one refused edit