Skip to content
Fluxx

DCC Bridges

Retired 2026-09-24 (ledger A12, the second pass). This page described a DCC bridge layer over a vault, a cloud product and a finish-track field under names since retired; its prior body is kept whole at 02_Working/Archive/Wiki_pre_second_pass_2026_09/technology/dcc-bridges.md. What follows is the bridge as decided, from 02_Working/CLI_Briefs/THE_ANSWER_3.md and Bridge/.

What crosses the bridge

One immutable take directory per take, closed by one rename: the manifest with checksums, the identity, the verdict, camera.usd in centimetres, lens.nk, the OpenTrackIO archive and every vendor’s native bytes. Beside it, a ProRes plate written by the collector, with the DP’s CDL and LUT as sidecars from the DIT. For a selected take, OpenEXR from the camera original when Fluxx holds it, a 2K version and the deliverable. Never FBX.

How the applications are driven

Fluxx Automate’s bridge services run beside the animation and compositing applications rather than inside them, hold a local connection to a plugin inside the application, inject code and receive telemetry, and detect a hung application by heartbeat and by update cadence so it can be killed and relaunched when it can no longer answer itself. A failed batch job resumes from the last verified good unit rather than from the start. This is the subject of the first of the two provisional filings, described as filed.

The tests that gate it

BT-3, camera.usd into Maya and Nuke, one hour; N-1, the Nuke normalisation radius; BT-4, the render deadline on the bench at quarter resolution; BT-5, the watcher on the NAS.

Cross-references

Audience visibility

industry, investor, vendor, counsel.