davinci-resolve-mcp 4.1.1 → 4.1.2
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 +57 -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,63 @@
|
|
|
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 v4.1.2 — the installer's healthy-branch test stops depending on a live Resolve
|
|
6
|
+
|
|
7
|
+
Test-only. No behaviour change to the server or the installer.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **`SetupExitStatusTests.test_a_working_install_still_reports_ready_and_exits_zero`
|
|
12
|
+
failed roughly once per full-suite run** while passing in isolation and on an
|
|
13
|
+
immediate re-run. It was not the shared-state bug class this repo has seen
|
|
14
|
+
before: it asserted the healthy branch by running the **real** probe, which
|
|
15
|
+
spawns a subprocess asking a live GUI application to answer over IPC within
|
|
16
|
+
10 seconds and returns `False, "Connection timed out"` if it does not.
|
|
17
|
+
Resolve can be mid-launch, showing a modal, loading a project, or simply slow
|
|
18
|
+
while the rest of the suite saturates the machine — none of which is a defect
|
|
19
|
+
in the installer, which is the only thing the test exists to catch.
|
|
20
|
+
|
|
21
|
+
What it actually guards — *a successful verification must print
|
|
22
|
+
`Environment ready!` and return 0* — is a property of `main()`'s reporting,
|
|
23
|
+
not of the host. It is now asserted against a **pinned** verification result,
|
|
24
|
+
so it is deterministic and runs everywhere, including on CI with no Resolve
|
|
25
|
+
installed. Its mirror (*a stated failure is never reported ready*) is pinned
|
|
26
|
+
the same way.
|
|
27
|
+
|
|
28
|
+
- **The live probe is still exercised, as an integration check**, by
|
|
29
|
+
`test_the_live_probe_agrees_with_the_summary`. It asserts the summary and
|
|
30
|
+
exit status **agree with whatever the probe said** — and skips, naming the
|
|
31
|
+
probe's own message, when the probe did not answer. It is not an assertion
|
|
32
|
+
that the probe succeeds, because that is not something a unit suite can
|
|
33
|
+
guarantee. A probe that answers and a summary that contradicts it still
|
|
34
|
+
fails, which is the regression that matters.
|
|
35
|
+
|
|
36
|
+
- **The skip gate admitted machines the test could not pass.**
|
|
37
|
+
`_resolve_is_installed()` checked only for a `fusionscript` library, but
|
|
38
|
+
`main()` sets `verification_failed` when `api_path` is falsy — printing
|
|
39
|
+
`Skipped — Resolve API path not detected` — *before* the probe runs. On a
|
|
40
|
+
machine with the app installed but no `Developer/Scripting` directory (Studio's
|
|
41
|
+
installer can omit that component; on Linux it may sit outside the defaults),
|
|
42
|
+
the test therefore failed **deterministically**, for a reason unrelated to
|
|
43
|
+
what it pins. The gate now requires both halves, and it expands `{user}` the
|
|
44
|
+
way `find_resolve_paths()` does.
|
|
45
|
+
|
|
46
|
+
### Guards
|
|
47
|
+
|
|
48
|
+
- Every reporting test in `SetupExitStatusTests` is re-run with
|
|
49
|
+
`verify_resolve_connection` booby-trapped to raise, so any test that reaches
|
|
50
|
+
a live Resolve — by dropping its pin, by letting discovery find the host's
|
|
51
|
+
install, or by being added without one — fails at authoring time instead of
|
|
52
|
+
once a fortnight in someone's suite run. Exactly one test is exempt, named in
|
|
53
|
+
`LIVE_TEST`.
|
|
54
|
+
- The ready assertion is re-asserted against a dead `RESOLVE_PATHS`, pinning
|
|
55
|
+
that the summary follows the verification result rather than the machine.
|
|
56
|
+
- A pinned verification is asserted to actually replace the probe rather than
|
|
57
|
+
shadow it, so pinning the wrong symbol cannot quietly reacquire the flake.
|
|
58
|
+
- The gate is asserted to reject a library with no API directory beside it.
|
|
59
|
+
|
|
60
|
+
All four fail when the defect they pin is reintroduced.
|
|
61
|
+
|
|
5
62
|
## What's New in v4.1.1 — drift detection stops comparing two different timelines
|
|
6
63
|
|
|
7
64
|
Reported by @V2arK (#224), with the root cause correctly diagnosed in the report.
|
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
|
-
> 本翻译对应 v4.1.
|
|
15
|
+
> 本翻译对应 v4.1.2 版 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
|
@@ -37,7 +37,7 @@ from src.utils.update_check import (
|
|
|
37
37
|
|
|
38
38
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
39
39
|
|
|
40
|
-
VERSION = "4.1.
|
|
40
|
+
VERSION = "4.1.2"
|
|
41
41
|
# Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
|
|
42
42
|
# Resolve's scripting bridge loads into newer interpreters on recent builds
|
|
43
43
|
# (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds
|
package/package.json
CHANGED
package/src/granular/common.py
CHANGED
|
@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
|
|
|
87
87
|
handlers=[logging.StreamHandler()],
|
|
88
88
|
)
|
|
89
89
|
|
|
90
|
-
VERSION = "4.1.
|
|
90
|
+
VERSION = "4.1.2"
|
|
91
91
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
92
92
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
93
93
|
logger.info(f"Detected platform: {get_platform()}")
|