Install openvdb with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• nanovdb_print
• nanovdb_validate
• vdb_print

Project history

OpenVDB was developed at DreamWorks Animation, with the project site naming Ken Museth, Peter Cucka, Mihai Alden, and David Hill as primary original developers. DreamWorks released it to the open source community in August 2012 after using the underlying sparse-volume technology in feature-film production.

The original emphasis was efficient level-set storage and manipulation, but the public library expanded into a broader volume toolkit: tree-based sparse grids, file I/O, filtering, meshing, topology operations, Python bindings, and command-line inspection tools. NanoVDB later extended the ecosystem with a compact, GPU-friendly representation for read-only sparse volumes.

In October 2018 the Academy Software Foundation accepted OpenVDB as its first hosted project, moving governance from a studio-maintained open source release toward a neutral foundation home for film and animation infrastructure.

Adoption history

OpenVDB spread because it solved a production problem shared by many studios: dense 3D volumes are expensive to store, move, and render, while effects work often touches only a sparse subset of space. ASWF described it as an industry-standard technology for more detailed volumetric imagery such as water, clouds, ice, and liquid simulations.

The package became a common dependency in digital-content-creation and rendering stacks because tools can exchange volumes through VDB files instead of inventing private cache formats. The ASWF announcement cites adoption for feature-film effects at DreamWorks, and the project appears in package managers as both a development library and a set of utilities such as vdb_print and NanoVDB validators.

How it is used

Developers and technical directors use OpenVDB to create, read, transform, filter, combine, resample, and serialize sparse volumes. In package-manager form it is usually installed as a native library for DCC applications, renderers, simulation tools, converters, and pipeline scripts rather than as a standalone end-user application.

The command-line tools matter for pipeline debugging: package users can inspect VDB metadata and validate NanoVDB data without launching a full DCC program.

Why package nerds care

OpenVDB is a package-nerd classic because a specialized movie-studio data structure escaped into the general open source supply chain. It brings heavy C++ dependencies, ABI concerns, Python bindings, file-format compatibility, and graphics-pipeline expectations into ordinary distro and Homebrew packaging.

It also shows how VFX infrastructure packages mature: studio origin, open source release, broad toolchain adoption, and foundation governance under ASWF alongside projects such as OpenColorIO, OpenEXR, OpenTimelineIO, and Open Shading Language.

Timeline

• 2012-08-03: DreamWorks Animation announces the open source release of OpenVDB.
• 2018-10-23: ASWF announces OpenVDB as its first hosted project.
• 2020: NanoVDB is introduced as a compact GPU-oriented companion representation within the OpenVDB ecosystem.
• 2024: OpenVDB 12.0 relicenses the project from MPL-2.0 to Apache-2.0 after approval from major copyright holders.

Related projects

• OpenVDB is closely related to NanoVDB, Houdini-style volume workflows, renderers and simulation systems that consume VDB caches, ASWF infrastructure projects such as OpenEXR and OpenColorIO, and DCC applications that need a shared sparse-volume interchange format.

Sources

• https://artifacts.aswf.io/io/aswf/openvdb/DWA_News_2012_8_3_OpenVDB/1.0.0/DWA_News_2012_8_3_OpenVDB-1.0.0.pdf
• https://github.com/AcademySoftwareFoundation/openvdb
• https://www.aswf.io/news/sony-pictures-entertainment-sony-pictures-imageworks-and-warner-bros-join-academy-software-foundation-at-the-linux-foundation/
• https://www.openvdb.org/
• https://www.openvdb.org/about/