Reference

Every setting, what it decides, and how the result is worked out. Written so that you can answer your own question without writing to us.

14 nodes · 65 error codes · spec 0.1.0

DESKTOP / MACOS

Sonir Bench

Requirements, the signal path, every control on every screen, the output stage, and the checks.

THE CONVERSION STAGE

Resample design

Every field of the design, what each one decides, and how the tap count and the stopband are solved.

FOURTEEN TYPES

Graph nodes

One page per node: the parameters, their ranges, and the arithmetic the node actually performs.

EVERY CODE

Error codes

What each refusal means and what to change. If a design will not load, start here.

How to read this

Ranges and defaults come from the implementation.
Every range, default and error message on these pages is extracted from the published specification, which is itself generated from the code. They are not transcribed by hand, so they cannot drift from what the app enforces.
Only what is implemented.
These pages describe the build you can install today. Nothing here is a plan, and where something is still being verified on real hardware it says so.
The limits are part of the specification.
Pages end with what the app does not do. Those are decisions rather than gaps, and knowing them is usually what answers the question you were about to ask.
The arithmetic is written down.
Where a value is computed rather than chosen, the formula is on the page. The models used are published ones, named so you can look them up.

Writing a module

This reference describes what the apps do. To write a DSP module yourself, or have an AI write one, the module specification is public: the prose, both JSON Schemas, every error code, and reference modules that pass as they are.

Read the module specification