01 Evidence with a boundary
VoltageSpaces is early in development. The current evidence belongs to the measurement system, deterministic engine harness, host shell and interface contract. It does not yet belong to finished Lush or Natural audio.
02 What is demonstrated now
Each result below is connected to executable evidence in the product repository. A public claim disappears if its supporting evidence disappears.
Decay, echo-density and stereo measurements qualify against constructed signals with declared tolerances. Dynamic range or coverage that cannot support a value produces a refusal.
Why it matters: a plausible graph cannot quietly become product evidence.
The deterministic foundation produces the same samples for the same input, including irregular call and buffer groupings. Delay timing scales with sample rate.
Why it matters: the architecture already treats recall and buffer independence as contracts.
Memory for the current delay subject is created during preparation. Processing, parameter installation, tail inspection and reset stay inside the real-time boundary.
Why it matters: long delay memory does not justify allocating inside the audio callback.
The declared tail follows the prepared engine at 44.1, 48, 96 and 192 kHz and covers ring-out below the defined floor without an order-of-magnitude safety fiction.
Why it matters: a DAW can preserve the tail after input stops instead of truncating it.
The panel, control-less faceplate, theme and interactive-control manifest are generated together. The engine selection is a two-position Lush or Natural switch.
Why it matters: the shipped control surface can be checked against the approved visual contract.
No public result currently proves the finished Lush tail, Natural density, stereo delay voicing, preset quality, CPU target or listening acceptance.
Current boundary: foundation evidence is not a substitute for the sound.
03 How sound evidence will be earned
Recover constructed decay, density and stereo answers within fixed tolerances.
Use repeat renders and statistical corridors because external products vary across instances.
Compare the developing network without treating reference proximity as release approval.
Use concealed, level-matched packages across vocals, drums, synths and ambience.
A person approves the sound and its limits. A graph never releases the product by itself.
04 Current position
VoltageSpaces is in development, with no public build and no release date. Questions about the method, product definition or relevant reverb experience are welcome.
Direct contactTalk to VoltageSpaces