Open format for vibration-aware software
A sound format built to be implemented, validated, compared, and shared cleanly
EEV, short for Energy Envelope Vibration, describes sound as behaviour unfolding through time rather than as a note label alone. The format organizes identity, context, global measurements, compact summaries, matrices, modes, and fine trajectories. This site helps a team separate the canonical contract, transport concerns, and what genuinely belongs in reader and writer code.
English by default
PHP + i18n
directly deployable
implementation-oriented
Where a team should begin
This site avoids dropping the raw repository on the reader all at once. It proposes a short reading path so a team can define a realistic implementation scope quickly.
1. Frame the contract
Read the Format page to understand sections, canonical order, transport variants, and the difference between tolerant reading and strict writing.
2. Fix the architecture
Read the Implementation page to separate container detection, text parsing, internal model, validation, export, and hashing.
3. Prepare the raw material
Read the Recording page and the resources to avoid a correct implementation built on useless or badly annotated recordings.
Canonical contract
The core work begins with the real v1 contract: known sections, writing order, modern fields, and the exact place of tolerated legacy variants.
Layer separation
The model must distinguish identity, global measurements, matrices, vectors, modes, peak tracks, and interpretive layers. Mixing them makes code fragile very quickly.
Export discipline
A reader can stay tolerant. A canonical writer must stay strict, readable, stable, and reproducible. That discipline is what makes the format trustworthy.