davinci-resolve-mcp 4.13.4 → 4.13.6

package/CHANGELOG.md

@@ -2,6 +2,55 @@
 
 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 v4.13.6 — `drt` downgrade stamps the real Resolve build
+
+### Fixed
+
+- **`drt(action='downgrade')` (`resolve-advanced/server/tools/drt.mjs`)**: the
+  `DbAppVer` stamp was built by padding `targetAppVersion` to four parts, so
+  `19.1.3` became `19.1.3.0`, a build no Resolve has ever written. The vendored
+  version registry already records the real stamps read from Resolve's own
+  exports (19 → `19.1.3.0007` / 14, 20 → `20.3.2.0009` / 15, 21 →
+  `21.0.0.0048` / 17), and the vendored retarget path used them, so the two
+  re-stamp paths disagreed in every XML member. `DbPrjVer` now comes from an
+  explicit `targetProjectVersion`, then the registry row for that major, then
+  the known gate map. Resolve 20, which the map never had, now resolves to
+  schema 15 instead of throwing. `DbAppVer` comes from an explicit
+  `appVersionString`, then the registry row (only when its schema matches the
+  one being written), then the old padded form, which is now labelled and
+  warned about.
+- The result gains `projectVersionSource`, `appVersionSource`, `registryRow`
+  and, when a fallback was used, `warnings`.
+
+### Validation
+
+- 6 new cases in `resolve-advanced/test/drt-downgrade.test.mjs`. All 6 fail
+  against the previous `drt.mjs`. All `drt*.test.mjs` pass: 42/42.
+- Offline Python suite and the release static checks pass. Offline file
+  authoring only; no live Resolve import was run for this change.
+
+## What's New in v4.13.5 — Missing-media diagnosis finds Windows drive and UNC volumes
+
+Lands #293 from @AllastorV, case 4 of the Windows failures tracked in #278.
+With #291 and #292, his Windows 11 run of the offline suite is now clean.
+
+### Fixed
+
+- **Volume roots (`src/server.py`, `_media_path_volume_root` and
+  `_sanitize_media_path`)**: both helpers split on `os.sep`, so they followed
+  the OS running the server rather than the path's own form. Neither recognised
+  a Windows drive or UNC root. An unplugged card (`E:\DCIM\...`,
+  `\\nas\share\...`) never produced `volume_not_mounted`, and the relink plan
+  ran a full search instead of saying "mount the volume". On Windows a
+  `/Volumes/<name>` path came out as a single part. Both helpers now split on
+  `/` and `\`, and treat `X:\` and `\\server\share` as the volume root
+  alongside the existing `/Volumes/<name>` rule.
+- Sanitized paths keep the volume and hide the rest, in the path's own
+  separator: `E:\...\clip.mov`, `\\nas\share\...\clip.mov`. POSIX output is
+  unchanged.
+- New `MediaPathFormTests` use Windows-form fixtures and pure string checks, so
+  they run on every platform.
+
 ## What's New in v4.13.4 — Windows: the bridge claims its port exclusively
 
 Lands #292 from @AllastorV, case 2 of the Windows failures tracked in #278.

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-4.13.4-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.13.6-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-37%20(390%20full)-blue.svg)](#server-modes)

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-4.13.4-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.13.6-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-37%20(390%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)
 
-> 本翻译对应 v4.13.4 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v4.13.6 版 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 = "4.13.4"
+VERSION = "4.13.6"
 # 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": "4.13.4",
+  "version": "4.13.6",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

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

@@ -128,12 +128,80 @@ function resolveTargetProjectVersion({ targetProjectVersion, targetAppVersion })
   throw new Error('provide targetProjectVersion (int) or targetAppVersion (e.g. "19.1.3")');
 }
 
+/**
+ * The verified registry row (vendor/drt-format/resolve-versions.js) for a targetAppVersion, keyed
+ * by MAJOR version like the registry's own resolveVersion. null when the major has no row — the
+ * caller must then say it fell back, never borrow another version's stamp.
+ */
+function registryRowFor(targetAppVersion) {
+  if (targetAppVersion === undefined || targetAppVersion === null || targetAppVersion === '') return null;
+  const { VERSIONS } = drt().resolveVersions;
+  const row = VERSIONS[String(targetAppVersion).split('.')[0]];
+  return row || null;
+}
+
+/**
+ * The gate value and comment stamp a downgrade writes, and where each came from. Precedence:
+ * - <ProjectVersion>/DbPrjVer: explicit targetProjectVersion, else the registry row's dbPrjVer,
+ *   else PROJECT_VERSION_BY_APP (confirmed gate points with no full stamp, e.g. 18 → 11).
+ * - DbAppVer: explicit appVersionString, else the registry row's dbAppVer — only when the row's
+ *   dbPrjVer is the gate being written (a 19 build stamp beside DbPrjVer 11 would be a lie) —
+ *   else a PADDED fallback ("18.0" → "18.0.0.0") that names no real build and is labelled so.
+ */
+function resolveDowngradeStamp(p) {
+  const row = registryRowFor(p.targetAppVersion);
+  let targetPV;
+  let projectVersionSource;
+  if (Number.isInteger(p.targetProjectVersion)) {
+    targetPV = p.targetProjectVersion;
+    projectVersionSource = 'targetProjectVersion';
+  } else if (row) {
+    targetPV = Number(row.dbPrjVer);
+    projectVersionSource = 'registry';
+  } else {
+    targetPV = resolveTargetProjectVersion(p);
+    projectVersionSource = 'version-map';
+  }
+
+  const warnings = [];
+  let appVer;
+  let appVersionSource;
+  if (p.appVersionString) {
+    appVer = p.appVersionString;
+    appVersionSource = 'appVersionString';
+  } else if (row && Number(row.dbPrjVer) === targetPV) {
+    appVer = row.dbAppVer;
+    appVersionSource = 'registry';
+  } else if (p.targetAppVersion) {
+    const parts = String(p.targetAppVersion).split('.');
+    appVer = `${p.targetAppVersion}${'.0'.repeat(Math.max(0, 4 - parts.length))}`;
+    appVersionSource = 'padded-fallback';
+    warnings.push(
+      row
+        ? `DbAppVer "${appVer}" is padded, not a verified build: the registry row for Resolve ${row.marketing} is schema ${row.dbPrjVer}, not the ${targetPV} being written. Pass appVersionString to stamp a real build.`
+        : `DbAppVer "${appVer}" is padded, not a verified build: the registry has no row for Resolve ${parts[0]} (known: ${Object.values(drt().resolveVersions.VERSIONS).map((v) => v.marketing).join(', ')}). The gate (<ProjectVersion> ${targetPV}) is unaffected; pass appVersionString to stamp a real build.`,
+    );
+  } else {
+    appVer = `${targetPV}.0.0.0000`;
+    appVersionSource = 'placeholder';
+    warnings.push(`DbAppVer "${appVer}" is a placeholder (only targetProjectVersion was given). Pass targetAppVersion or appVersionString to stamp a real build.`);
+  }
+  return {
+    targetPV,
+    appVer,
+    projectVersionSource,
+    appVersionSource,
+    registryRow: row ? { marketing: row.marketing, dbAppVer: row.dbAppVer, dbPrjVer: row.dbPrjVer } : null,
+    warnings,
+  };
+}
+
 const downgradeSchema = z.object({
   drtPath: z.string().describe('Source .drt/.drp (e.g. exported from a newer Resolve)'),
   outputPath: z.string().describe('Where to write the downgraded file'),
   targetProjectVersion: z.number().int().optional().describe('On-disk <ProjectVersion> to stamp (overrides targetAppVersion)'),
-  targetAppVersion: z.string().optional().describe('Target Resolve app version, e.g. "19.1.3" — mapped to ProjectVersion'),
-  appVersionString: z.string().optional().describe('DbAppVer comment to stamp (default derived from targetAppVersion, else "<v>.0.0.0000")'),
+  targetAppVersion: z.string().optional().describe('Target Resolve app version, e.g. "19.1.3" — a major with a verified registry row (19, 20, 21) takes its DbAppVer/DbPrjVer from it; other majors use the ProjectVersion map'),
+  appVersionString: z.string().optional().describe('DbAppVer comment to stamp (overrides the registry; default = the verified registry build for targetAppVersion, else a padded fallback, labelled in appVersionSource)'),
 });
 
 /**
@@ -718,10 +786,8 @@ export const drtTool = {
     }
     if (action === 'downgrade') {
       const p = downgradeSchema.parse(args);
-      const targetPV = resolveTargetProjectVersion(p);
-      const appVer =
-        p.appVersionString ||
-        (p.targetAppVersion ? `${p.targetAppVersion}${'.0'.repeat(Math.max(0, 4 - String(p.targetAppVersion).split('.').length))}` : `${targetPV}.0.0.0000`);
+      const stamp = resolveDowngradeStamp(p);
+      const { targetPV, appVer } = stamp;
       const zip = await JSZip.loadAsync(await fs.readFile(p.drtPath));
       const out = new JSZip();
       let elementPatches = 0;
@@ -758,6 +824,10 @@ export const drtTool = {
         bytes: buf.length,
         targetProjectVersion: targetPV,
         appVersion: appVer,
+        projectVersionSource: stamp.projectVersionSource,
+        appVersionSource: stamp.appVersionSource,
+        registryRow: stamp.registryRow,
+        ...(stamp.warnings.length ? { warnings: stamp.warnings } : {}),
         projectVersionElementsPatched: elementPatches,
         commentStampsPatched: stampPatches,
         note: 'Stamp downgrade clears the import GATE only; verify content imports cleanly (fine clip corrections can drop across a multi-version gap).',

package/src/granular/common.py

@@ -91,7 +91,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "4.13.4"
+VERSION = "4.13.6"
 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 377-tool granular server instead
 """
 
-VERSION = "4.13.4"
+VERSION = "4.13.6"
 
 import base64
 import os
@@ -8455,29 +8455,48 @@ def _probe_interchange_roundtrip(proj, mp, tl, p: Dict[str, Any]):
     }
 
 
+_WINDOWS_DRIVE_PATH = re.compile(r"[A-Za-z]:[\\/]")
+
+
+def _media_path_parts(text: str) -> List[str]:
+    # Resolve stores a path the way the OS that wrote it gave it, and a project
+    # moves between machines, so split on both separators rather than `os.sep`:
+    # a macOS path stays a macOS path when the project opens on Windows (#278).
+    return [part for part in re.split(r"[\\/]", text) if part]
+
+
 def _sanitize_media_path(path: Any, *, keep_filename: bool = True) -> Optional[str]:
     if not path:
         return None
     text = str(path)
-    filename = os.path.basename(text.rstrip(os.sep))
-    parts = [part for part in text.split(os.sep) if part]
+    parts = _media_path_parts(text)
+    filename = parts[-1] if keep_filename and parts else ""
     if text.startswith("/Volumes/") and len(parts) >= 2:
-        root = f"/Volumes/{parts[1]}"
-        return f"{root}/.../{filename}" if keep_filename and filename else f"{root}/..."
-    if text.startswith(os.sep):
-        return f"/.../{filename}" if keep_filename and filename else "/..."
-    return f".../{filename}" if keep_filename and filename else "..."
+        prefix, sep = f"/Volumes/{parts[1]}/...", "/"
+    elif text.startswith("\\\\") and len(parts) >= 2:
+        prefix, sep = f"\\\\{parts[0]}\\{parts[1]}\\...", "\\"
+    elif _WINDOWS_DRIVE_PATH.match(text):
+        prefix, sep = f"{text[:2]}\\...", "\\"
+    elif text.startswith(("/", "\\")):
+        prefix, sep = "/...", "/"
+    else:
+        prefix, sep = "...", "/"
+    return f"{prefix}{sep}{filename}" if filename else prefix
 
 
 def _media_path_volume_root(path: Any) -> Optional[str]:
     if not path:
         return None
     text = str(path)
-    parts = [part for part in text.split(os.sep) if part]
+    parts = _media_path_parts(text)
     if text.startswith("/Volumes/") and len(parts) >= 2:
         return f"/Volumes/{parts[1]}"
-    if text.startswith(os.sep) and parts:
-        return os.sep + parts[0]
+    if text.startswith("\\\\") and len(parts) >= 2:
+        return f"\\\\{parts[0]}\\{parts[1]}"
+    if _WINDOWS_DRIVE_PATH.match(text):
+        return f"{text[:2]}\\"
+    if text.startswith(("/", "\\")) and parts:
+        return text[0] + parts[0]
     return None