The global stop-motion record Stop Motion Database

camera

Dragonframe

Capture technique

Authoritative 8 sources on file ยท Confirmed against a primary source. Pending confirmation from Dragonframe.
Spotted an error? Suggest a correction โ†’

Definition

Industry-standard stop-motion animation software for Mac, Windows and Linux, widely used by major studios including LAIKA and Aardman Animations. Core workflow tools: live view from a connected camera for real-time composition; high-resolution frame capture; X-Sheet (exposure sheet) for timing notes and dope-sheet editing; audio track import and scrubbing for dialogue sync; vector drawing overlays and composition guides; reference layer compositing with chromakey. Hardware companions include the DDMX-512 lighting controller and the DMC-32 motion control board. Supported cameras include Canon EOS R series and DSLRs (5D Mark IV, 6D), Nikon Z series and most DSLRs, Sony Alpha A7/A9, Olympus OM-D, Panasonic Lumix and Fujifilm GFX medium format. Used in production on Kubo and the Two Strings, Isle of Dogs, Guillermo del Toro Pinocchio, Memoir of a Snail, Missing Link and Wallace and Gromit: Vengeance Most Fowl.

Overview

Dragonframe's camera support is a bounded, actively maintained list, not an open standard, and it keeps growing: the published list (checked 2026-07-07) now runs from Canon's newest EOS R1, R3, R5 Mark II and R6 Mark III down through the long-running 5D/6D/7D DSLR lines, Nikon's Z-series mirrorless and D-series DSLRs, Sony's Alpha/FX/ZV ranges, Fujifilm's X and GFX bodies, Olympus/OM System, Panasonic Lumix, Pentax, Leica SL, Sigma fp, cinema cameras from ARRI and Blackmagic, 360-degree bodies from Insta360 and Ricoh Theta, and Intel RealSense depth cameras -- alongside Ximea's xiQ/xiC/xiMu machine-vision line for rigs that need a fixed, uncompressed industrial feed rather than a consumer stills body. Two things gate whether a camera works at all: live view over USB (the manufacturer must expose tethered shooting, which is why Nikon's D3000/D3100 and most Canon EOS M bodies are excluded) and, for the highest-quality capture, RAW or high-resolution still transfer rather than a compressed HDMI feed.

Canon EOS bodies are Dragonframe's default recommendation -- large, exposure-simulated live view and mechanically smooth, repeatable capture matter more for stop motion than resolution or autofocus speed -- and Canon publishes a free stop-motion firmware for the R, RP, R5, R8, R100 and R6 Mark II that raises live view to 1920x1280 with focus peaking, built for animators judging focus frame by frame. Blackmagic Design support is the narrowest case in the list: only the original Cinema Camera and the Production Camera 4K connect directly, because they alone expose a Thunderbolt stream Dragonframe can pull a high-resolution image from; every later Blackmagic body has to go through an HDMI capture device instead, at video-assist rather than still-frame quality.

Beyond the software, Dragonframe's own hardware closes the loop between capture and motion. The DMC-32 motion-control coordinator is a 1U rack unit with 32 independent step/direction channels (200,000 steps/second max) for driving external stepper-motor drivers on camera slides, pan/tilt heads or puppet rigs, plus a built-in DMX512 output that can run up to 512 lighting channels from the same timeline, so a move and a lighting cue can be keyframed and played back together. The DDMX-512 is the lighting-only counterpart for stages that need programmable DMX control without motion hardware -- up to 512 channels over a standard 3-pin XLR DMX output (a 5-pin XLR adapter is also supported) when driven from Dragonframe 4 or 5, dropping to 99 channels on the older Dragonframe 3, plus relay and 5V-TTL logic outputs that are optically isolated from the host computer -- and a Bluetooth/USB handheld controller covers manual jogging and frame capture from the stage floor.

Dragonframe's public development-branch changelog (checked 2026-07-13) shows the software's underlying engine changing as well as its feature list: an entry reads "Replace OpenGL code with QRhi (Metal/D3D11/Vulkan)," a rendering-backend rewrite rather than a user-facing feature, alongside continued camera-list growth (Canon EOS C50 and R6 V, Panasonic S5D, autofocus support for Fujifilm bodies) and, on the lighting side, new DMX fixture definitions for working manufacturers including ARRI, Nanlite and Nanlux, plus sACN protocol support for DMX output over a network rather than only a physical XLR run. The dev branch's motion-control work has grown into its own topic -- see Arc: motion control and robotic arms in Dragonframe for Dragonframe's newest capability, driving six-axis Universal Robots arms rather than only simple stepper-motor rigs.

The same changelog adds Capture | Shoot Clean Pass..., a dedicated menu command for shooting a clean plate -- the bare set with no puppet or rig present -- directly from Dragonframe's own capture workflow rather than as an off-app improvisation. It formalises, inside the animation software itself, a step whose output feeds straight into After Effects compositing's Content-Aware Fill rig-removal pass.

In 2026 the Academy of Motion Picture Arts and Sciences recognised Dragonframe itself. Brothers Jamie Caliri and Dyami Caliri, who built the tool out of an in-house need while directing a United Airlines commercial called "The Dragon" and then turned it into a commercial product distributed by DZED Systems from 2008, each received a Scientific and Engineering Award at the Academy's annual Sci-Tech Awards ceremony (Academy Museum of Motion Pictures, 28 April 2026) "for the design, engineering and continuing development of the Dragonframe software suite." The Academy's own citation is itself a useful summary of what the software displaced: an integrated toolset that replaced fragmented, error-prone capture methods with a single precision workflow at production scale -- the same throughline as the DMC-32/DDMX-512 hardware and the Arc motion-control and X-Sheet features documented above.

A follow-up check of the same development-branch changelog (dragonframe.com/dev/, checked 2026-07-22) shows the branch has moved past the Shoot Clean Pass build into a new 2027.01 release cycle, adding a handful of small but concrete workflow and scripting refinements: new graphics for the Arc orbit-navigation tools, a +/- adjustment control on all point-of-view directions, and three Python API additions -- event callbacks now receive a full event object, an optional reference-layer parameter, and an optional DRAGONFRAME_PYTHONPATH environment variable for extending where Dragonframe looks for Python modules -- alongside a fix ensuring a shot's first exposure is always marked enabled. The parallel 2026.04 branch picked up a fix for the Arc workspace crashing when dragged between windows and a fix for a potential access error in NDI network-video output. None of this rises to a feature on the scale of the QRhi engine rewrite, but it shows Dragonframe's Python scripting surface -- long used by studios and hobbyists for camera control and custom tooling -- continuing to grow in the same dev cycle as Arc's robotic-arm support.

Workflow

  1. Connect a supported camera by USB (or an HDMI signal into a capture device for unsupported or cinema bodies) and confirm live view appears in the workspace.
  2. Frame the shot using live view with onion-skinning and exposure simulation, referencing the previous frame to judge motion increments.
  3. Log the shot in the X-Sheet: exposure count, camera-move cues and audio-phoneme timing, so the sheet stays a live record of what was actually captured.
  4. For a motorized move, key positions on the DMC-32's step/direction channels (or a compatible third-party rig) and preview the interpolated path before committing frames.
  5. Capture each frame at full resolution, using Canon's stop-motion firmware or the camera's native RAW/tethered mode where available for the sharpest live-view judgment.
  6. Export the finished sequence (image sequence or movie file) for compositing in After Effects, where rig removal and grading complete the shot.

Worked examples

Related

Techniquesstop motion / motion control / live view capture

Links