camera
Production notes and metadata in Dragonframe
Dragonframe
Definition
The set of Dragonframe tools -- the Notepad, and per-take/exposure/frame notes stored in a metadata text file -- that record why a take was shot, kept, or rejected, and hand that record on to post-production, distinct from the guide layers and X-Sheet tools that operate purely inside the shoot.
Overview
Before a shot leaves the stage, a crew accumulates decisions and rejections that a frame sequence alone doesn't carry: why take 4 was rejected, what a lighting change was for, which exposure was the safety take. Historically that record lived on a paper log sheet or in an animator's memory, and rarely survived the handoff to post-production intact. Dragonframe formalises it as software-native, exportable data: a scene-level Notepad for standing context on a shot or sequence, and, one point release later, notes attached directly to individual takes, exposures and frames, saved into a metadata text file that travels with the footage.
The same release round added two features that address a related but distinct problem -- a single setup serving more than one final deliverable. Alternate composition guide layers let an animator frame a shot against several crop or aspect-ratio targets at once, so one capture pass covers every delivery format instead of reshooting per crop. Reference images can be popped out into their own window, so a previous take stays visible for direct comparison while framing or relighting the next one, rather than toggling between a single embedded overlay and the live view.
On the motion-control side, the same round of updates gave Dragonframe's Arc integration (see Arc: motion control and robotic arms in Dragonframe) a non-destructive adjustment layer for nudging a saved robotic move without re-recording it, and a "time warp" tool that stretches or compresses a finished move's duration over time. Both let a crew revise a move after review without returning to the rig and re-keying it from nothing.
Read together, these are workflow tools rather than capture tools: none of them change what the camera records. Their job is to keep the reasoning behind each take, and the intent behind each move, attached to the shot as it crosses from the stage into editorial -- the same handoff problem that guide layers and the X-Sheet solve for framing and dialogue, applied instead to notes and metadata.
Workflow
- Before the shot, the DP or animator records standing context in the Notepad -- setup intent, lighting or continuity decisions, anything the next viewer of this shot needs to know that isn't visible in the frame.
- During the shoot, notes are logged directly against the take, exposure or frame they concern, so a rejected take carries its own reason for rejection instead of depending on a separate paper log or the crew's memory.
- If the shot has more than one final deliverable -- a different aspect ratio or crop -- the animator frames using the alternate composition guide layers so a single capture pass serves every version.
- If a robotic move needs revising after review, the crew applies the motion-control adjustment layer for a small correction, or the time-warp tool to change the move's duration, rather than re-recording the move from the rig.
- At handoff, the accumulated take, exposure and frame notes export as a metadata text file alongside the footage, giving post-production a paper trail for every take, accepted or rejected.