davinci-resolve-mcp 2.171.0 → 2.173.0

package/CHANGELOG.md

@@ -2,6 +2,43 @@
 
 Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
 
+## What's New in v2.173.0 — E118: Resolve's own OTIO exports re-conform
+
+### Fixed
+
+- **A Resolve OTIO export with generators could not conform.** Resolve's
+  OTIO writer emits a Solid Color as a `Clip` with a NULL `media_reference`
+  named after the generator (E117), which the parser read as a source reel —
+  `assemble_from_interchange` refused the turnover ("unmapped source reel:
+  Solid Color"). Generator clips — a null or `MissingReference` with a
+  generator name, or a proper OTIO `GeneratorReference` — now walk as BL legs
+  carrying `generatorName` (and the colour when a `GeneratorReference`
+  declares one), so the bridge authors generators. Render-verified on
+  19.1.3.7: the E110 fade-to-white conform, re-exported as OTIO and
+  re-conformed, plays its clip → generator fade 124 → 96 → 68 → 41 → 18 → 16
+  and holds 16 — black, because the OTIO writer carries no colour (E117),
+  which `verify_roundtrip` reports as `generatorColourNotInExport`.
+
+## What's New in v2.172.0 — E117: colour QC knows which writers are colour-blind
+
+### Fixed
+
+- **`verify_roundtrip` no longer fails a colour compare against a re-export
+  that cannot carry colour.** Measured on 19.1.3.7: Resolve's OTIO writer
+  emits a Solid Color as a `Clip` with a null `media_reference` and empty
+  `Resolve_OTIO` metadata — no colour anywhere (its FCP7 XML writer echoes
+  the colour as `input_1`). Pass `exportedFormat` (otio|edl|xml|drt): a
+  colour-blind export reports `generatorColourNotInExport` (like
+  `markersNotInExport`) instead of `generator-colour` failures; an XML
+  export keeps the strict compare. Without the format the compare stays
+  strict. Resolve's OTIO export is a permanent fixture.
+
+### Measured (filed in api-limitations)
+
+- `EXPORT_OTIO` writes generators as media-less clips named after the
+  generator with no parameters; `Cross Dissolve` transitions carry a
+  `transitionCustomCurvesKeyframes` 0→1 curve in `Resolve_OTIO` metadata.
+
 ## What's New in v2.171.0 — E114: audio-lane `-1` edges take their own lane's junctions
 
 ### Fixed

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-2.171.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.173.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-36%20(353%20full)-blue.svg)](#server-modes)

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-2.171.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.173.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-36%20(353%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
 [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-> 本翻译对应 v2.171.0 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v2.173.0 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
 
 一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
 

package/docs/reference/api-limitations.md

@@ -313,7 +313,7 @@ equivalent, blocking full automation.
 
 - **Object:** `MediaPool`
 - **Signature:** `(filePath.xml) -> Timeline`
-- **Behavior:** Resolve's FCP7 XML importer HONOURS a generatoritem's `fillcolor` parameter (measured on Studio 19.1.3.7, E110): a Premiere-shaped Color Matte (effectid Color, category Matte) and a Solid Color generatoritem, both with <red>/<green>/<blue>/<alpha> 0..255 values, imported as Solid Color items and rendered Y81 U90 V240 (red) and Y41 U240 V110 (blue) — exact BT.601 limited-range values for a 640x360 timeline. EXPORT_FCP_7_XML writes the fillcolor back (same 0..255 channels). EXPORT_DRT carries the colour as a 55-byte <EffectFiltersBA> on the Sm2TiGenerator: 8-byte header (version 2, length 47), a fixed 20-byte prefix, a flag byte, then big-endian uint16 A R G B (0xffff = full) plus a pad word, then a second, black colour record; only the ARGB words differed between the red and blue captures. The default generator has an EMPTY EffectFiltersBA. The same importer does NOT carry a TRANSITION's parameters: a `Dip to Color Dissolve` transitionitem with a white and with a red `color` parameter imported as `Dip To Color Dissolve` elements whose 37-byte EffectFiltersBA were byte-identical (defaults), and the transition rendered inert (luma flat through its window, the E66 law) — the dip colour stays GUI-only on 19.1.3.7 (measured, E111). The writer emits a Solid Color's colour as the FxPlug parameter `input_1` (effectid FxPlugWrapper:C18E8B62_…), not `fillcolor` — an authored EffectFiltersBA colour came back exactly (white, 128/64/191; E112).
+- **Behavior:** Resolve's FCP7 XML importer HONOURS a generatoritem's `fillcolor` parameter (measured on Studio 19.1.3.7, E110): a Premiere-shaped Color Matte (effectid Color, category Matte) and a Solid Color generatoritem, both with <red>/<green>/<blue>/<alpha> 0..255 values, imported as Solid Color items and rendered Y81 U90 V240 (red) and Y41 U240 V110 (blue) — exact BT.601 limited-range values for a 640x360 timeline. EXPORT_FCP_7_XML writes the fillcolor back (same 0..255 channels). EXPORT_DRT carries the colour as a 55-byte <EffectFiltersBA> on the Sm2TiGenerator: 8-byte header (version 2, length 47), a fixed 20-byte prefix, a flag byte, then big-endian uint16 A R G B (0xffff = full) plus a pad word, then a second, black colour record; only the ARGB words differed between the red and blue captures. The default generator has an EMPTY EffectFiltersBA. The same importer does NOT carry a TRANSITION's parameters: a `Dip to Color Dissolve` transitionitem with a white and with a red `color` parameter imported as `Dip To Color Dissolve` elements whose 37-byte EffectFiltersBA were byte-identical (defaults), and the transition rendered inert (luma flat through its window, the E66 law) — the dip colour stays GUI-only on 19.1.3.7 (measured, E111). The writer emits a Solid Color's colour as the FxPlug parameter `input_1` (effectid FxPlugWrapper:C18E8B62_…), not `fillcolor` — an authored EffectFiltersBA colour came back exactly (white, 128/64/191; E112). The OTIO writer CANNOT: EXPORT_OTIO emits a Solid Color as a Clip.2 named 'Solid Color' with a NULL media_reference, metadata {"Resolve_OTIO": {}} and a parameterless Transform effect — no colour anywhere (measured E117) — so only an XML re-export witnesses a generator colour (editorial.verify_roundtrip exportedFormat → generatorColourNotInExport). Such an OTIO export DOES re-conform through drt.assemble_from_interchange (E118): the media-less generator clips walk as black legs and the clip→generator fade renders 124→16 — black, the colour having been lost by the writer.
 - **Workaround / current handling:** Author fade-to-white / colour mattes by placing a Solid Color generator with that blob (drp-format placeGenerator `color`, drt.assemble elements[].color) — or carry an XMEML generatoritem fillcolor through editorial.parse_interchange; the bridge authors the coloured leg.
 - **Tags:** xml, import, generator, colour, export, drt
 

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.171.0"
+VERSION = "2.173.0"
 # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
 # Resolve's scripting bridge loads into newer interpreters on recent builds
 # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davinci-resolve-mcp",
-  "version": "2.171.0",
+  "version": "2.173.0",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/resolve-advanced/server/author-interchange.mjs

@@ -986,10 +986,20 @@ export function verifyRoundtrip(inputEvents, exportedEvents, opts = {}) {
   const colourKey = (c) => (c ? [c.r, c.g, c.b].map((v) => Math.round(v * 255)).join(',') : '0,0,0');
   const colourTol = 1 / 255 + 1e-9;
   const sameColour = (x, y) => ['r', 'g', 'b'].every((k) => Math.abs((x ? x[k] : 0) - (y ? y[k] : 0)) <= colourTol);
+  // Which writers can WITNESS a generator colour (measured, E112/E117):
+  // Resolve's FCP7 XML export echoes it (`input_1`); its OTIO export writes
+  // a Solid Color as a Clip with a NULL media_reference and empty metadata —
+  // no colour anywhere — and an EDL/DRT re-export carries none either. A
+  // colour compare against such an export can only ever "fail", so it is
+  // reported as generatorColourNotInExport instead (like markersNotInExport).
+  const exportedFormat = String(opts.exportedFormat || '').toLowerCase();
+  const colourCapable = exportedFormat === '' || /^(xml|xmeml|fcp7|fcpxml)$/.test(exportedFormat);
+  let generatorColourNotInExport = false;
   {
     const inLegs = a0.filter((e) => isBlackSeg(e) && e.color);
+    if (inLegs.length && !colourCapable) generatorColourNotInExport = true;
     const exLegs = b0.filter((e) => isBlackSeg(e));
-    for (const leg of inLegs) {
+    for (const leg of generatorColourNotInExport ? [] : inLegs) {
       const partner = exLegs.find((x) => x.track === leg.track && x.recIn < leg.recOut && x.recOut > leg.recIn);
       generatorColours.compared += 1;
       if (!partner) {
@@ -1070,6 +1080,7 @@ export function verifyRoundtrip(inputEvents, exportedEvents, opts = {}) {
   return {
     pass: mismatches.length === 0, pairs: n, srcOffsets, mismatches, markers,
     ...(generatorColours.compared ? { generatorColours } : {}),
+    ...(generatorColourNotInExport ? { generatorColourNotInExport } : {}),
     ...(markersNotInExport ? { markersNotInExport } : {}),
     ...(blackSegments.input || blackSegments.exported ? { blackSegments } : {}),
     ...(fadeReshapedBoundaries.length ? { fadeReshapedBoundaries } : {}),

package/resolve-advanced/server/editorial.mjs

@@ -51,6 +51,7 @@ function evt(o) {
     track: o.track || 'V',
     ...(o.name !== undefined ? { name: o.name } : {}),
     ...(o.color !== undefined ? { color: o.color } : {}),
+    ...(o.generatorName !== undefined ? { generatorName: o.generatorName } : {}),
     source: o.source || 'UNKNOWN',
     srcIn: o.srcIn ?? null,
     srcOut: o.srcOut ?? null,
@@ -247,7 +248,25 @@ export function parseOTIO(otio, opts = {}) {
             reverse = false;
           }
         }
-        const src = (child.media_reference && (child.media_reference.target_url || child.media_reference.name)) || child.name || 'UNKNOWN';
+        const mref = child.media_reference || null;
+        const mrefSchema = String((mref && mref.OTIO_SCHEMA) || '');
+        const clipName = String(child.name || '');
+        // GENERATOR clips (E118): Resolve's OTIO writer emits a Solid Color as
+        // a Clip with a NULL media_reference named after the generator
+        // (measured E117); OTIO proper uses a GeneratorReference. Neither
+        // is a source reel — they walk as BL legs (a colour, when a
+        // GeneratorReference carries one, rides along) so the bridge authors
+        // a generator instead of refusing the turnover as an unmapped reel.
+        const isGeneratorRef = /^GeneratorReference/.test(mrefSchema);
+        const isGeneratorClip = isGeneratorRef || ((!mref || /^MissingReference/.test(mrefSchema)) && /solid color|colou?r matte|^black$/i.test(clipName));
+        let genColor;
+        if (isGeneratorRef && mref.parameters && typeof mref.parameters === 'object') {
+          const pc = mref.parameters.color || mref.parameters.Color || mref.parameters.fillcolor || null;
+          if (pc && typeof pc === 'object' && pc.r != null) genColor = { r: Number(pc.r) || 0, g: Number(pc.g) || 0, b: Number(pc.b) || 0, a: pc.a != null ? Number(pc.a) : 1 };
+          else if (Array.isArray(pc) && pc.length >= 3) genColor = { r: Number(pc[0]) || 0, g: Number(pc[1]) || 0, b: Number(pc[2]) || 0, a: pc.length > 3 ? Number(pc[3]) : 1 };
+          if (genColor && genColor.r === 0 && genColor.g === 0 && genColor.b === 0) genColor = undefined;
+        }
+        const src = isGeneratorClip ? 'BL' : ((mref && (mref.target_url || mref.name)) || clipName || 'UNKNOWN');
         // CLIP markers belong to the ITEM, not the sequence — carried as
         // itemMarkers (frames CLIP-relative) so the bridge authors them as
         // Sm2TiItemLockableBlobs (E80). Track-level markers above remain
@@ -270,6 +289,8 @@ export function parseOTIO(otio, opts = {}) {
             reverse,
             transition: pendingTransition,
             itemMarkers: itemMarkers.length ? itemMarkers : undefined,
+            color: genColor,
+            generatorName: isGeneratorClip ? (clipName || (mref && mref.name) || 'Solid Color') : undefined,
             fps: rate,
           }),
         );

package/resolve-advanced/server/tools/editorial.mjs

@@ -86,7 +86,7 @@ const markerSchema = z.object({
 export const editorialTool = {
   name: 'editorial',
   description:
-    'Editorial integrity (Cluster E) — turnover interchange → normalized events → changelist + conform manifest with TIMING silent-lie guards (flattened retime / dropped J/L-cut audio / framerate-pulldown slip / reverse dropped / transition-handle starvation → flag, skip-not-fake). Report-only (gate: review). Actions: parse_interchange (EDL/OTIO/XMEML natively — incl. Resolve-written FCP7 -1 junction edges (paired in record order) + Solid Color / Color Matte generators carrying their `fillcolor` (BL legs with `color` → fade-to-white and colour mattes author, E110), XMEML audio-track transitionitems as audio cross-fades on numbered lanes A/A2/…, and CMX FROM/TO CLIP NAME comments over the generic AX reel — + AAF via pyaaf2 (flat sound/picture slots number A/A2/… and V/V2/… in slot order so separate beds keep their lanes; NestedScope layers keep layer numbering) + PRPROJ via gunzip+XML → normalized events incl. span-explicit transitions, BL fade legs, and freezes as zero-speed events (OTIO FreezeFrame, XMEML timeremap 0, PrProj in==out, AAF 0% motion effects); for AAF/PRPROJ pass the file PATH as content; AAF also returns per-sequence startTimecode/startFrame — build the timeline at THAT start, not the Resolve 01:00:00:00 default — and per-clip `geometry` for Avid transform effects), list_sequences (ONE offline picker entry point across xml/edl/otio/drt/drp/aaf/prproj → [{id,name,eventCount}], plus startTimecode/startFrame for AAF), convert_to_interchange (author OTIO/EDL/DRT Resolve CAN import from events or a parsed source; the EDL target writes CMX transition pairs incl. BL fades — the .prproj→Resolve conform bridge, no Premiere needed; editorial timing/transitions survive and per-clip effects/color do not. SPEED/REVERSE survive on the otio (LinearTimeWarp) and edl (M2) targets ONLY — this FLAT drt target flattens every retime to 100% forward and returns `flattened`/`flattenedCount` naming each event that lost one (`flattened` is always present on `drt`, empty when there were none); for a .drt that AUTHORS retimes/dissolves/multi-track/audio, use drt.assemble_from_interchange), turnover_changelist (diff old vs new → moved/retimed/trimmed/replaced/new/gone PLUS the junction diff: transition_added/transition_dropped/transition_changed with fade in/out or dissolve, outgoing/incoming, span and duration/type/pre-roll deltas — zero-length CMX carrier lines and the BL legs that carry fades fold into the junction diff instead of reading as gone/new sources; events pair by closest record position, consumed once, so a source cut twice at two speeds compares instance to instance; + timing flags incl. transition_dropped and dropped_split_audio on any A-track), conform_manifest (per-event assert: source resolved/handles/retime/reverse/TC-base; BL-aware — black legs need no source, fades no black-side handles, and a fade-out tail requirement lands on the picture source), marker_roundtrip (markers with provenance tags), verify_roundtrip (input events vs re-export events -> pass/mismatches + fitted per-source TC offsets + marker compare w/ markersNotInExport honesty flag; FADE-AWARE: BL/Solid-Color legs merge out as blackSegments and fade-window boundary reshapes are excused into fadeReshapedBoundaries instead of failing; RETIME-AWARE: speed/reverse compare pairwise — EXPORT_OTIO carries an authored Sm2TimeMap back as LinearTimeWarp (measured), so a flattened/lost retime fails as drift geometry alone cannot catch; AUDIO-AWARE: declared audio events compare (a video-only export such as EXPORT_EDL flags audioNotInExport instead of failing) (channel legs deduped, mismatches tagged trackType audio) while the mirrored-A1 export of a video-only turnover stays informational; COLOUR-AWARE: an input generator leg carrying a fillcolor (fade-to-white, colour matte) must come back on the same track over its span with the same colour — Resolve\'s FCP7 writer emits it — else generator-colour fails (generatorColours reports the compare); the conform QC loop-closer). Offline (AAF needs pyaaf2; live AAF/DRP import is on the Python davinci-resolve MCP).',
+    'Editorial integrity (Cluster E) — turnover interchange → normalized events → changelist + conform manifest with TIMING silent-lie guards (flattened retime / dropped J/L-cut audio / framerate-pulldown slip / reverse dropped / transition-handle starvation → flag, skip-not-fake). Report-only (gate: review). Actions: parse_interchange (EDL/OTIO/XMEML natively — incl. Resolve-written OTIO generator clips (a Solid Color is a Clip with a NULL media_reference; it walks as a BL leg with generatorName, and an OTIO GeneratorReference carries its colour) so Resolve\'s own OTIO exports re-conform, Resolve-written FCP7 -1 junction edges (paired in record order) + Solid Color / Color Matte generators carrying their `fillcolor` (BL legs with `color` → fade-to-white and colour mattes author, E110), XMEML audio-track transitionitems as audio cross-fades on numbered lanes A/A2/…, and CMX FROM/TO CLIP NAME comments over the generic AX reel — + AAF via pyaaf2 (flat sound/picture slots number A/A2/… and V/V2/… in slot order so separate beds keep their lanes; NestedScope layers keep layer numbering) + PRPROJ via gunzip+XML → normalized events incl. span-explicit transitions, BL fade legs, and freezes as zero-speed events (OTIO FreezeFrame, XMEML timeremap 0, PrProj in==out, AAF 0% motion effects); for AAF/PRPROJ pass the file PATH as content; AAF also returns per-sequence startTimecode/startFrame — build the timeline at THAT start, not the Resolve 01:00:00:00 default — and per-clip `geometry` for Avid transform effects), list_sequences (ONE offline picker entry point across xml/edl/otio/drt/drp/aaf/prproj → [{id,name,eventCount}], plus startTimecode/startFrame for AAF), convert_to_interchange (author OTIO/EDL/DRT Resolve CAN import from events or a parsed source; the EDL target writes CMX transition pairs incl. BL fades — the .prproj→Resolve conform bridge, no Premiere needed; editorial timing/transitions survive and per-clip effects/color do not. SPEED/REVERSE survive on the otio (LinearTimeWarp) and edl (M2) targets ONLY — this FLAT drt target flattens every retime to 100% forward and returns `flattened`/`flattenedCount` naming each event that lost one (`flattened` is always present on `drt`, empty when there were none); for a .drt that AUTHORS retimes/dissolves/multi-track/audio, use drt.assemble_from_interchange), turnover_changelist (diff old vs new → moved/retimed/trimmed/replaced/new/gone PLUS the junction diff: transition_added/transition_dropped/transition_changed with fade in/out or dissolve, outgoing/incoming, span and duration/type/pre-roll deltas — zero-length CMX carrier lines and the BL legs that carry fades fold into the junction diff instead of reading as gone/new sources; events pair by closest record position, consumed once, so a source cut twice at two speeds compares instance to instance; + timing flags incl. transition_dropped and dropped_split_audio on any A-track), conform_manifest (per-event assert: source resolved/handles/retime/reverse/TC-base; BL-aware — black legs need no source, fades no black-side handles, and a fade-out tail requirement lands on the picture source), marker_roundtrip (markers with provenance tags), verify_roundtrip (input events vs re-export events -> pass/mismatches + fitted per-source TC offsets + marker compare w/ markersNotInExport honesty flag; FADE-AWARE: BL/Solid-Color legs merge out as blackSegments and fade-window boundary reshapes are excused into fadeReshapedBoundaries instead of failing; RETIME-AWARE: speed/reverse compare pairwise — EXPORT_OTIO carries an authored Sm2TimeMap back as LinearTimeWarp (measured), so a flattened/lost retime fails as drift geometry alone cannot catch; AUDIO-AWARE: declared audio events compare (a video-only export such as EXPORT_EDL flags audioNotInExport instead of failing) (channel legs deduped, mismatches tagged trackType audio) while the mirrored-A1 export of a video-only turnover stays informational; COLOUR-AWARE: an input generator leg carrying a fillcolor (fade-to-white, colour matte) must come back on the same track over its span with the same colour — Resolve\'s FCP7 writer emits it — else generator-colour fails (generatorColours reports the compare) — pass exportedFormat: an OTIO/EDL re-export cannot carry colour (measured) and reports generatorColourNotInExport instead of failing; the conform QC loop-closer). Offline (AAF needs pyaaf2; live AAF/DRP import is on the Python davinci-resolve MCP).',
   async handler({ action, args }) {
     if (action === 'parse_interchange') {
       const p = parseSchema.parse(args);
@@ -158,6 +158,8 @@ export const editorialTool = {
         srcTol: z.number().optional(),
         sourceMap: z.record(z.object({ mediaFilePath: z.string() }).passthrough()).optional()
           .describe('The SAME reel→{mediaFilePath} map the assemble used — lets an EDL reel (CUTSRC) match the re-export\'s file basename (cut_src)'),
+        exportedFormat: z.string().optional()
+          .describe('Format of the re-export (otio|edl|xml|drt). Generator COLOUR can only be witnessed by an XML re-export (Resolve\'s OTIO/EDL writers carry none — measured); pass it so a colour compare against a colour-blind export reports generatorColourNotInExport instead of failing'),
       }).parse(args);
       // EDL reels vs exported basenames: derive the alias table from the
       // sourceMap that drove the assemble (the one authority linking them).
@@ -166,7 +168,7 @@ export const editorialTool = {
         const base = String(src.mediaFilePath).split('/').pop();
         if (base) sourceAliases[reel] = base;
       }
-      return verifyRoundtrip(p.input, p.exported, { recTol: p.recTol, srcTol: p.srcTol, sourceAliases });
+      return verifyRoundtrip(p.input, p.exported, { recTol: p.recTol, srcTol: p.srcTol, sourceAliases, exportedFormat: p.exportedFormat });
     }
     if (action === 'marker_roundtrip') {
       const p = markerSchema.parse(args);

package/src/granular/common.py

@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.171.0"
+VERSION = "2.173.0"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")

package/src/server.py

@@ -11,7 +11,7 @@ Usage:
     python src/server.py --full       # Start the 353-tool granular server instead
 """
 
-VERSION = "2.171.0"
+VERSION = "2.173.0"
 
 import base64
 import os

package/src/utils/api_truth.py

@@ -2841,7 +2841,17 @@ API_TRUTH: List[Dict[str, Any]] = [
                    "a Solid Color's colour as the FxPlug parameter `input_1` "
                    "(effectid FxPlugWrapper:C18E8B62_…), not `fillcolor` — an "
                    "authored EffectFiltersBA colour came back exactly (white, "
-                   "128/64/191; E112).",
+                   "128/64/191; E112). The OTIO writer CANNOT: EXPORT_OTIO "
+                   "emits a Solid Color as a Clip.2 named 'Solid Color' with a "
+                   "NULL media_reference, metadata {\"Resolve_OTIO\": {}} and a "
+                   "parameterless Transform effect — no colour anywhere "
+                   "(measured E117) — so only an XML re-export witnesses a "
+                   "generator colour (editorial.verify_roundtrip exportedFormat "
+                   "→ generatorColourNotInExport). Such an OTIO export DOES "
+                   "re-conform through drt.assemble_from_interchange (E118): the "
+                   "media-less generator clips walk as black legs and the "
+                   "clip→generator fade renders 124→16 — black, the colour "
+                   "having been lost by the writer.",
         "recommended": "Author fade-to-white / colour mattes by placing a "
                        "Solid Color generator with that blob "
                        "(drp-format placeGenerator `color`, drt.assemble "