dovi_tool mit Homebrew, apk, Nix, pacman, scoop installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• dovi_tool

Projektgeschichte

The public GitHub repository was created in November 2020, with early 0.1.x releases appearing the same month. The README describes both the `dovi_tool` CLI and the `dolby_vision` crate hosted in the same repository; the C-compatible library is also known as `libdovi`.

Over time the tool grew from a Dolby Vision RPU utility into a broader HEVC and metadata toolbox. The README documents metadata commands such as `info`, `generate`, `editor`, `export`, and `plot`, plus stream-handling commands such as `convert`, `demux`, `mux`, `extract-rpu`, and `inject-rpu`.

Adoptionsgeschichte

dovi_tool became a foundation package in the hobbyist and professional Dolby Vision tooling ecosystem because it exposes low-level RPU and metadata operations that other scripts and workflows can build on. Its package metadata shows distribution through Homebrew, Alpine, Nix, Arch, and Scoop.

The release stream has remained active from 2020 through 2026, including 2.x releases in 2024, 2025, and 2026. That continuity matters for media workflows because Dolby Vision profile handling, HDR10+ interop, and container tooling are moving targets.

Wie es verwendet wird

Users call `dovi_tool` subcommands to inspect an RPU, generate metadata from Dolby Vision XML, generic JSON, HDR10+ JSON, or madVR measurements, edit binary RPUs according to JSON config, export metadata to JSON or CSV, and plot brightness or trim metadata.

For HEVC workflows, dovi_tool can convert RPU modes, discard enhancement layers, demux and mux streams, and extract or inject RPU data. It is commonly used directly by advanced users and indirectly by higher-level tools such as dovi_convert.

Warum Paket-Nerds sich dafür interessieren

dovi_tool is package-nerd significant because it is the low-level Swiss-army CLI for Dolby Vision metadata. Packaging it turns a specialized video-engineering capability into a normal installable command that can be scripted and depended on by other packages.

It also shows why Rust CLIs travel well through package managers: the core tool, Rust crate, and C-compatible library can serve shell users, Rust projects, and FFI consumers from the same source repository.

Zeitleiste

• 2020: Public GitHub repository is created and early 0.1.x releases are published.
• 2021: 0.2.0 and 0.3.0 releases expand the early release line.
• 2024: 2.1.x releases are published.
• 2025: 2.2.0 and 2.3.x releases continue active development.
• 2026: 2.3.2 is published and repository activity continues.

Related projects

• The `dolby_vision` crate and `libdovi` are library surfaces from the same repository.
• dovi_convert depends on dovi_tool for higher-level Profile 7 to Profile 8.1 conversion workflows.
• FFmpeg, MKVToolNix, HDR10+ metadata tools, and madVR measurement files are adjacent inputs or workflow companions named by the README.

Quellen

• https://github.com/quietvoid/dovi_tool
• https://api.github.com/repos/quietvoid/dovi_tool
• https://api.github.com/repos/quietvoid/dovi_tool/releases?per_page=100
• https://api.github.com/repos/quietvoid/dovi_tool/tags?per_page=100
• https://formulae.brew.sh/formula/dovi_tool