EncodingDB
GitHubRun a benchmark

Contribute results

Contribute your results.

Download the client and follow the launch steps for your system. Choose Small, Medium, Large, or Full; the client detects usable encoders and submits finished measurements automatically once you approve uploads.

Version 1.3.0-rc.5 is published. The downloads below are the packaged builds for the current server (protocol 7.1). Verify each file against the SHA-256 listed on the release page before running.

macOS (Apple Silicon)

Download for macOS (Apple Silicon)

EncodingDB-macOS-arm64.dmg

  1. Open the disk image and drag EncodingDB to Applications.
  2. Open EncodingDB from Applications; it launches the guided menu in Terminal.
  3. First launch blocked by macOS? Use the first-launch help under build details below.

Double-clickable app inside a disk image; opens the guided menu in Terminal. Ad-hoc signed (not Developer ID, not notarized), so the first launch may need “Open Anyway” in System Settings → Privacy & Security (see first-launch help below). Native arm64; the embedded runtime requires macOS 27 or later; Intel Macs remain unverified.

SHA-256 cc6c6503293c8f01b223e1fac9a5da56888352d39c5e777cf90d23acec8aa8c6

Windows (GUI)

Download for Windows (GUI)

encodingdb-client-windows.exe

  1. Run the downloaded file.
  2. Windows warns because the build is unsigned; verify the SHA-256 below before continuing.
  3. Choose a sweep size in the window and press Start.

No Authenticode signature, so SmartScreen may warn at first launch. The window exposes the same Small/Medium/Large/Full sweeps as the guided interface and recovers automatically from a cache folder protected against the current user.

SHA-256 2ec0a4bcb7d94af340e61a1837bfc9380b51b2dd60bbd1f48eb023dfa24c0379

Linux (x86-64)

Download for Linux (x86-64)

encodingdb-client-linux.tar.gz

  1. Unpack the archive anywhere you can write.
  2. Open a terminal in the extracted folder and run ./start.sh.
  3. The guided Terminal menu asks for a sweep size, then runs.

Unsigned archive; unpack it and run the launcher inside. Same guided flow; includes the command-line entry point for scripts.

SHA-256 b1a68a039ce78a6bc9718adbae99409865326ea8a8b3fc29e47aaa090ef0f4d8

1 · Choose a sweepSmall, Medium, Large, or Full — increasing coverage of canonical clips and presets. The client prints the plan (time and disk budget) before it encodes anything.
2 · Press startEncoders are detected on your machine; only usable ones are measured. You can review the numbers locally before anything leaves your machine.
3 · Approve uploads onceOne consent, then finished measurements submit automatically. An upload receipt means analysis is pending; results may be accepted, suspect and awaiting review, or rejected.
4 · Continue after an interruptionSweeps checkpoint as they go and queued uploads retry, so resuming the run finishes the work without re-encoding.
Build details, checksums, signing, and older releases

1.3.0-rc.5 signing and support

Per the current build chain: the macOS app is ad-hoc signed (not Developer ID, not notarized) on native arm64 and requires macOS 27 or later; the Windows executable carries no Authenticode signature; the Linux build is unsigned. Encoders were exercised per platform where shown — VideoToolbox on the Apple Silicon Mac, NVIDIA NVENC plus software encoders on the Windows and Linux hosts; Intel macOS, Intel QSV, and AMD AMF remain unproven. Release notes, checksums, and build evidence (1.3.0-rc.5)

First-launch help

macOS: the app is ad-hoc signed and not notarized, so the first open may be blocked. If you trust this source, open System Settings → Privacy & Security and choose “Open Anyway” — see Apple’s instructions for opening a blocked app. Nothing here asks you to disable Gatekeeper or clear the quarantine flag.

Windows: SmartScreen warns because the executable is unsigned. Verify the SHA-256 above first, and continue only if you trust the source; the page gives no bypass tool or automation.

Superseded packaged builds (1.3.0-rc.4)

The 1.3.0-rc.4 macOS build predates the preparation, retained-campaign storage, and resume repairs in 1.3.0-rc.5. The verified Windows and Linux binaries are unchanged in this release.

  • Windows GUI (rc.4) encodingdb-client-windows.exe · SHA-256 2ec0a4bcb7d94af340e61a1837bfc9380b51b2dd60bbd1f48eb023dfa24c0379
  • Windows console (rc.4) encodingdb-client-windows-console.exe · SHA-256 05189da160c876f812cd16ae228b76df50bac8925d5763bb3d49ea9f0e42a60e
  • macOS DMG (rc.4) EncodingDB-macOS-arm64.dmg · SHA-256 2ec29a38cf36920d8eb030de97113cd37c56373a277ddbd79e46d1b0336c36ef
  • Linux archive (rc.4) encodingdb-client-linux.tar.gz · SHA-256 b1a68a039ce78a6bc9718adbae99409865326ea8a8b3fc29e47aaa090ef0f4d8

Plain command-line builds (1.3.0-rc.1)

Protocol-compatible executables that predate the packaged apps; the macOS file is a bare extensionless executable.

Historical 1.2.0 (cannot submit)

The 1.2.0 downloads (client/0.2.0, protocol 7.0) remain reachable for reference, but they cannot submit to the server version shipped with this page. Treat them as archived, not as recommended downloads.

Advanced: source checkout and scripted CLI (optional)

Not the normal contribution path — the packaged apps do everything below. For automation or source builds, from a client checkout with its installed Python environment:

python -m client --codec libx264 --presets fast --no-submit

A seven-clip campaign with the same recipe:

python -m client --codec libx264 --presets fast --campaign full --no-submit

Publish a saved campaign without re-encoding, or measure and publish in one step:

python -m client --resume-campaign CAMPAIGN_ID --submit
python -m client --codec libx264 --presets fast --submit

Resume unfinished measurements or retry queued uploads:

python -m client --resume-campaign CAMPAIGN_ID --no-submit
python -m client --upload-only
python -m client --queue-status