davinci-resolve-mcp 4.10.0 → 4.10.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 +61 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/docs/process/release-process.md +9 -0
- package/install.py +1 -1
- package/package.json +1 -1
- package/resolve-advanced/vendor/drp-format/README.md +9 -1
- package/src/granular/common.py +1 -1
- package/src/server.py +1 -1
- package/src/utils/media_analysis.py +10 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,67 @@
|
|
|
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.10.2 — place_fusion_title measured on another build; the .drp harness says when it can't run
|
|
6
|
+
|
|
7
|
+
### Documentation
|
|
8
|
+
|
|
9
|
+
- **`place_fusion_title` is inert on the free edition 21.1.0 too.** The
|
|
10
|
+
harness's `RT_TITLE` project was built offline and imported into free
|
|
11
|
+
Resolve 21.1.0 through the Project Manager. A second into the title the
|
|
12
|
+
viewer was black, while a `place_generator` SMPTE Color Bar project built and
|
|
13
|
+
imported the same way rendered. `vendor/drp-format/README.md` now lists the
|
|
14
|
+
builds measured: inert on Studio 21.0.4.5 and free 21.1.0, with one
|
|
15
|
+
contributor-reported visible render on Studio 21.0.3.7 (#273 thread) that has
|
|
16
|
+
not been reproduced here. The harness keeps `place_fusion_title` as
|
|
17
|
+
known-broken.
|
|
18
|
+
- `docs/process/release-process.md`: the round-trip harness needs a Resolve
|
|
19
|
+
21.x host, and external scripting cannot drive the free edition. When no
|
|
20
|
+
21.x Studio is available, the release notes say the harness was not run.
|
|
21
|
+
|
|
22
|
+
### Changed
|
|
23
|
+
|
|
24
|
+
- `tests/live_drp_roundtrip_verification.py` stops with `CANNOT RUN` (exit 2)
|
|
25
|
+
on a Resolve older than 21, instead of reporting every case as a failure.
|
|
26
|
+
It authors the Resolve 21 project format, which 19.1.3.7 refuses at
|
|
27
|
+
`ImportProject` (all six cases failed there before any frame was checked).
|
|
28
|
+
|
|
29
|
+
### Validation
|
|
30
|
+
|
|
31
|
+
- No server code changed; offline suite green. The free 21.1.0 result is a
|
|
32
|
+
manual import and viewer check, not a harness run.
|
|
33
|
+
|
|
34
|
+
## What's New in v4.10.1 — the server's own tools stay first on PATH; portable runtime tests
|
|
35
|
+
|
|
36
|
+
### Fixed
|
|
37
|
+
|
|
38
|
+
- **A tool installed alongside the server could be shadowed by an older
|
|
39
|
+
system copy.** At import, `media_analysis` adds the interpreter's script
|
|
40
|
+
directory and the standard tool directories (`/opt/homebrew/bin`,
|
|
41
|
+
`/usr/local/bin`, …) to `PATH`, meaning to put the server's own venv first.
|
|
42
|
+
When the venv was already on `PATH` (an activated environment) but the
|
|
43
|
+
Homebrew directories were not, the missing directories were prepended in
|
|
44
|
+
front of it, so a `whisper` or `ffmpeg` in `/opt/homebrew/bin` won over the
|
|
45
|
+
one installed with the server. The venv's script directory now always comes
|
|
46
|
+
first; every other entry is kept, and the call stays idempotent. Reported
|
|
47
|
+
by @sidevconcept from a macOS validation run (#273); the existing test only
|
|
48
|
+
caught it on a host whose `PATH` lacked Homebrew.
|
|
49
|
+
|
|
50
|
+
### Tests
|
|
51
|
+
|
|
52
|
+
- `tests/test_child_process_text_encoding.py`: with `PATH` pinned to the venv
|
|
53
|
+
plus system directories, the venv stays first, whether it was listed first
|
|
54
|
+
or in the middle. Fails on v4.10.0.
|
|
55
|
+
- `tests/test_headless_runtime.py` and `tests/test_dashboard_source_review.py`
|
|
56
|
+
(@sidevconcept, #282, related to #278): the macOS process-table fixtures pin
|
|
57
|
+
their platform instead of following the test host, a launch-path assertion
|
|
58
|
+
normalizes separators, and the source-review test closes its cached SQLite
|
|
59
|
+
connection before its temporary directory is removed, which Windows
|
|
60
|
+
requires. Test-only.
|
|
61
|
+
|
|
62
|
+
### Validation
|
|
63
|
+
|
|
64
|
+
- Offline suite green. No Resolve scripting call changed.
|
|
65
|
+
|
|
5
66
|
## What's New in v4.10.0 — subtitle caption and preset editing in saved projects
|
|
6
67
|
|
|
7
68
|
### Added
|
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.10.
|
|
15
|
+
> 本翻译对应 v4.10.2 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
|
|
16
16
|
|
|
17
17
|
一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
|
|
18
18
|
|
|
@@ -153,6 +153,15 @@ that only diffs `GetStart()`/`GetDuration()` will call that green. Known-broken
|
|
|
153
153
|
cases are declared in the harness rather than skipped, so a fix reports
|
|
154
154
|
`UNEXPECTED PASS` and fails until the docs describing it are updated.
|
|
155
155
|
|
|
156
|
+
The harness needs a **Resolve 21.x host**: it authors the Resolve 21 project
|
|
157
|
+
format, which 19.x refuses at `ImportProject`, so on 19.x it stops with
|
|
158
|
+
`CANNOT RUN` (exit 2) instead of reporting every case as a failure. External
|
|
159
|
+
scripting is Studio-only, so it also cannot drive the free edition. When no
|
|
160
|
+
21.x Studio is available, say in the release notes that the harness was not
|
|
161
|
+
run and why; a manual import into the free edition (as done for
|
|
162
|
+
`place_fusion_title` on 21.1.0) is evidence for that one case, not a harness
|
|
163
|
+
pass.
|
|
164
|
+
|
|
156
165
|
The same rule generalises: **"the file round-trips" and "Resolve honours it" are
|
|
157
166
|
different claims.** Only a live import establishes the second one. Do not write
|
|
158
167
|
"verified live" in a doc unless a runnable command produced that result.
|
package/install.py
CHANGED
|
@@ -37,7 +37,7 @@ from src.utils.update_check import (
|
|
|
37
37
|
|
|
38
38
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
39
39
|
|
|
40
|
-
VERSION = "4.10.
|
|
40
|
+
VERSION = "4.10.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
|
@@ -53,7 +53,7 @@ and `.../resolve-authoring-completion.md`.
|
|
|
53
53
|
**Place elements (track-targeted — the #74 bypass, offline)**
|
|
54
54
|
| Action | What it does |
|
|
55
55
|
|---|---|
|
|
56
|
-
| `place_fusion_title` | ⚠️ **INERT on 21.0.4.5 — placed but not rendered, see below
|
|
56
|
+
| `place_fusion_title` | ⚠️ **INERT on Studio 21.0.4.5 and free 21.1.0 — placed but not rendered, see below** (one contributor-reported visible render on Studio 21.0.3.7). Text+ on a chosen track. Options: `text, font, style, size, vJustify, hJustify, color:{r,g,b}`, `trackIndex`, `startFrame`, `durationFrames` |
|
|
57
57
|
| `place_generator` | built-in generator (`generatorName`, e.g. "Solid Color") on a chosen track |
|
|
58
58
|
| `place_transition` | cross-dissolve at an abutting cut (`track`, `atFrame`, `durationFrames`) — clips need handle media |
|
|
59
59
|
|
|
@@ -145,6 +145,14 @@ Selector's current target (V1 in practice), which no API can read or set.
|
|
|
145
145
|
> only by text length) and DbId rewriting (the comp blobs contain no DbId references). Root cause
|
|
146
146
|
> open. Use the live nested-timeline route until this is fixed.
|
|
147
147
|
>
|
|
148
|
+
> **Builds measured so far.** Inert on Studio 21.0.4.5 (above) and on the free edition 21.1.0
|
|
149
|
+
> (2026-10-09: the harness's `RT_TITLE` project imported through the Project Manager, viewer
|
|
150
|
+
> black a second into the title, while a `place_generator` SMPTE Color Bar project built and
|
|
151
|
+
> imported the same way rendered). A contributor's round-trip harness run on Studio 21.0.3.7 /
|
|
152
|
+
> macOS reported the title **visible** (UNEXPECTED PASS, PR #273 thread); that result is theirs
|
|
153
|
+
> and has not been reproduced here. The live harness cannot run on a 19.x host — 19.1.3 refuses
|
|
154
|
+
> the Resolve 21 project format at `ImportProject` — so only a 21.x Resolve can add data points.
|
|
155
|
+
>
|
|
148
156
|
> **The defect is specific to the Fusion-comp path, not to clone-a-template.** `place_generator`,
|
|
149
157
|
> built the same way, works: an imported Solid Color shows a populated `Generator - Solid Color`
|
|
150
158
|
> Inspector with a live Color parameter and renders on the timeline. The difference is where the
|
package/src/granular/common.py
CHANGED
|
@@ -91,7 +91,7 @@ if not logging.getLogger().handlers:
|
|
|
91
91
|
handlers=[logging.StreamHandler()],
|
|
92
92
|
)
|
|
93
93
|
|
|
94
|
-
VERSION = "4.10.
|
|
94
|
+
VERSION = "4.10.2"
|
|
95
95
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
96
96
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
97
97
|
logger.info(f"Detected platform: {get_platform()}")
|
package/src/server.py
CHANGED
|
@@ -440,8 +440,16 @@ def _ensure_path_includes_standard_tool_dirs() -> None:
|
|
|
440
440
|
parts = current.split(os.pathsep) if current else []
|
|
441
441
|
existing = set(parts)
|
|
442
442
|
additions = [d for d in candidates if os.path.isdir(d) and d not in existing]
|
|
443
|
-
|
|
444
|
-
|
|
443
|
+
# The script dir must come first even when it is already on PATH. An
|
|
444
|
+
# activated venv puts it there, but prepending the other missing dirs in
|
|
445
|
+
# front of it would let /opt/homebrew/bin or /usr/local/bin shadow it
|
|
446
|
+
# (reported on macOS in #273's validation, where Homebrew was not yet on
|
|
447
|
+
# the inherited PATH).
|
|
448
|
+
script_dir = candidates[0]
|
|
449
|
+
front = [script_dir] if (script_dir in existing or script_dir in additions) else []
|
|
450
|
+
ordered = front + [d for d in additions if d != script_dir] + [p for p in parts if p != script_dir]
|
|
451
|
+
if ordered != parts:
|
|
452
|
+
os.environ["PATH"] = os.pathsep.join(ordered)
|
|
445
453
|
|
|
446
454
|
|
|
447
455
|
_ensure_path_includes_standard_tool_dirs()
|