davinci-resolve-mcp 2.67.0 → 2.67.1
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 +18 -0
- package/README.md +1 -1
- package/docs/kernels/render-deliver-kernel.md +14 -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,24 @@
|
|
|
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.67.1
|
|
6
|
+
|
|
7
|
+
Documentation correction. No code changes — v2.67.0 already ships the correct
|
|
8
|
+
behavior.
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- **`docs/kernels/render-deliver-kernel.md` no longer quotes a format/codec count
|
|
13
|
+
as portable.** It presented "23 formats and 99 format/codec pairs" as the
|
|
14
|
+
expected probe result; a live probe on Studio 19.1.3.7 found 20 formats and 271
|
|
15
|
+
pairs. Both mentions now carry the build they came from and point at probing
|
|
16
|
+
the machine in hand (`probe_render_matrix`, or `list_delivery_targets` with
|
|
17
|
+
`check_availability`) instead of comparing against a fixed number.
|
|
18
|
+
- The kernel's boundary list now records the two traps the delivery-target work
|
|
19
|
+
verified live: codec **descriptions are not codec ids** (`H.264` vs `H264`, not
|
|
20
|
+
only the ProRes family), and some formats expose **no codecs at all** (`Wave`,
|
|
21
|
+
`GIF` on 19.1.3.7) and cannot be selected through this API.
|
|
22
|
+
|
|
5
23
|
## What's New in v2.67.0
|
|
6
24
|
|
|
7
25
|
Adds **delivery targets** — named render intents that carry their own QC spec —
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# DaVinci Resolve MCP Server
|
|
2
2
|
|
|
3
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
4
4
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
5
5
|
[](docs/reference/api-coverage.md)
|
|
6
6
|
[-blue.svg)](#server-modes)
|
|
@@ -79,7 +79,17 @@ come from one definition.
|
|
|
79
79
|
readback as version/page dependent and still validates and applies settings
|
|
80
80
|
through `SetRenderSettings`.
|
|
81
81
|
- Render format and codec availability is machine, OS, license, and plugin
|
|
82
|
-
dependent
|
|
82
|
+
dependent, and it varies a lot: a live probe found 23 formats / 99 pairs on one
|
|
83
|
+
build, and 20 formats / 271 pairs on Studio 19.1.3.7. Treat neither figure as
|
|
84
|
+
the expected count — probe the machine you are on
|
|
85
|
+
(`probe_render_matrix`, or `list_delivery_targets` with `check_availability`).
|
|
86
|
+
- Codec **descriptions are not codec ids**. `GetRenderCodecs` returns
|
|
87
|
+
`{description: id}` and every setter wants the id, so the name shown in the
|
|
88
|
+
Deliver page is rejected — for `H.264` (`H264`) just as much as for
|
|
89
|
+
`Apple ProRes 422 HQ` (`ProRes422HQ`). `src/utils/render_ids.py` normalizes
|
|
90
|
+
either form; see `docs/reference/api-limitations.md`.
|
|
91
|
+
- Some formats expose **no codecs at all** (`Wave`, `GIF` on 19.1.3.7) and then
|
|
92
|
+
reject every codec value, so they cannot be selected through this API.
|
|
83
93
|
- Some settings may be accepted but not readable for coercion checks on builds
|
|
84
94
|
where `GetRenderSettings` is unavailable.
|
|
85
95
|
- Quick Export actual execution is intentionally gated behind
|
|
@@ -151,6 +161,8 @@ Result:
|
|
|
151
161
|
|
|
152
162
|
The live harness created and deleted a disposable project named
|
|
153
163
|
`_mcp_render_deliver_probe_1778342107`, generated synthetic media, probed 23
|
|
154
|
-
formats and 99 format/codec pairs
|
|
164
|
+
formats and 99 format/codec pairs **on that build** (a later probe on Studio
|
|
165
|
+
19.1.3.7 saw 20 formats / 271 pairs — the counts are not portable), rendered one
|
|
166
|
+
tiny synthetic output, wrote
|
|
155
167
|
JSON and Markdown reports, and removed the generated media and render output
|
|
156
168
|
directories after the report was written.
|
package/install.py
CHANGED
|
@@ -36,7 +36,7 @@ from src.utils.update_check import (
|
|
|
36
36
|
|
|
37
37
|
# ─── Version ──────────────────────────────────────────────────────────────────
|
|
38
38
|
|
|
39
|
-
VERSION = "2.67.
|
|
39
|
+
VERSION = "2.67.1"
|
|
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.67.
|
|
88
|
+
VERSION = "2.67.1"
|
|
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()}")
|