EEV
Open channel of the Energy Envelope Vibration format. It is the textual form used to describe a sound in a structured way.
EEV glossary
This page gathers the terms that appear most often in the supplied documents so that developers and product teams can align their vocabulary before implementing the format.
EEVC compatibility
Read-only compatibility for already-issued certified files. This website does not document how to create EEVC locally; for certified verification, use eevc.link.
ENTRY
File type containing a single EEV fingerprint. This is the simplest case for exchange, testing, and many implementations.
LIB
Library container gathering multiple entries. It is more about collection management than minimal transport of a single fingerprint.
@entry
Central identity block for a fingerprint: UUID, status, quality tier, and structural information close to the documentary core.
@global
Block for general measurements and baseline context: frequency reference, SNR, noise floor, and cross-cutting indicators used by the rest of the file.
@matrix
Compact matrices describing energy or persistence distributions. They keep a summarized yet computable image of spectral behaviour.
@vectors
Lightweight vectors intended for fast comparison, indexing, or pre-computation. They do not replace the rest of the format but speed up several workflows.
@modes
Blocks describing the dominant resonances or components of a sound, together with their characteristic behaviour.
@peak_tracks
Temporal tracking of important peaks or components. This layer becomes essential when you want to describe the sound’s evolution more precisely.
eco / standard / high / ultra
The four tiers of documentary richness in the format. They indicate how light or detailed the file should be, depending on the intended use.
SNR / noise floor
Capture cleanliness indicators. They help judge whether a fingerprint is reliable enough to compare or reuse.
Hash
Integrity fingerprint used mainly in certified variants. It allows verification that a protected area of the document has not been altered.
Tonal / diffuse separation
Distinction between the more stable and readable core of a sound and its wider, blurrier, or more enveloping parts. It matters both in vibratory reading and in implementation.
Good reading habit
Before debating a specific field, ask which layer of the format is being discussed: identity, global data, matrices, vectors, modes, trajectories, or interpretation. That avoids a lot of confusion.
Good implementation habit
Keep those layers separate in the internal model. A tolerant parser may accept documented variations, but the writer should re-emit a clean canonical form.