davinci-resolve-mcp 2.70.1 → 2.70.2

package/CHANGELOG.md

@@ -2,6 +2,59 @@
 
 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.70.2
+
+The control panel could never reach the free edition, even with a perfectly
+healthy in-app bridge. Reported in issue #109 by @alpaolo.
+
+### The bug
+
+The panel runs as a separate process from the MCP server and has its own Resolve
+connector. That connector returned as soon as `import DaVinciResolveScript`
+failed:
+
+```python
+try:
+    import DaVinciResolveScript as dvr_script
+except Exception as exc:
+    return None, f"Resolve scripting API unavailable: {exc}"
+```
+
+On the free edition that import is exactly what fails — Blackmagic's module ships
+with the installer, not the App Store build, so there is no
+`Developer/Scripting/Modules` tree to import from. The panel returned there,
+before ever calling `connect_resolve`, whose entire purpose is that it accepts
+`None` in bridge mode:
+
+> `dvr_script` may be None in bridge mode: the bridge does not need Blackmagic's
+> module at all, which is precisely why it reaches editions the module cannot.
+
+So the reporter saw the bridge listening, the MCP server connected, and the panel
+insisting "Resolve unavailable" — all at the same time, all correct.
+
+`_try_connect` in `src/server.py` already carried this guard, with a comment
+recording the same diagnosis from when it bit the server. The panel's connector
+was missed. That makes it the third connector overlooked when a transport was
+added, after the network-scripting one in v2.64.0.
+
+### The fix
+
+The panel now consults the bridge first and treats both the environment setup and
+the module import as optional when it is enabled — the same ordering the MCP
+server uses.
+
+The not-connected message no longer assumes Studio. It used to send every reader
+to "open Resolve Studio with a project loaded", which is poor advice for a
+free-edition user, since free is the one edition external scripting refuses by
+design. It now names the fix that fits the situation, and says something
+different depending on whether the bridge is enabled.
+
+### Windows bridge: `%PROGRAMDATA%` now confirmed
+
+v2.70.1 shipped Windows script paths unverified. The #109 report was made on free
+21.0.1.11 with the bridge installed, listed and serving from `%PROGRAMDATA%`, so
+that half is now confirmed rather than assumed. `%APPDATA%` remains untested.
+
 ## What's New in v2.70.1
 
 Windows support for the free-edition in-app bridge, and the end of doctor.py's

package/README.md

@@ -1,6 +1,6 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.70.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.70.2-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)
@@ -57,11 +57,11 @@ interpreters are not detected, and the script silently never appears in the
 menu. A Lua canary is installed alongside so you can tell that apart from a
 wrong folder.
 
