INT DCP Baker v1.0 is a $20 macOS application developed by Meguro-based Interceptor Inc. The software allows video editors using Apple Silicon Macs running macOS 26 or later to format, write, and verify EXT2 and EXT3 distribution drives for digital cinema servers directly from a single window, bypassing the need for Linux machines or virtual environments.
Bridging the Filesystem Gap on macOS
Transferring a finished Digital Cinema Package (DCP) to a server-compatible drive has historically meant negotiating an awkward workflow hurdle. Digital cinema projection servers running on Doremi, Dolby, GDC, and Barco hardware rely on Linux file systems, specifically EXT2 or EXT3. Macs natively generate APFS or exFAT volumes. Simply copying a DCP folder onto a standard USB drive using macOS typically results in unreadable files on theater servers. Furthermore, partition structures matter just as much as the filesystem itself; projection hardware often expects an MBR (Master Boot Record) partition table rather than the GUID partition map applied automatically by macOS.
Post-production teams faced limited choices to bridge this gap. Engineers either maintained a dedicated Ubuntu machine, spun up a local Linux virtual machine, purchased costly commercial EXT drivers for macOS, or outsourced the drive preparation entirely. For a fast-turnaround festival delivery, those workarounds introduce unnecessary friction. Interceptor Inc., operating out of Meguro, Japan, built INT DCP Baker to solve this specific friction point within the macOS environment.
The Mechanics of Preparation and Baking
The application splits the workflow into two distinct stages: preparation and baking. During the preparation phase, users select their working folder, DCP asset, and target media. The software then generates a disk image configured precisely for cinematic distribution. According to the developer’s technical specification, this entails an MBR partition scheme, a Linux partition type of 0x83, a 128-byte inode size, and reserved blocks set strictly to 0 percent. Standard Linux file systems automatically reserve five percent of a volume for root processes—space that serves no purpose on a projection delivery drive and can crowd out massive feature-length packages.
Once the disk image is prepared, the bake stage writes the complete image file to the external media as raw data. The software subsequently reads back the written media, computes the resulting SHA hash, and compares it against the source image hash. This process generates an automated Baking Report containing the verification results. For post-production supervisors, attaching this verification report to a delivery email provides an audit trail if a screening venue later flags a corrupted drive. The modular design also allows teams to generate an image once and reuse it across multiple physical drives when duplicating a show for regional distribution.
Leveraging Apple’s Containerization Framework
Under the hood, INT DCP Baker avoids reinventing the wheel by leaning on native operating system tools released by Apple. The utility relies upon Apple’s containerization tooling, built directly on top of the Containerization framework that Apple open-sourced at WWDC 2025 and finalized as version 1.0.0 in June 2026 under an Apache 2.0 license. This framework runs lightweight Linux containers as isolated virtual machines on Apple Silicon chips, with the underlying container package providing native capabilities to construct and populate EXT file systems.
By utilizing this native framework, Interceptor bypasses the need for resource-heavy solutions like Docker Desktop, manually configured Ubuntu virtual machines, or proprietary kernel extensions. However, this architectural choice dictates the system requirements. Because Apple’s containerization utility is tied directly to modern macOS releases and Apple Silicon architecture, editors still operating on Intel-based Macs or running legacy operating systems cannot run the software. For facilities that have transitioned entirely to Apple Silicon over recent hardware upgrade cycles, this integration operates invisibly beneath a clean user interface.
Validation Limits and Market Alternatives
Interceptor reports that test media compiled through INT DCP Baker successfully mounted as EXT3 volumes in Ubuntu, cleared the DCP-o-matic validator, ingested cleanly via a Doremi DCP-2000 server, and matched source SHA hashes during post-write verification. While these specific test markers indicate strong baseline compatibility, field conditions vary wildly across legacy projection hardware, making internal theater testing a necessary final step for any critical release.
The developer maintains transparency regarding the software’s hard boundaries. INT DCP Baker does not grant general read-and-write EXT support to macOS as a whole; it cannot be used to mount and inspect incoming return drives from theaters. It also does not transcode, generate, or modify DCP content—the package must already exist via software suites like DaVinci Resolve Studio or DCP-o-matic. Because operations route through an intermediate disk image, users must budget extra storage overhead and rendering time, particularly when processing multi-gigabyte feature films onto slower USB drives.
While free utilities like DCP-o-matic Disk Writer offer cross-platform EXT2 writing capabilities, INT DCP Baker bundles MBR structuring, kino-optimized inode settings, multi-DCP storage, reusable disk images, and automated SHA verification into a unified interface priced at a single $20 purchase. For independent studios and post houses managing regular festival runs, eliminating terminal commands and auxiliary virtual machines streamlines the final delivery pipeline significantly.
