EncodingDB 1.2.0 provides the compatible client/0.2.0 release for retained, authoritative V7 benchmark collection with the frozen seven-reference Test Suite v1.
Downloads
- macOS client
- Linux client
- Windows GUI and Windows console
- Frozen suite pack (1,506,890,018 bytes) and notices
- Checksums and exact source/build provenance
On macOS/Linux, make the downloaded client executable (chmod +x encodingdb-client-macos or chmod +x encodingdb-client-linux). The client acquires and verifies the frozen suite automatically; the exact pack may also be placed beside the executable. Per-binary runtime locks, release manifests, signing reports and smoke evidence are included as assets.
Verified source and checks
Built from main c001ddc73964d5ae0d1fe454fda9865eceaddb72, promoted through PR #13 after reviewed PR #12 integrated into beta at 027a382a98a10ae23dcbb345f04c2b03756f0ef0. These are fresh main-bound native builds, with original generated sidecars.
Main CI, all eleven release-preflight gates, and dependency audits passed. Native Linux/macOS/Windows model/build checks and CLI no-submit benchmarks executed. Clean-checkout deployment, all seven server-image source hashes, failed-pack rejection before rollout and public TLS corpus routing were exercised.
Scope and limitations
PL remains unavailable/null until a separate production calibration is approved. Existing metric bands, CRF defaults and source diagnostics are unchanged. The athletic-action proxy, letterboxing and added-grain limitations remain documented in the review report.
Clients are unsigned; macOS is not notarized and arm64 requires Rosetta for the Intel FFmpeg helper. Windows GUI and additional GPU combinations have not been interactively certified. The Windows console received native CLI smoke coverage; the GUI's skipped smoke is recorded explicitly.
The existing staging pack/runtime URLs remain required by the frozen locks and are retained. Production deployment evidence is recorded separately from software-build acceptance.
P910 deployment verification
P910 now runs server main b0f0bc7d12cb127c86a7c76979eb361398e293dd from PR #14, which fixes the production XPSNR frame-rate crash. Client binaries remain the verified c001ddc73964d5ae0d1fe454fda9865eceaddb72 builds above. All final main checks passed; all seven source hashes and backup/restore preparation were verified before rollout. The operator checkout and deployment wrapper are synchronized.
Production deployment evidence records the image, checks, backups, and four real client submissions. Two fresh submissions completed analysis on their first attempt after the repair. All four records remain SUSPECT, with VERIFIED artifact bytes awaiting metric-disagreement review; they are publicly browseable and unscored. This is a one-clip production check, not full seven-clip production certification or an accepted-evidence epoch declaration. PL calibration remains inactive.