davinci-resolve-mcp 2.86.3 → 2.86.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +32 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/install.py +1 -1
- package/package.json +1 -1
- package/src/granular/common.py +1 -1
- package/src/server.py +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,38 @@
|
|
|
2
2
|
|
|
3
3
|
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.
|
|
4
4
|
|
|
5
|
+
## What's New in v2.86.4
|
|
6
|
+
|
|
7
|
+
The issue #132 follow-up, which turned out not to be a tool bug at all. No
|
|
8
|
+
behavior changed in any tool.
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- **The skills told an assistant to "route the user to the UI" and stopped
|
|
13
|
+
there, so it invented the directions.** In issue #132 a user was sent hunting
|
|
14
|
+
for a retime dropdown "in the lower left of the clip"; the keyframe tray was
|
|
15
|
+
never mentioned. That direction exists nowhere in this repo — no skill, doc,
|
|
16
|
+
or ledger entry describes where any Resolve control sits. The assistant
|
|
17
|
+
improvised the handoff and delivered it in the same confident register as the
|
|
18
|
+
API facts around it, which had been measured, so the user had no way to tell
|
|
19
|
+
the two apart. `resolve-edit` now carries the rule: **never improvise UI
|
|
20
|
+
geography.** Name the operation, say you cannot see the user's screen, and
|
|
21
|
+
treat a UI pointer already written into a skill (the playback-frame-rate path
|
|
22
|
+
in `resolve-rough-cut`) as the only kind to quote — verbatim, never extended
|
|
23
|
+
from memory. Where no pointer exists, point at Blackmagic's manual for their
|
|
24
|
+
build rather than supplying one. `resolve-rough-cut` picks up the same guard
|
|
25
|
+
at its own UI handoff.
|
|
26
|
+
|
|
27
|
+
Deliberately **not** fixed by adding the correct location. This repo verifies
|
|
28
|
+
API behavior and has no mechanism to version-guard a UI claim — every
|
|
29
|
+
`api_truth` entry is stamped with the build it was measured on because
|
|
30
|
+
unstamped claims rot, and UI geography moves between builds, pages and
|
|
31
|
+
layouts with no drift guard that would catch it going stale. The reporter hit
|
|
32
|
+
this on Resolve 21; the validation machine here is Studio 19.1.3.7, so
|
|
33
|
+
confirming a location here and publishing it for 21 would be the exact move
|
|
34
|
+
v2.82.1 exists to correct. Thanks to @magwa101 for coming back with the
|
|
35
|
+
detail that relocated the bug.
|
|
36
|
+
|
|
5
37
|
## What's New in v2.86.3
|
|
6
38
|
|
|
7
39
|
A Simplified Chinese phrasing fix from the reviewer who asked for it when #122
|
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
English | [简体中文](README.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#server-modes)
|
package/README.zh-CN.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[English](README.md) | 简体中文
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#服务器模式)
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
[](https://www.python.org/downloads/)
|
|
13
13
|
[](https://opensource.org/licenses/MIT)
|
|
14
14
|
|
|
15
|
-
> 本翻译对应 v2.86.
|
|
15
|
+
> 本翻译对应 v2.86.4 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
package/install.py
CHANGED
|
@@ -36,7 +36,7 @@ from src.utils.update_check import (
|
|
|
36
36
|
|
|
37
37
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
38
38
|
|
|
39
|
-
VERSION = "2.86.
|
|
39
|
+
VERSION = "2.86.4"
|
|
40
40
|
# Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
|
|
41
41
|
# Resolve's scripting bridge loads into newer interpreters on recent builds
|
|
42
42
|
# (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds
|
package/package.json
CHANGED
package/src/granular/common.py
CHANGED
|
@@ -85,7 +85,7 @@ if not logging.getLogger().handlers:
|
|
|
85
85
|
handlers=[logging.StreamHandler()],
|
|
86
86
|
)
|
|
87
87
|
|
|
88
|
-
VERSION = "2.86.
|
|
88
|
+
VERSION = "2.86.4"
|
|
89
89
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
90
90
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
91
91
|
logger.info(f"Detected platform: {get_platform()}")
|