MIDI Layer
Why MIDI is the control surface, not the final output
Why preserving timing, velocity, phrase, and gesture before rendering matters for multi-modal interfaces.
Direct answer
Audio is playback. MIDI is control. VIBEnet uses MIDI-derived timing because it preserves pattern before a renderer turns that pattern into sound, motion, light, haptics, or trace behavior.
Key points
What to remember
- MIDI keeps timing, velocity, sustain, phrase, and gesture separate from the final sound.
- One pattern can become piano audio, visual pulse, route-strip motion, or future haptic rhythm.
- The playing is source truth; theory and metadata make the phrase retrievable.
Control before output
An audio file collapses pattern and rendering into a finished artifact. MIDI preserves what happened before rendering: note, timing, velocity, sustain, pause, accent, and phrase.
That difference matters because VIBEnet is not trying to make only one sound. It is trying to let one temporal pattern drive many renderers.
Body-time rather than factory-time
Most interface timing is square, repetitive, and easy to code. Human performance carries breath, lilt, suspension, recovery, and small timing decisions that are hard to fake after the fact.
VIBEnet treats those human-origin gestures as infrastructure. The renderer can simplify, layer, or translate them, but the source pattern remains protected.
The proof path
The browser proof currently starts with a scored reference run as a visual concept, then derives public control sidecars from the same sequence.
That is the moment the architecture becomes obvious: one pattern, one contract run, multiple renderers moving together.
Answer engine notes
Frequently asked questions
Why use MIDI instead of only audio?
MIDI preserves the timing and performance pattern before rendering. That makes it useful as a shared control source for audio, visuals, haptics, lights, and logs.
Does VIBEnet require every renderer to play music?
No. A renderer can express the same temporal pattern as motion, color, pulse, trace behavior, haptic rhythm, or structured output.
What is protected in the Soul Bank?
Protected source phrases, timing, performance metadata, and derivative render metadata stay governed as authored assets. Public demos can explain the pattern without exposing the private corpus.
Next read