BlueForest Studios
SYS-2026-004 · Editor onboarding · DaVinci Resolve

BlueCue: how we drive an edit

BlueCue connects DaVinci Resolve, Claude Code and our planning sheets. It isn't one fixed process: we pick the control method that fits the project, and timeline markers carry the notes either way.

Path · Resolve editMotion graphics · laterUpdated · Oct 2026
Ways to drive an edit2Claude + markers, or the AV Script sheet
Shared languageMarkersNotes and status live on the timeline
EngineClaudeClaude Code drives Resolve through its MCP server
ConsolePrototypeProject status and control in one screen

What BlueCue is

Every edit at BlueForest is shared between you and Claude. You make the picture decisions in Resolve. Claude builds assemblies, graphics and exports, and keeps the paperwork in sync. BlueCue is how the two of you talk: through markers on the timeline.

How much structure sits behind those markers depends on the project. Most edits don't need a planning sheet at all. Some do.

Claude + markers

Most edits

Claude builds the assembly, you leave notes as markers and timecodes, and Claude works through them. No sheet. Best for interview-led films, recruiting and brand videos, and quick turnarounds.

AV Script sheet

When it helps

Every planned shot is a row in a Google Sheet, pushed onto the timeline as a marker and synced back when it's placed. Best for shot-by-shot work like music videos and storyboarded spots.

Which one?

If the project…Use
Is built from interviews and found moments, so the story is found in the editClaude + markers
Has a storyboard with a fixed shot list that must all be accounted forAV Script
Needs a producer or client to track shot progress without opening ResolveAV Script
Is a short turnaround, or a cutdown of an existing editClaude + markers
Starts loose but grows a lot of moving partsStart with markers; Ammon may add a sheet
The project's CLAUDE.md says which mode it uses.

Claude reads that file on its own, so always open Claude Code in the project folder. If you're not sure which mode a project is in, ask Ammon before you cut.

Mode 1 · Claude + timeline markers

This loop was worked out on the R Brooks recruiting films. Every pass is the same, and a film typically goes around it six to eight times.

  • 1 · Claude builds the first assembly"Read the transcripts, pick the strongest quotes, build a 24p timeline with the standard track layout, and draft the title cards." You get faces on V1, interview audio on A3, graphics on V4 and ducked music on A2.Claude
  • 2 · You leave notes as blue markersPlay it down. Wherever something needs to change, drop a blue marker and type the note ("cut the umm", "title too late"). Then: "I added blue markers in <timeline>. Please work through them."You
  • 3 · You do the fine cuttingTrims, slides and swapping takes are yours. Interviews on V1 + A3, linked. B-roll on V2, always over someone talking. Leave V4 (graphics) and A2 (music) alone; Claude replaces them each pass.You
  • 4 · Claude re-times the graphics to your cut"I recut the voices and b-roll. Please update the graphics timing." Claude moves every card, lower third and exit to the words as they're now spoken, re-bakes the music duck, and reports any rule it can't meet. You decide each one.Claude
  • 5 · Give notes by timecode"Move the '<card>' title so it starts at 00:35:01 to cover the jump cut." Timecode notes are the fastest notes there are.You
  • 6 · Export and share"Export a 1080p H.265 10-bit version." Claude renders to Exports/ and checks the file. Drag it into Frame.io yourself (it's too big for Claude's upload), then ask Claude for the share link.Both

Who does what

You, in ResolveClaude
Picture edit: trims, slides, inserts, swapping takesAssembly, title cards, lower thirds, exits
B-roll placementConforming graphics and the music duck to your cut
Blue-marker notes and timecode notesWorking through your notes; flagging rule conflicts
Dragging the export into Frame.ioExport, file check, share link, thumbnail

Mode 2 · The AV Script sheet

When a project is planned shot by shot, every shot or asset is one row in a Google Sheet: the AV Script and Asset List. BlueCue pushes each row onto the timeline as a color-coded marker at its planned time, with the shot description in the marker note. You edit against those markers.

When a shot is cut in, you turn its marker Green. Sync writes Placed = TRUE back to the sheet, and the producer sees progress without opening Resolve.

Resolve timeline with one cyan marker per planned shot above the song on A1
After the push on a scratch timeline: one Cyan marker per planned shot, sitting on the song clock above the master track. Double-click a marker to read its note; leave its name alone.

The five ideas

Asset ID

Three-letter type plus three digits, e.g. BRL014. If a row has an ID, the shot is planned.

Type sets the color

The prefix decides the marker color. B-roll is a Cyan marker and a Teal clip.

Marker = plan

One marker per row, at the row's timecode. The markers are the edit map.

Green = placed

Only you turn a marker Green (or Mint), and only when the shot is on the timeline.

One-way flow

Shot definitions go sheet → Resolve. Only placement status comes back. Never re-plan inside Resolve.

The loop: plan → push → edit → mark Green → sync

StepWhat happens
PlanRead the sheet before you cut. VISUAL is the instruction; VOICE is the line or lyric the shot sits under. Timecodes are HH:MM:SS:FF; other formats are skipped.
PushOnce at the start, and again only if rows are added. One marker per row.
EditCut footage into each marker's span. Picture goes on V2, the asset track.
Mark GreenRight-click the marker → Color → Green. Don't tick Acquired or Placed by hand.
SyncAt the end of the session. Green markers become Placed = TRUE; moved markers update their timecodes.