-Validated on free 21.0.3.7 and Studio 19.1.3.7, both macOS. **Windows paths were
-added in v2.70.1 (issue #106) and have not yet been confirmed on Windows
-hardware** — the installer targets the `%APPDATA%` and `%PROGRAMDATA%` script
-folders Blackmagic documents, but whether Resolve lists the bridge from them is
-unverified. Reports welcome.
+Validated on free 21.0.3.7 and Studio 19.1.3.7, both macOS. The Windows paths
+added in v2.70.1 (issue #106) shipped unverified; a report on free 21.0.1.11
+(issue #109) has since shown the bridge installing, listing and serving from
+`%PROGRAMDATA%` on Windows, so that path is now confirmed rather than assumed.
+`%APPDATA%` remains untested. Reports welcome.
 
 This is the documented in-app path, not a licence circumvention, but Blackmagic
 could close it — treat it as a supported-until-it-is-not tier. Loopback only,

package/docs/SKILL.md

@@ -33,11 +33,14 @@ work unchanged. Two things to know when diagnosing it:
   Lua canary, which always lists, so "Python not detected" is distinguishable
   from "wrong folder". The preflight is macOS-only — off macOS Resolve finds
   Python by other means, and running the check there was a false alarm (#106).
-- **Windows is unconfirmed.** The `%APPDATA%`/`%PROGRAMDATA%` script folders are
-  targeted as of v2.70.1, but no Windows machine has verified that Resolve lists
-  the bridge from them. If a user reports the menu entry missing on Windows, ask
-  whether the Lua canary lists — that separates "wrong folder" from "Python not
-  detected" there too.
+- **Windows: `%PROGRAMDATA%` confirmed, `%APPDATA%` still not.** Both script
+  folders have been targeted since v2.70.1; a free 21.0.1.11 report (#109) has
+  since shown Resolve listing and serving the bridge from `%PROGRAMDATA%`. If a
+  user reports the menu entry missing on Windows, ask whether the Lua canary
+  lists — that separates "wrong folder" from "Python not detected" there too.
+- The **control panel connects over the bridge too** (fixed in v2.70.2). It runs
+  as a separate process with its own connector, so a panel that reports "Resolve
+  unavailable" while tool calls work is a panel-side bug, not a broken bridge.
 - The in-Resolve runtime is a **copy taken at install time**. After changing the
   repository, re-run the installer and then ask the running bridge to reload —
   it re-imports from disk in place, so Resolve does not need restarting.

package/install.py

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

package/src/analysis_dashboard.py

@@ -11953,9 +11953,33 @@ def _serialize_resolve(func):
     return wrapper
 
 
+def _bridge_requested() -> bool:
+    """Has the operator asked for the in-app bridge?
+
+    Read at call time rather than at import, so a panel started before the
+    variable was set still honours it.
+    """
+    try:
+        from src.utils import resolve_bridge_client
+
+        return resolve_bridge_client.bridge_enabled()
+    except Exception:  # pragma: no cover - the client is optional
+        return False
+
+
 def _connect_resolve_read_only() -> Tuple[Any, Optional[str]]:
     global _RESOLVE_ENV_READY
     with _RESOLVE_API_LOCK:
+        # Blackmagic's module ships with the *installer*, not the App Store
+        # build, so a free-edition machine has no Developer/Scripting/Modules
+        # tree and both the environment setup and the import fail. Returning
+        # here made the control panel unreachable on exactly the configuration
+        # the bridge exists for: the MCP server connects fine over the bridge
+        # while the panel — a separate process with its own connector — reports
+        # "Resolve unavailable". `connect_resolve` accepts None in bridge mode,
+        # and this returned before ever calling it (server.py:_try_connect
+        # carries the same guard for the same reason).
+        bridge_on = _bridge_requested()
         # Environment + sys.path setup is pure overhead and never goes stale, so
         # run it once per process rather than on every connection.
         if not _RESOLVE_ENV_READY:
@@ -11968,20 +11992,41 @@ def _connect_resolve_read_only() -> Tuple[Any, Optional[str]]:
                         sys.path.append(candidate)
                 _RESOLVE_ENV_READY = True
             except Exception as exc:
-                return None, f"Resolve scripting API unavailable: {exc}"
+                if not bridge_on:
+                    return None, f"Resolve scripting API unavailable: {exc}"
+        dvr_script = None
         try:
-            import DaVinciResolveScript as dvr_script  # type: ignore
+            import DaVinciResolveScript as _dvr_script  # type: ignore
+
+            dvr_script = _dvr_script
         except Exception as exc:
-            return None, f"Resolve scripting API unavailable: {exc}"
+            if not bridge_on:
+                return None, f"Resolve scripting API unavailable: {exc}"
         try:
             resolve = connect_resolve(dvr_script)
         except Exception as exc:
             return None, f"Resolve connection failed: {exc}"
         if resolve is None:
-            return None, "DaVinci Resolve is not connected. Open Resolve Studio with a project loaded."
+            return None, _not_connected_message(bridge_on)
         return resolve, None
 
 
+def _not_connected_message(bridge_on: bool) -> str:
+    """Name the fix that applies, rather than assuming Studio.
+
+    The old text sent every reader to "open Resolve Studio", which is wrong
+    advice for a free-edition user — the edition external scripting refuses by
+    design, and the one the bridge exists to reach.
+    """
+    if bridge_on:
+        return ("The in-app bridge is enabled but not answering. In Resolve, run "
+                "Workspace > Scripts > resolve_bridge; launching Resolve cannot start it.")
+    return ("DaVinci Resolve is not connected. On Studio, enable Preferences > General > "
+            "'External scripting using' = Local. On the free edition, install the in-app "
+            "bridge, run Workspace > Scripts > resolve_bridge, and set "
+            "DAVINCI_RESOLVE_BRIDGE=1.")
+
+
 @_serialize_resolve
 def _current_resolve_project_id() -> Tuple[Optional[str], Optional[str]]:
     """(project_id, error) for the currently-open Resolve project.

package/src/granular/common.py

@@ -85,7 +85,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.70.1"
+VERSION = "2.70.2"
 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.70.1"
+VERSION = "2.70.2"
 
 import base64
 import os