How cinecert/asdcplib works
Project Type and Purpose
• Type: C++ Native Library + Command-Line Tool Suite
• Purpose: Parse, wrap/un-wrap, and manipulate SMPTE D-Cinema (ST 429) MXF files, IMF Essence Components (AS-02/ST 2067-5) and Dolby Vision PHDR tracks.
• Libraries Provided:
– libkumu (platform abstraction)
– libasdcp (ST 429 DCP + JPEG-2000)
– libas02 (ST 2067-5 IMF/AS-02)
– libphdr (Dolby Vision PHDR, optional)
File Structure
• Top-Level Build & CI:
– Autotools (configure.ac, Makefile.am, autogen.sh)
– CMake (CMakeLists.txt, README.cmake)
– Win32 Makefiles (win32/)
– CI workflows (.github/workflows/ci.yml, .gitlab-ci.yml)
• Registers:
– XML definitions under registers/ (Dolby, RDD47, etc.)
• Source Tree (src/):
– Core platform module: KM_* (.fileio, .log, .prng, .sha1, .xml, .mutex, .platform)
– Parsers & containers: KLV, MXF, MXFTypes, JP2K, JXS, MPEG, PCM, PHDR, ACES, MDD, Metadata, TimedText, ST2052, ST2095 PinkNoise
– High-level standards modules: AS_DCP_*.cpp/h, AS_02_*.cpp/h
– Utility generators & encoders: AtmosSyncChannel_*, SyncEncoder, WavFileWriter
– CLI tools: asdcp-*.cpp, as-02-*.cpp, kmfilegen.cpp, kmuuidgen.cpp, kmrandgen.cpp, wavesplit.cpp, blackwave.cpp, pinkwave.cpp, j2c-test.cpp, etc.
– Test harnesses & scripts (sh, pl)
README for Additional Insights
• Key features & intended users (D-Cinema & IMF toolchains).
• Build variations: Autotools vs. CMake vs. Win32.
• Libraries vs. executables.
• External dependencies (via m4 macros): libexpat, OpenSSL, Xerces.
Main Components
a. Build & CI Layer
– Autotools, CMake, Win32
– GitHub Actions / GitLab CI
b. External Dependencies
– Expat, OpenSSL, Xerces (XML parsing, cryptography)
c. Platform Abstraction (libkumu)
– File I/O, logging, threading, mutexes, PRNG, SHA-1, UUID, XML support
d. Core Format Modules
– Container & KLV: MXF, MXFTypes
– Essence Parsers/Streams: JP2K, JXS, MPEG, PCM, ACES codestream, PHDR, TimedText, PinkNoise
e. Standards Libraries
– libasdcp (ST 429 + JPEG-2000 DCP)
– libas02 (ST 2067-5 AS-02 IMF)
– libphdr (Dolby Vision PHDR)
f. Command-Line Tools
– asdcp-wrap, asdcp-unwrap, asdcp-info, asdcp-test, asdcp-util
– as-02-wrap, as-02-unwrap, as-02-info
– kmfilegen, kmuuidgen, kmrandgen, wavesplit, blackwave, pinkwave, j2c-test
g. Registers Loader
– On startup, XML registers are loaded into dictionaries used by container/metadata modules.
Relationships & Data Flow
• CLI tools → link against Standards Libs (libasdcp, libas02, libphdr)
• Standards Libs → use Core Format Modules + Registers
• Core Format Modules → depend on libkumu for platform services + external libs
• Build System → compiles all layers, orchestrates dependency resolution
• CI Pipelines → invoke build, run tests
Architectural Patterns & Design Principles
• Layered Architecture – clear separation: Platform → Format Parsers → Standards → CLI
• Modular Libraries – libkumu (foundation), libasdcp/libas02/libphdr (domain), CLI (presentation)
• Plugin-style extensions – optional AS-02 and PHDR components compiled separately
• Data-flow orientation – parsing pipelines for essence codestreams & sequences