Marker colors by asset type

PrefixTypeMarker
INTInterviewBlue
BRLB-rollCyan
DRGResolve graphicPurple
REMRemotion compFuchsia
AFXAfter EffectsPink
VOIVoiceoverLemon
MUS · SFXMusic · Sound effectLavender · Yellow
IMG · 3DG · MSCStill · 3D graphic · MiscSand · Cream · Cocoa
—PlacedGreen or Mint
Rules that bite.

Don't rename or delete markers; move them if the edit moves, and sync follows. One sheet per timeline (a cutdown gets its own). Sync is not undo: turning a marker back from Green doesn't un-place anything. If markers land an hour late, the timeline starts at 01:00:00:00. Tell Ammon instead of dragging them.

Day-1 setup

Do these once, in order, with Ammon nearby for the ones that need him.

  • GitHub invite accepted, repo clonedblueforest-studios/blueforest-bluecueBoth modes
  • Claude Code installed, DaVinci Resolve MCP configuredAmmon sets this up with you.Both modes
  • Resolve Studio: external scripting set to LocalPreferences → General → External scripting using → Local, then restart Resolve.Both modes
  • Open the project and confirm the timeline runs at 24 fpsBoth modes
  • Google libraries installed/usr/bin/python3 -m pip install --user -r requirements.txtAV Script
  • Google sign-in for the sheetsAmmon adds your Google account as a test user, then you run the one-time sign-in from SETUP_GUIDE.md Part 2. Your token lands in ~/.bluecue/, never in the repo.AV Script

How it's run

Everything goes through Claude Code, in plain words, with Resolve open on the project timeline. Read Claude's report every time: it lists what it skipped and why.

markers › I added blue markers in "Film 02 v3". Please work through them.
re-time › I recut the voices and b-roll. Please update the graphics timing.
push › Push the planned assets from the AV Script sheet to the timeline.
sync › Sync placement status from Resolve back to the sheet.
status › Which planned shots are not placed yet?

The BlueCue Console Prototype

We're building a console that shows a whole project at a glance and lets you control parts of it from one screen. Point it at a project folder and it checks every link in the chain: folder → NAS backup → Resolve → AV Sheet → Remotion → Claude. Each one lights green (connected), amber (reachable, not ready) or red (broken or missing).

Below the chain are panels for the project, Resolve (assets, bins, timelines), Remotion comps and Claude's context, plus a Claude panel that answers questions about the project, read-only by default.

Rough prototypeBlueCue Console prototype: a dark control-room screen with six status lights for folder, NAS, Resolve, AV sheet, Remotion and Claude, project panels, and a Claude chat panel
The rough prototype, open on A Second Chance (VID-2026-031). The look and the panels will change; it isn't part of your daily workflow yet.

Worked example: A Second Chance (AV Script mode)

Brianna jogs past a graveyard at night. An incantation wakes Gustav Mahler's gold-skeleton ghost. He spell-binds her into a two-world dance, graveyard and saturated studio, and drops back into his coffin at dawn with a wink. A music video is exactly the kind of shot-by-shot project the AV Script is for.

Song4:00.8F major · ~116 BPM
Sequences11The song sections
Planned shots47BRL001 to BRL047
Worlds3Graveyard · Studio · Coffin set

Song clock = video clock. Timeline zero is the first frame of the song master, so every sheet timecode is song time.

  • Reverse-trick shots: S4-04 (the rise) and S11-02b (the fall) were shot as falls. Play them backwards.
  • S11-02c is optional and has no timecode. It only gets a marker if you give it one.
  • Bridge orbit continuity: studio S10-02 sets the orbit direction and speed; graveyard S10-01 and S10-03 must match it.
  • Two Gustav looks: glued-on bones only in graveyard and coffin shots. Don't intercut a bones shot into a studio section.

Exercises

Do them in order. Ammon watches the first two.

  • Leave three marker notesOn a duplicate of any finished R Brooks timeline, drop three blue markers with notes, ask Claude to work through them, and read its report.Markers
  • Read the mapOpen the A Second Chance sheet and storyboard side by side. For S5-01 to S5-04, say the lyric, the world, and what the VFX flag means.AV Script
  • Push on a scratch timelineDuplicate the main timeline as TRAIN scratch, push markers, and confirm: count = planned rows, all Cyan, first marker at 0:00.AV Script
  • Place three shots, close the loopCut S1-01 to S1-03 into V2, turn the markers Green, sync, and confirm only those three rows show Placed = TRUE.AV Script
  • Break it on purposeMove a marker two seconds, sync, and watch the timecode update in the sheet. Then delete the scratch timeline.AV Script

Glossary

Blue markerA note to Claude on the timeline
AV ScriptThe optional shot-by-shot planning sheet
Asset trackV2, where placed picture goes
Push · SyncSheet → markers · markers → sheet
customDataHidden marker field holding the row key; never edit
BlairBlueForest's central database
ConsoleThe BlueCue project dashboard; a prototype for now
Next

Your first edit

Ammon tells you which mode your first project uses and walks the first pass with you.

Finish day-1 setup

The four "Both modes" items above, before your first session.

Do the exercises

Start with the marker notes exercise; it's the loop you'll use most.

Send your notes

Anything unclear on this page? Pin a note with ?review and export it to Ammon.