Atlas node · Tools · prototype DSP study
Horizon
Mid/side DSP processor for spatial and dynamics experiments where dry/wet comparison and listening become the evidence.
Where listening becomes evidence
Horizon treats spatial processing as something that has to be heard against itself. Dry and wet, center and side, pressure and release become the terms of the argument.
A processor can hide behind taste words too easily. This work asks the chain to show what it changes, how the controls move, and whether the listening proof can carry the claim.
DSP math, control maps, and preset direction show the intended shape of the tool. The missing public proof is audible: a short before-and-after trace tied to the settings that made it.
The page should stay with prototype listening evidence, not mastering-grade generality, enclosure maturity, or live reliability that has not been shown.
What it is
Horizon is a mid/side processing study with hardware and plugin directions. It matters publicly because it exposes spatial shaping and dynamics as a readable chain rather than a black-box finishing move.
What it lets people do
It lets people compare dry and processed audio, trace control mappings, and reason about what the processor is actually changing.
What is public now
Evidence status
Status: prototype DSP study. The public source supports the design direction, but the page still needs an audible before/after proof before stronger quality claims belong here.
Next proof object: 30-second dry/wet audio comparison with one screenshot or note naming the key settings used.
What remains unresolved
- The current public page should not imply mastering-grade generality or long-run live reliability.
- Hardware maturity and enclosure state should stay modest until shown directly.
- Integration claims with other tools are still stronger conceptually than publicly documented.
Methods surfaced
Related Fleet Projects
Source trail
- Project repo — Implementation truth.
- Last reviewed: 2026-05-15
The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.
Where to go next
- Open frZone — Follow the analysis side of the sound branch.
- Open live-rig — Follow the processor into a larger performance topology.