AVELUNE

Avelune specification drafts

Index of Avelune Draft Generation 1 specification documents, historical experiments, and change discipline.

View specification source
Specification navigation

Current draft

  1. Avelune specification drafts
  2. Avelune Draft Generation 1 Baseline profile
  3. ALV1 video bitstream — Draft Generation 1
  4. Avelune V1 — common integer and entropy coding
  5. Avelune container — Draft Generation 1 (header generation 1, minor 0)
  6. ALA1 audio bitstream — Draft Generation 1
  7. Avelune Draft Generation 1 conformance requirements
  8. Specification changelog

History

  1. Avelune Audio Candidate 0.0
  2. Avelune Container Candidate 0.0
  3. Avelune Video Candidate 0.0
  4. Candidate conformance requirements
On this page
  1. Reading order
  2. Normative language and conventions
  3. Document status
  4. Change discipline

The normative draft documents in this directory define current decoded behavior. They are the source of truth when they disagree with an implementation. The project is still 0.x, so syntax, identifiers, constraints, and decoded semantics may change incompatibly when evidence supports a better design.

ALV1 and ALA1 mean Draft Generation 1. They do not mean the format has reached stable 1.0.

Reading order

  1. Start with the Baseline profile to understand the interoperability boundary.

  2. Read common integer and entropy coding, which is shared by both media codecs.

  3. Use the ALV1 video and ALA1 audio documents for decoded media semantics.

  4. Use the AVL container document for stream descriptors, packets, epochs, and byte-range access.

  5. Finish with the conformance requirements when implementing or validating a decoder.

Normative language and conventions

The key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY express requirement strength. All byte offsets and ranges are zero-based. Half-open ranges use [start,end) notation. Fixed-width integers are little-endian unless a structure explicitly says otherwise. Mathematical floor, division, and modulo behavior is stated explicitly where host-language integer behavior could differ.

The specification defines accepted syntax and decoded results. Encoder search, rate control, preset behavior, and other choices that do not affect conformance are non-normative unless explicitly stated.

Document status

Files prefixed 000- are historical experiments and are non-normative.

Change discipline

A format change is complete only when the normative draft, affected implementations, conformance vectors/tests, public docs, and spec/CHANGELOG.adoc agree. During the unstable phase, do not retain an inferior design solely to decode an earlier development artifact.

See ../docs/development/VERSIONING.adoc.