davinci-resolve-mcp 2.57.0 → 2.57.1

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 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.57.1
+
+Investigation outcome for community feature request #74 — no behavior change.
+
+- **Note** (issue #74) the DaVinci Resolve scripting API does not expose the
+  Source/Auto Track Selector, so there is no way to choose the destination track
+  when inserting Text+/titles/generators. Verified live on Resolve Studio 21.0.0:
+  no get/set for the selector exists; the `Insert*IntoTimeline` family takes no
+  `trackIndex` and always lands on V1; locking lower tracks makes the insert fail
+  rather than redirect; and titles/generators can't be relocated afterward (no
+  `MediaPoolItem`). Closed as won't-fix (API limitation).
+- **Documentation** recorded the limitation in the verified `api_truth` ledger
+  (query at runtime with `resolve_control api_truth "track"`) and in
+  `docs/reference/api-coverage.md`, with the supported alternative for
+  media-backed clips (`MediaPool.AppendToTimeline` clipInfo `trackIndex`, exposed
+  as `media_pool.append_to_timeline` `clip_infos`). Added a regression test.
+
 ## What's New in v2.57.0
 
 Community feature requests #72 and #73.

package/README.md

@@ -1,6 +1,6 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.57.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.57.1-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-34%20(341%20full)-blue.svg)](#server-modes)
@@ -168,3 +168,6 @@ Samuel Gursky (samgursky@gmail.com)
 
 - [@rgxdev](https://github.com/rgxdev) — configurable Media Pool inventory walk
   (exclude bins + inventory limit), [#69](https://github.com/samuelgursky/davinci-resolve-mcp/pull/69) (v2.53.0)
+- [@swayll](https://github.com/swayll) — Source Track Selector investigation
+  ([#74](https://github.com/samuelgursky/davinci-resolve-mcp/issues/74)); confirmed
+  + documented API limitation (v2.57.1)

package/docs/process/release-process.md

@@ -86,6 +86,17 @@ env RESOLVE_SCRIPT_API="/Library/Application Support/Blackmagic Design/DaVinci R
   venv/bin/python tests/live_v233_validation.py
 ```
 
+For Fusion comp changes (masks, Text+/title text), run the issue #73 harness,
+which creates a disposable Fusion-title project, exercises `add_fusion_mask` and
+`set_text_plus` / `get_text_plus`, and deletes the project:
+
+```bash
+env RESOLVE_SCRIPT_API="/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting" \
+  RESOLVE_SCRIPT_LIB="/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/Fusion/fusionscript.so" \
+  PYTHONPATH="/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules" \
+  venv/bin/python tests/live_fusion_mask_title_validation.py
+```
+
 One-off live harnesses are acceptable during review, but reusable coverage
 should live under `tests/`. Do not commit generated media or disposable project
 artifacts.

package/docs/reference/api-coverage.md

@@ -44,6 +44,19 @@ maps `shot_descriptions[shot_index]` onto Media Pool shot markers, and triggers
 metadata writeback for that clip. Works with any MCP client whose chat model
 is vision-capable; no `sampling/createMessage` support required.
 
+Some Edit-page behavior is simply not reachable through public scripting. The
+**Source/Auto Track Selector** (the patch panel that chooses which video track a
+clip lands on) has no get/set in the API, and the `Insert*IntoTimeline` family
+(titles, generators, OFX, Fusion comps) takes no `trackIndex` — they always drop
+onto the selector's current target (V1 in practice). Locking lower tracks does
+not redirect the insert; it just makes the insert fail. Titles and generators
+can't be relocated afterward either, since they have no `MediaPoolItem` for
+`AppendToTimeline`/`MoveClips` to act on. For media-backed clips you *can* target
+a track via `MediaPool.AppendToTimeline`'s clipInfo `trackIndex` (exposed as
+`media_pool.append_to_timeline` with `clip_infos`). This limitation is recorded
+in the verified `api_truth` ledger (query `resolve_control api_truth "track"`);
+see issue #74.
+
 | Class | Methods | Tools | Description |
 |-------|---------|-------|-------------|
 | Resolve | 22 | 22 | App control, pages, layout presets, render/burn-in presets, keyframe mode |

package/install.py

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

package/src/granular/common.py

@@ -80,7 +80,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.57.0"
+VERSION = "2.57.1"
 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 341-tool granular server instead
 """
 
-VERSION = "2.57.0"
+VERSION = "2.57.1"
 
 import base64
 import os

package/src/utils/api_truth.py

@@ -158,6 +158,28 @@ API_TRUTH: List[Dict[str, Any]] = [
                        "need a comp to operate on.",
         "tags": ["fusion", "timeline"],
     },
+    {
+        "symbol": "Source Track Selector / destination track for Insert*IntoTimeline",
+        "object": "Timeline",
+        "reality": "There is no API to read or set the Source/Auto Track Selector "
+                   "(the Edit-page patch panel that picks the destination track). "
+                   "InsertTitleIntoTimeline, InsertFusionTitleIntoTimeline, "
+                   "InsertGeneratorIntoTimeline, InsertFusionGeneratorIntoTimeline, "
+                   "InsertOFXGeneratorIntoTimeline and "
+                   "InsertFusionCompositionIntoTimeline take no trackIndex and "
+                   "always drop the clip on the selector's current target (V1 in "
+                   "practice). Locking lower video tracks does NOT redirect the "
+                   "insert — verified live on 21.0.0: locking V1 makes the insert "
+                   "FAIL rather than land on V2. Titles/generators also can't be "
+                   "moved afterward (no MediaPoolItem, so AppendToTimeline clipInfo "
+                   "and MoveClips don't apply).",
+        "recommended": "Accept the limitation for titles/generators (insert lands "
+                       "on V1). For clips that DO have a MediaPoolItem, target a "
+                       "track with MediaPool.AppendToTimeline's clipInfo 'trackIndex' "
+                       "instead (exposed as media_pool append_to_timeline clip_infos). "
+                       "See issue #74.",
+        "tags": ["missing-method", "timeline", "title", "generator", "track"],
+    },
     {
         "symbol": "subprocess inheriting stdin under the MCP stdio server",
         "object": "(server runtime)",