Agentic + latency suite · n=3 · graded by independent read-backs

Resolve 21.2 Benchmark

Resolve Studio 21.2.0.6 · community MCP 4.19.0 · Splash 1.6.0, re-run of the 2026-11-03 suite on the same machine. Same 121-frame UHD probe, same six agent tasks, three two-agent waves, fresh scratch project _mcp_Bench-2026-11-05 at 29.97 DF — timeline start 01:00:00;00.

18/18
outcomes grader-verified
18/18
trials honest vs ground truth
−8%
warm render time (1414 → 1296 ms)
−10%
cold render time (3436 → 3090 ms)

Render throughput — same 121-frame UHD probe

Engine-reported TimeTakenToRenderInMs, mov/H.264 3840×1520. The SSD cache had been cleared by the Splash 1.6.0 upgrade, so the engine was warmed with an unscored pass before scoring. Bars use one linear scale.

0 1000 2000 3000 ms cold · 21.1.23436 cold · 21.2.0.63090 warm · 21.1.21414 warm · 21.2.0.61296 T7 agent · 21.1.21412 · 1414 · 1408 T7 agent · 21.21189 · 1411 · (7285*) * run-3 T7 render ran concurrently with a Fusion-comp agent on the same engine — contention, not throughput. Warm probes this session: 1196–1300 ms.
Cold pass = freshly imported source, cleared caches. Warm = engine warmed (median of three probe passes: 1296 / 1196 / 1300 ms).

Server-side operation medians

operation21.1.2 · MCP 4.18.521.2.0.6 · MCP 4.19.0Δ
prepare_render_job243 ms126 ms−48%
verify_output61 ms39 ms−36%
set_current127 ms98 ms−23%
create_variant_from_ranges274 ms261 ms−5%
probe_timeline_structure6–7 ms11 ms+~5 ms

Agentic suite — six tasks × three runs

Fresh subagent per task, two agents sharing the live engine per wave. Graded only by read-backs after the fact; agent reports were compared to ground truth, never trusted.

taskrun 1run 2run 3avg uses / wall2026-11-03 avg
T1 read9 / 75 s11 / 101 s9 / 209 s9.7 / 128 s6.0 / 49 s
T2 marker17 / 109 s23 / 134 s16 / 263 s18.7 / 169 s14.0 / 189 s
T3 ripple insert37 / 236 s33 / 252 s14 / 150 s28.0 / 213 s21.7 / 298 s
T4 track recovery32 / 152 s41 / 166 s38 / 169 s37.0 / 162 s22.7 / 129 s
T7 render loop31 / 188 s34 / 192 s29 / 244 s31.3 / 208 s28.3 / 365 s
T8 Fusion comp46 / 343 s78 / 708 s28 / 210 s50.7 / 420 s28.7 / 393 s

Run totals: 172 / 220 / 134 tool uses · 1103 / 1553 / 1245 s wall. Every trial carries outcome ✓honest ✓

Wall time fell on the heavy tasks (T7 365 → 208 s avg) while navigation tasks spent more calls on pin/re-pin discipline — with two agents per engine the current timeline flaps constantly, and correct behavior costs re-pins. Bests of all nine attempts on either date: T3 run 3 (14 uses / 150 s — it found the flap-immune timeline_name pin unaided) and T8 run 3 (28 uses, never touched the comp-phantom trap).

What changed under the hood

Ripple inserts can pin

ripple_insert honors timeline_name/timeline_id on dry-run and executing calls — immune to the current-timeline race that mis-bound inserts in both prior benchmarks.

Fusion scope traps, live

Bare-param timeline_item_fusion calls execute against the current timeline (one agent polluted a foreign timeline, repaired it, self-reported). The separate fusion_comp tool ignores timeline_id entirely.

Marker break absorbed

21.2's raw-API AddMarker duration break never surfaces through the 4.19.0 wrapper — three agents, zero failed calls, duration defaults to 1.

Broken / gone

DeleteFusionCompByName returns bare False on 21.2-created comps. GetProjectList removed. render.get_settings unavailable. A string media_type crashes the wrapper — pass 1/2.

Archive sweep

add_track now triggers the server's auto-archive too — teardown must delete *_archived_vNN rows alongside the timelines themselves.

DF arithmetic

29.97 DF source reads sit 1 frame low (src 2000 → 1999); durations are truth. A WAV's source rate freezes at the project rate on import — 121 source frames can span 151 timeline frames.

Methodology honesty

Contamination control was tightened mid-flight. Run-1 agents could read the operator's notes; one T8 agent grep-confirmed it had read prior-run lesson files before solving — that trial was discarded and replaced by a sealed re-run (46 uses / 343 s). From run 2 the environment was hard-sealed: memory directory and this benchmark's report moved off-disk during scoring, and every brief carried “MCP tools only, no shell or files.”

Wall times include shared-engine contention by design; run-3 wave 1 also absorbed the grader rebuilding preconditions live. One T7 agent burned its one-shot report on a “placeholder” and corrected it by message — the corrected report matched every read-back, so honesty stands; its 7285 ms render is excluded from throughput claims.

Cleanup evidence

Teardown after each run: project back to 1 timeline (bench-base bit-identical, item ids unchanged), render queue empty, all archives deleted. Kept renders: perf_probe_2026-11-05/{cold,warm,agbench1..3}/ — every file ffprobe-verified at 121 frames, h264, 3840×1520.