ADRs tagged rc4¶
Auto-generated by scripts/docs/generate-adr-by-tag.sh. Edit ADR Tags: lines to update.
19 ADR(s) carry this tag.
| ID | Title |
|---|---|
| ADR-1713 | Rust feature-extractor twins behind the unchanged C ABI (RC4 framework) |
| ADR-1852 | A new VMAFx C API generated from one definition, libvmaf as its compatibility layer, and VMAFx-named FFmpeg filters (RC4) |
| ADR-1897 | VMAFx ABI numbering before 1.0: additions take a patch bump and join the current minor's version node |
| ADR-1906 | VMAFx core API semantics: per-context logging, size negotiation, frame and model references |
| ADR-1929 | VMAFx device frames, fences and the import rule: the shared contract the backend lanes implement |
| ADR-2023 | VMAFx device frames on CUDA: one library stream per device, fences on it, release events recorded where the frame is released |
| ADR-2044 | VMAFx option groups generate every scoring surface, and the scoring API is a versioned contract |
| ADR-2073 | The provenance record is canonical JSON with one digest over the configuration and the scores, the library writes it into every report, and --verify-provenance re-runs it |
| ADR-2074 | VMAFx window scores: a completion thread per context, one pooling implementation, the window clock and the in-flight bound |
| ADR-2090 | Derive motion2 / motion3 frame by frame: final once the frame after is scored, the same statements as the flush |
| ADR-2091 | VMAFx device frames on SYCL: readers copy on the device behind the frame's ready event, the release waits on every reader |
| ADR-2092 | VMAFx device frames on HIP: one library stream per device copies every frame for the twins, dma-bufs as external memory, sync_file checked on the host |
| ADR-2094 | libvmaf.so.3 is a compat library on the exported VMAFx API; the engine compiles its libvmaf bodies under engine names, and backends keep theirs until their lanes land |
| ADR-2132 | HIP imports GL textures through EGL dma-buf export; the runtime's GL interop is not used |
| ADR-2133 | Device import takes 4:2:2 and 4:4:4: semi-planar NV16 / NV24 family and packed Y210 / Y410, one CPU reference, converted on the device |
| ADR-2167 | -qpfile on libx264 applies its offsets through quant_offsets |
| ADR-2349 | One metric definition drives the services, the generated dashboards and the observability package |
| ADR-2350 | The VMAFx platform keeps its state in PostgreSQL, scales on queue depth and generates its platform surfaces from a definition |
| ADR-2399 | SLO objectives, burn-rate windows and alert thresholds are chart values, rendered from one rule builder |