davinci-resolve-mcp 2.104.3 → 2.104.5

package/CHANGELOG.md

@@ -2,6 +2,76 @@
 
 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.104.5
+
+The recent bug classes, generalized into guards — and the sweeps found the
+kwarg bug a second time.
+
+**PR #165's bug existed twice.** The positional-only bridge rule was guarded
+for src/server.py alone; sweeping ALL of src/ found
+`StartRendering(isInteractiveMode=...)` again in the render-deliver probe
+catalogue. Fixed, and the guard is rebuilt properly: it parses the Resolve
+method names out of the shipped API reference and flags keyword arguments on
+exactly those calls across the whole tree — which is what separates
+StartRendering from Popen without drowning in stdlib false positives.
+
+**Closing a project mid-render is now unreachable through this server.** The
+wedge documented in v2.104.0 (orphaned render, stuck IsRenderingInProgress,
+0% jobs, refused Quit) could still be triggered via project_manager.close or
+a disposable-project delete. `close` now refuses while a render is in
+progress — with the wedge named in the remediation — and accepts
+stop_render=true to stop, wait for the flag to clear, and close.
+delete_project_safely auto-stops first (deleting kills the render anyway;
+stopping is strictly better) and refuses when the flag will not clear, which
+is the already-wedged state where no delete ends well. Live-verified both
+paths on Studio 19.1.3.7: mid-render close refused, stop_render=true stopped
+and closed cleanly, no wedge.
+
+**Audits that came back clean, on the record:** the remaining default-ON
+analysis gates (marker plan is built unconditionally, vision is default-OFF
+behind a capability gate) cannot reproduce the cache-poisoning shape, and the
+Python tree carries no numeric-keyed hex tables of the kind that rotted in
+the Node encoders.
+
+PR #166's discarded-return guard fired on this release's own
+StopRendering call — third catch in three releases; the allowlist entry
+records that the helper verifies by polling the flag, stronger than the None
+the API returns.
+
+## What's New in v2.104.4
+
+Hardening pass over the classes the v2.104.2 batch exposed, live-verified on
+Studio 19.1.3.7.
+
+**set_title_text works on builds where SetProperty cannot.** On Studio 19.1.3
+a Text+ item rejects every title property key, so set_title_text failed while
+the item's Fusion comp accepted the same text all along. The setter now falls
+back to writing StyledText on the TextPlus tool — deliberately UNLOCKED, per
+the comp-lock render bug — and reports success only after reading the input
+back. Live-verified end to end: set via fallback, read via get_title_text,
+and a rendered frame confirms the text reaches the output (mean luma above
+black). bulk_set_title_text inherits the fallback. PR #166's discarded-return
+guard caught the fallback's bare SetInput during development — the allowlist
+entry records that the write is verified by readback, which is stronger than
+the bool Fusion doesn't return.
+
+**verify_output no longer flags deliberate short renders.** A single-frame
+capture tripped the mark-range-collapse warning, because the checker cannot
+distinguish a caller-chosen short range from a Resolve-rewritten one. Passing
+expected_frames / expected_duration_seconds matching the mark range now
+suppresses the collapse warning; an unstated short range still warns.
+
+**#171's scope measured: the internal-name override is FCP7-specific.** An
+OTIO export re-imported under a new timelineName creates a new timeline
+(measured 19.1.3.7), so the api_truth entry now says the override is an FCP7
+XML behavior, not a general import rule.
+
+**One more #167-class constant found and removed.** effect-encoder's exported
+"common double values" hex table — consumed by nothing — carried a '0.9'
+entry that decoded to 0.8. Deleted; the sweep found the remaining converters
+(editorial, media-inventory, the Python timecode helpers) already round
+correctly.
+
 ## What's New in v2.104.3
 
 Documentation follow-through on the v2.104.2 batch.

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-2.104.3-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.104.5-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.104.3-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.104.5-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.104.3 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v2.104.5 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
 
 一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
 

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.104.3"
+VERSION = "2.104.5"
 # 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.104.3",
+  "version": "2.104.5",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/resolve-advanced/vendor/drp-format/effect-encoder.js

@@ -180,16 +180,10 @@ function encodeFloat(value) {
   return buffer.toString('hex');
 }
 
