Avelune Draft Generation 1 Baseline profile
Normative Draft Generation 1 interoperability boundaries for Avelune video, audio, container, and compute backends.
View specification sourceSpecification navigation
Current draft
- Avelune specification drafts
- Avelune Draft Generation 1 Baseline profile
- ALV1 video bitstream — Draft Generation 1
- Avelune V1 — common integer and entropy coding
- Avelune container — Draft Generation 1 (header generation 1, minor 0)
- ALA1 audio bitstream — Draft Generation 1
- Avelune Draft Generation 1 conformance requirements
- Specification changelog
On this page
|
Warning
|
Draft status: experimental, unfrozen, and subject to incompatible change while the software is |
The current Draft Generation 1 baseline intentionally has a bounded surface rather than untested feature flags. It is an interoperability target for this POC, not a compatibility freeze.
The shared syntax is defined by common integer and entropy coding. Media packets are carried by the AVL packet envelope.
1. Video
-
codec: ALV1;
-
8-bit planar YUV 4:2:0;
-
even dimensions, at most 8192x8192 and at most 8192^2 luma pixels;
-
lossy and mathematically lossless (
qstep=1); -
at most four immutable dependencies per frame;
-
dependencies contained within indexed epochs;
-
color matrix/transfer/primaries/range/chroma-location metadata as defined by the V1 container.
Not in Baseline V1: 4:2:2, 4:4:4, 10/12-bit, alpha, spatial scalability, HDR-specific reconstruction transforms, or normative GPU requirements. Future profiles must be explicitly versioned/profiled so a Baseline decoder rejects rather than silently misinterprets them.
2. Audio
-
codec: ALA1;
-
48,000 Hz;
-
mono or stereo signed 16-bit PCM domain;
-
reversible stereo coupling available for stereo;
-
lossy and mathematically lossless (
qstep=1); -
no decoder priming/pre-skip.
3. Container
-
front-indexed Avelune Draft Generation 1 container;
-
microsecond timescale for reference muxer streams;
-
independently fetchable epochs suitable for HTTP Range streaming;
-
CRC-32C protected header, front index, packet headers, and payloads.
4. Compute backends
Conformance is defined only by decoded samples and container semantics. Scalar native Rust and scalar WASM are required implementation baselines for this project. SIMD, threads, WebGPU presentation, and WebGPU compute acceleration may be added without changing the bitstream so long as outputs remain conforming.