OSCILLA

A zero-install, scientifically honest acoustic laboratory in your browser: generate, measure and reproduce sound experiments, and know how far each result can be trusted.

See sound. Shape frequency.

Try it: https://korczis.github.io/oscilla/. It is one HTML file that loads nothing at runtime: no install, no account, nothing sent anywhere, and the same file runs when you open dist/index.html from disk (claims dist-self-contained, opens-from-file-and-subpath).

Landing page: https://korczis.github.io/oscilla/lab/, an interactive overview in Czech with the app in a playable frame, cards that open each workspace, the screenshots below and charts of the releases, the plan and the claims. It is generated from this repository on every Pages deploy, beside the unchanged app.

Three things to try first

Each link opens its workspace and starts nothing until you press a button.

1. Hear and see a tone. Hold Hold to Play (or Space) for the default 440 Hz sine, and watch its waveform, spectrum and spectrogram; letting go stops it (claims tone-plays-and-releases, space-one-owner).
2. Measure your speaker, room and microphone chain. The link fills the Measure setup with two 3-second log sweeps. Check the setup, start quietly and without headphones, and read the response with its valid range and the quality reasons for its rating. Nothing is called dB SPL until you calibrate the level (claims measurement-workbench, transfer-function, measurement-quality, spl-only-with-level-calibration).
3. Patch a synth in the Studio. The Subtractive Synth template opens on its graph: an oscillator through an envelope and a filter whose cutoff an LFO and an automation lane move. Press Play; the graph on screen is the graph that sounds (claims studio-compiled-topology, studio-click-free-live-edit).

tests/unit/extending-guide.test.mjs checks that each of these addresses routes to the workspace, recipe and template it names (claim readme-landing-links-route). Each claim id is an entry of docs/CLAIMS.yaml with the test that proves it.

Extend it

OSCILLA is MIT-licensed, modular source that you can read, change and build into the same single file. Hack and extend OSCILLA shows where each kind of extension plugs in: a Studio node (with a complete example), a template, a lab or workspace, a chart, a browser check, and the rules a change has to satisfy. Every file, export and npm script the guide names is checked by a unit test, and its example node compiles through the real Studio registry (claim extending-guide-checked).

What it does today

From one static file and with no account:

• measure the response of your speaker, room and microphone chain with a log sweep, and see the quality reasons that say how far that response can be trusted;
• compare two experiments, for example two setups or two microphone positions, with every difference between their records named;
• save an experiment and repeat it later from its recipe;
• generate tones, sweeps and sequences and see them as waveform, spectrum and spectrogram;
• patch a signal graph in the Studio and run it;
• play the Synth, a semi-modular voice with polyphonic engines and an XY pad, from its keyboard, the computer keys or a MIDI keyboard, and keep sounds in one patch library shared with the Studio.

From a tone to a result you can trust

flowchart LR
  gen["Generate<br/>tone, sweep or sequence"] -->|"listen and watch"| obs["Observe<br/>waveform, spectrum, spectrogram"]
  obs -->|"play a log sweep through<br/>speaker, room and microphone"| mea["Measure<br/>transfer function, impulse response, RTA"]
  mea -->|"valid range and<br/>quality reasons"| int["Interpret<br/>relative dB until the level is calibrated"]
  int -->|"save the run"| exp["Save and repeat<br/>an experiment reruns from its recipe"]
  exp -->|"two setups or positions"| cmp["Compare<br/>every difference between records named"]
  gen -.->|"the same engine, as a patch"| stu["Studio<br/>the graph on screen is the graph that sounds"]

The illustration above is drawn, not measured. The screenshot below is the real built app, captured by npm run social from dist/index.html:

Screenshots

These are the visual-gate references of the built app, not mock-ups: CI renders dist/index.html and the visual scripts (scripts/visual-*.mjs) fail the build when a render drifts from them. They are read from tests/visual/reference.png + tests/visual/*/linux-x64-*.png.

On a phone, 390 px wide:

This is the beginning of the README. Read the rest at the original. Read the full README ↗