AVELUNE

Specification changelog

Chronological record of Draft Generation 1 specification status and intentional format changes.

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. Draft Generation 1 — current
  2. 2026-08-10 publishing cleanup
  3. Historical snapshot — 2026-08-10

Draft Generation 1 — current

The ALV1, ALA1, and current container documents are unfrozen normative drafts for the reference POC. They define the current conformance target, not a permanent compatibility promise. Breaking changes are permitted during 0.x development when they are intentional, documented, and accompanied by updated conformance vectors and implementations.

Encoder heuristics are non-normative. Search strategies, presets, rate control, scene-cut policy, and other encoder decisions may change without a format-generation change as long as emitted streams conform to the current draft.

  • Removed obsolete entropy mode 1. Draft Generation 1 accepts only raw mode 0 and canonical-uvarint static-rANS mode 2; canonical and independent decoders reject every other mode.

2026-08-10 publishing cleanup

  • Reframed the previously premature “1.0” snapshot as Draft Generation 1.

  • Clarified that no codec, container, or public API compatibility line is frozen yet.

  • Kept the ALV1/ALA1 byte identifiers as generation identifiers, not semantic-version promises.

Historical snapshot — 2026-08-10

An internal POC snapshot was originally labeled 1.0.0 and described as frozen. That label is superseded by the public 0.x development policy above. The historical release note is retained under docs/history/ for provenance only.