-/**
- * Common double values in hex for quick reference
- */
-const DOUBLE_VALUES = {
-  '1.0': '000000000000f03f',
-  '1.1': '9a9999999999f13f',
-  '0.9': '9a9999999999e93f',
-  '2.0': '0000000000000040',
-  '0.5': '000000000000e03f',
-};
+// A "common double values in hex" reference table used to sit here. It was
+// consumed by nothing, and its '0.9' entry actually decoded to 0.8 — the same
+// hand-typed-hex rot that put 30000/1001 in drt.author's 23.976 slot
+// (issue #167). Encode with encodeDouble()/writeDoubleLE; never copy hex.
 
 /**
  * Build a protobuf field with double value
@@ -636,5 +630,4 @@ module.exports = {
   // Constants
   EFFECT_PARAMS,
   WIRE_TYPES,
-  DOUBLE_VALUES,
 };

package/src/granular/common.py

@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.104.3"
+VERSION = "2.104.5"
 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.104.3"
+VERSION = "2.104.5"
 
 import base64
 import os
@@ -5745,9 +5745,41 @@ def _timeline_set_title_text(tl, p: Dict[str, Any]) -> Dict[str, Any]:
                     "attempts": attempts,
                 }
 
+    # SetProperty exposes no title keys on every build (Text+ on Studio 19.1.3
+    # rejects all of them), while the item's Fusion comp carries the same text
+    # as the TextPlus tool's StyledText input and accepts writes there — the
+    # route get_title_text already reads. Deliberately a bare, UNLOCKED
+    # SetInput: the comp-lock render bug (api_truth / v2.98.5) eats writes
+    # wrapped in Comp.Lock(), and unlocked writes are the safe ones.
+    if not bool(p.get("as_styled_xml", p.get("styled", False))):
+        try:
+            if int(item.GetFusionCompCount() or 0) > 0:
+                comp = item.GetFusionCompByIndex(1)
+                tools = comp.GetToolList(False, "TextPlus") if comp else None
+                for tool_key in (tools or {}):
+                    tool = tools[tool_key]
+                    tool.SetInput("StyledText", text)
+                    confirmed = tool.GetInput("StyledText")
+                    rec = {"mode": "fusion_comp", "property_key": "StyledText",
+                           "success": confirmed == text}
+                    if confirmed != text:
+                        rec["readback"] = _ser(confirmed)
+                    attempts.append(rec)
+                    if confirmed == text:
+                        return {
+                            "success": True,
+                            "timeline_item_id": _safe_timeline_item_id(item),
+                            "property_key": "StyledText",
+                            "mode": "fusion_comp",
+                            "attempts": attempts,
+                        }
+        except Exception as exc:
+            attempts.append({"mode": "fusion_comp", "success": False, "error": str(exc)})
+
     return {
         "success": False,
-        "error": "SetProperty did not succeed; run title_property_scan, copy a real key from `properties`, "
+        "error": "SetProperty did not succeed and the Fusion-comp StyledText fallback found no "
+        "TextPlus tool to write; run title_property_scan, copy a real key from `properties`, "
         "and pass `property_key` (see `attempts` for diagnostics).",
         "attempts": attempts,
     }
@@ -17598,7 +17630,11 @@ def project_manager(action: str, params: Optional[Dict[str, Any]] = None) -> Dic
       create(name, media_location_path?) -> {success, name}
       load(name) -> {success}
       save() -> {success}
-      close() -> {success}
+      close(stop_render?) -> {success}
+        Refuses while a render is in progress — closing mid-render orphans the
+        render and wedges Resolve's pipeline until restart (stuck
+        IsRenderingInProgress, 0% jobs, refused Quit). stop_render=true stops
+        the render, waits for the flag to clear, then closes.
       delete(name) -> {success}
       import_project(path, name?) -> {success}
       export_project(name, path, with_stills_and_luts?) -> {success}
@@ -17702,7 +17738,33 @@ def project_manager(action: str, params: Optional[Dict[str, Any]] = None) -> Dic
         return {"success": bool(pm.SaveProject())}
     elif action == "close":
         proj = pm.GetCurrentProject()
-        return {"success": bool(pm.CloseProject(proj))} if proj else _err("No project open")
+        if not proj:
+            return _err("No project open")
+        # Closing mid-render orphans the render and wedges Resolve's pipeline
+        # (api_truth IsRenderingInProgress entry, measured live). Refuse by
+        # default; stop_render=true stops the render and waits before closing.
+        try:
+            rendering = bool(proj.IsRenderingInProgress())
+        except Exception:
+            rendering = False
+        if rendering:
+            if not p.get("stop_render"):
+                return _err(
+                    "A render is in progress on this project. Closing now would "
+                    "orphan the render and wedge Resolve's render pipeline — the "
+                    "stuck IsRenderingInProgress flag blocks every later render "
+                    "and refuses Quit until Resolve is restarted.",
+                    category="invalid_input",
+                    remediation=(
+                        "Wait for the render (poll render.get_job_status), or pass "
+                        "stop_render=true to stop it and close once the flag clears."
+                    ),
+                )
+            from src.utils.project_cleanup import stop_render_before_close
+            render_state = stop_render_before_close(proj)
+            if not render_state.get("safe"):
+                return _err(render_state["detail"], category="api_error")
+        return {"success": bool(pm.CloseProject(proj))}
     elif action == "delete":
         if not p.get("name"):
             return _err("delete requires name")
@@ -18833,7 +18895,9 @@ def render(action: str, params: Optional[Dict[str, Any]] = None) -> Dict[str, An
         cross-checks the job's timeline items (which read back their real
         positions): items before the timeline start and a mark range far
         smaller than the item extent both warn. Pass expected_frames or
-        expected_duration_seconds when you know what the render should hold.
+        expected_duration_seconds when you know what the render should hold —
+        a DELIBERATE short render (single-frame capture, excerpt) reads as a
+        collapse warning unless the stated expectation matches the mark range.
         Verify BEFORE deleting the job; deleted jobs carry no TargetDir.
       start(job_ids?, interactive?) -> {success}
       stop() -> {success}
@@ -18971,7 +19035,28 @@ def render(action: str, params: Optional[Dict[str, Any]] = None) -> Dict[str, An
                         "zero, issue #164). The items read back as placed; the "
                         "render is a stub."
                     )
+                caller_expected_frames = None
+                if p.get("expected_frames") is not None:
+                    try:
+                        caller_expected_frames = int(p["expected_frames"])
+                    except (TypeError, ValueError):
+                        caller_expected_frames = None
+                elif p.get("expected_duration_seconds") is not None and fps:
+                    try:
+                        caller_expected_frames = int(round(float(p["expected_duration_seconds"]) * fps))
+                    except (TypeError, ValueError):
+                        caller_expected_frames = None
+                # A caller who states the render SHOULD be this short (a
+                # deliberate single-frame or excerpt render) is not a collapse
+                # victim — the warning is for ranges Resolve rewrote, which the
+                # caller by definition did not expect.
+                intentional_short_range = (
+                    caller_expected_frames is not None
+                    and mark_frames is not None
+                    and abs(caller_expected_frames - mark_frames) <= 1
+                )
                 if (extent_lo is not None and mark_frames is not None
+                        and not intentional_short_range
                         and mark_frames < (extent_hi - extent_lo) * 0.5):
                     warnings.append(
                         f"The job's mark range ({mark_frames} frame(s)) is under "

package/src/utils/probe_catalogue.py

@@ -504,7 +504,9 @@ def _probe_render_to_disk(ctx):
     job = ctx.project.AddRenderJob()
     if not job:
         return False
-    ctx.project.StartRendering(job, isInteractiveMode=False)
+    # Positional: the free-edition bridge proxies Resolve calls positionally,
+    # and a keyword argument dies inside _BoundMethod (PR #165's bug class).
+    ctx.project.StartRendering(job, False)
     deadline = _t.monotonic() + 420
     while ctx.project.IsRenderingInProgress() and _t.monotonic() < deadline:
         _t.sleep(1)

package/src/utils/project_cleanup.py

@@ -64,6 +64,52 @@ def save_project_if_safe(pm: Any) -> Dict[str, Any]:
         return {"saved": False, "skipped": False, "project": name, "reason": repr(exc)}
 
 
+def stop_render_before_close(project: Any, *, wait_seconds: float = 8.0) -> Dict[str, Any]:
+    """Stop any in-progress render and wait for the flag to clear.
+
+    Closing or deleting a project while its render runs orphans the render and
+    wedges Resolve's whole pipeline: IsRenderingInProgress sticks True on every
+    subsequent project, new jobs sit at 0%, StartRendering starts returning
+    False, and Quit() is refused behind a modal (api_truth, measured live on
+    Studio 19.1.3.7). Returns {safe, was_rendering, waited_seconds, detail}.
+    A flag that stays True after StopRendering at idle is the stuck state —
+    only restarting Resolve clears it, so `safe` comes back False.
+    """
+    import time as _time
+
+    try:
+        rendering = bool(project.IsRenderingInProgress())
+    except Exception:
+        return {"safe": True, "was_rendering": False, "waited_seconds": 0.0,
+                "detail": "IsRenderingInProgress unavailable; proceeding"}
+    if not rendering:
+        return {"safe": True, "was_rendering": False, "waited_seconds": 0.0, "detail": ""}
+    try:
+        project.StopRendering()
+    except Exception:
+        pass
+    waited = 0.0
+    while waited < wait_seconds:
+        _time.sleep(0.5)
+        waited += 0.5
+        try:
+            if not project.IsRenderingInProgress():
+                return {"safe": True, "was_rendering": True,
+                        "waited_seconds": waited, "detail": "render stopped"}
+        except Exception:
+            break
+    return {
+        "safe": False, "was_rendering": True, "waited_seconds": waited,
+        "detail": (
+            "IsRenderingInProgress is still True after StopRendering and "
+            f"{waited:.0f}s — closing now would orphan the render and wedge "
+            "Resolve's render pipeline (stuck flag, 0% jobs, refused Quit). "
+            "If Resolve is idle at 0% CPU this is the already-stuck state and "
+            "only restarting Resolve clears it."
+        ),
+    }
+
+
 def delete_project_safely(
     pm: Any,
     name: str,
@@ -89,6 +135,20 @@ def delete_project_safely(
         except Exception:
             current = None
         if current == name:
+            # Deleting the current project kills its render anyway — stopping
+            # first is strictly better than orphaning it (the wedge documented
+            # in stop_render_before_close). Refuse only when the flag will not
+            # clear, which is the already-wedged state where the delete cannot
+            # end well either.
+            try:
+                project = pm.GetCurrentProject()
+            except Exception:
+                project = None
+            if project is not None:
+                render_state = stop_render_before_close(project)
+                if not render_state.get("safe"):
+                    return {"success": False, "attempts": 0, "leftover": name,
+                            "detail": render_state["detail"]}
             # CloseProject ALWAYS, and first. It is what releases the session's
             # lock on the project; switching away with LoadProject does not, and
             # DeleteProject then returns False permanently — retries never help.