Install alembic with Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• abcconvert
• abcdiff
• abcecho
• abcechobounds
• abcls
• abcstitcher
• abctree

Project history

Alembic was jointly developed by Sony Pictures Imageworks and Lucasfilm/Industrial Light & Magic. The official site describes it as an application-independent representation of baked geometric results, explicitly not a dependency graph, rig format, asset manager, or native scene-file replacement.

The official updates page says joint development was announced at SIGGRAPH 2010 and Alembic 1.0 was released publicly at SIGGRAPH 2011. The 1.0 announcement emphasized production-scale animated data exchange, automatic data de-duplication, C++ and Python code, HDF5/OpenEXR-era dependencies, and a BSD license.

Alembic 1.1 in 2012 added Python API bindings, lights, materials, collections, and performance fixes. Later NEWS entries show a long maintenance life focused on CMake, Python bindings, Imath/OpenEXR transitions, Ogawa storage robustness, Windows and mingw portability, fuzzing fixes, and ABI/package integration details.

Adoption history

The official 2012 update says ILM used Alembic on The Avengers and Sony Pictures Imageworks used it on Men in Black 3, The Amazing Spider-Man, and Hotel Transylvania. It also names Autodesk, The Foundry, Solid Angle, Side Effects, Luxology, and Exocortex as vendors or plugin providers adding Alembic support.

The supplied package facts show broad distribution packaging across Homebrew, apk, Debian, Fedora, MacPorts, Nix, Arch, Ubuntu, and openSUSE. That is consistent with Alembic's role as both an end-user command suite and a build dependency for DCC, renderer, and pipeline software.

How it is used

Alembic packages usually expose command-line utilities such as `abcconvert`, `abcdiff`, `abcecho`, `abcechobounds`, `abcls`, `abcstitcher`, and `abctree`. Users and build systems also consume the C++ library, Python bindings, and plugins for host applications such as Maya.

Its core use is geometry caching and scene handoff: baking animated meshes, transforms, curves, points, cameras, and related data so downstream lighting, rendering, simulation, or review tools can read the results without needing the original procedural rig.

Why package nerds care

Alembic is package-nerd significant because it is infrastructure disguised as a media format. A distro package has to care about C++ ABI, CMake config files, Python bindings, optional HDF5 support, Imath/OpenEXR compatibility, renderer/DCC plugin toggles, and command-line utilities.

It is also a good example of film-industry open source becoming normal system dependency material. The old project site, generated docs, and GitHub repository together show the migration from studio-driven release announcements to ordinary long-tail open source maintenance.

Timeline

• 2010: Joint development announced at SIGGRAPH.
• 2011-08-09: Alembic 1.0 released publicly at SIGGRAPH.
• 2012-08-05: Alembic 1.1 announced after a year of industry adoption.
• 2021-04-17: Alembic 1.8.0 dropped ancient TR1 support and moved toward modern C++ expectations.
• 2023-09-25: Alembic 1.8.6 added CPack and mingw-related build fixes.
• 2025-03-20: Alembic 1.8.11 recorded CMake, Python binding, and Ogawa robustness fixes.

Related projects

• Alembic's README names Imath, HDF5, Boost/PyAlembic, Arnold, Pixar PRMan, and Autodesk Maya as build-time or optional integration surfaces.
• The project's history sits beside other studio-born open media infrastructure such as OpenEXR, OpenColorIO, OSL, and related Academy Software Foundation ecosystem components.

Sources

• http://docs.alembic.io/
• http://www.alembic.io/
• http://www.alembic.io/updates.html
• https://github.com/alembic/alembic/blob/master/NEWS.txt
• https://github.com/alembic/alembic/blob/master/README.txt
• source_facts.package-manager