Skip to content

samuelgursky/davinci-resolve-mcp

v2.41.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1mo MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

blackmagic blackmagic-design blackmagicdesign davinci-resolve davinciresolve mcp
+1 more
mcp-server

ReleasePort's take

Light signal
editorial:auto 1mo

Release v2.41.0 introduces schema v9 to the per‑project SQLite DB, adding multiple new tables and making the DB the source of truth for clip analysis.

Why it matters: Affects developers and SREs managing media pipelines; migration to schema v9 is required before upgrading beyond v2.41.0.

Summary

AI summary

The per‑project SQLite DB becomes the source of truth for clip analysis with schema v9.

Changes in this release

Feature Low

Adds schema v9 with new tables: clips, clip_aliases, analysis_reports, shots, subjective_fields, field_changelog, transcript_segments, frames, qc_observations.

Adds schema v9 with new tables: clips, clip_aliases, analysis_reports, shots, subjective_fields, field_changelog, transcript_segments, frames, qc_observations.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Feature Low

Adds `analysis_store.py` with transactional ingest, export overlay, alias-based clip lookup, and shot id stability.

Adds `analysis_store.py` with transactional ingest, export overlay, alias-based clip lookup, and shot id stability.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Feature Low

Adds `media_analysis` actions `db_status` and `db_ingest` for one‑shot JSON report migration.

Adds `media_analysis` actions `db_status` and `db_ingest` for one‑shot JSON report migration.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Bugfix Medium

Fixes eight V2 actions that were unreachable from MCP dispatch since v2.24.0.

Fixes eight V2 actions that were unreachable from MCP dispatch since v2.24.0.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Bugfix Medium

Enhances action‑list drift guard to inspect async tool functions and fail on unreachable actions; lists four previously unadvertised reachable actions in unknown‑action errors.

Enhances action‑list drift guard to inspect async tool functions and fail on unreachable actions; lists four previously unadvertised reachable actions in unknown‑action errors.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Refactor Low

Changes analysis write path to write DB rows first, then export JSON; panel endpoints read DB‑first with JSON fallback.

Changes analysis write path to write DB rows first, then export JSON; panel endpoints read DB‑first with JSON fallback.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Refactor Low

Mirrors field corrections (`update_clip_field`, `update_shot_field`, `revert_field`) into DB as row‑level provenance while keeping sidecar for compatibility.

Mirrors field corrections (`update_clip_field`, `update_shot_field`, `revert_field`) into DB as row‑level provenance while keeping sidecar for compatibility.

Source: llm_adapter@2026-06-10

Confidence: high

 —
Full changelog

DB-canonical clip analysis (C1) — Phase A of the analysis + edit-engine program.

The per-project SQLite DB (_soul/timeline_brain.sqlite, schema v9) is now the source of truth for clip analysis; analysis.json becomes a derived export written in lockstep.

Added

  • Schema v9: clips, clip_aliases, analysis_reports (canonical full payload), shots, subjective_fields + field_changelog (per-field provenance), transcript_segments, frames, qc_observations.
  • src/utils/analysis_store.py: transactional ingest, export with human-correction overlay (human rows always win and survive re-analysis), alias-based clip lookup, shot ids stable under one-second boundary jitter, round-trip guard verified against a real sample analysis root.
  • media_analysis actions db_status and db_ingest (one-shot migration of existing JSON reports + corrections.json sidecars into the DB).

Changed

  • Analysis write path: execute_plan and commit_vision write DB rows first, then export the JSON. Panel clip/shot endpoints read DB-first with JSON fallback for pre-v9 reports and job-linked report dirs.
  • update_clip_field / update_shot_field / revert_field mirror corrections into the DB as row-level provenance (the sidecar remains for compatibility).

Fixed

  • Eight V2 actions unreachable from MCP dispatch since v2.24.0 (get_panel_state, set_panel_state, session_start_context, update_shot_field, update_clip_field, get_field_history, revert_field, list_corrections) — checked inside the dispatch block but missing from its membership set; the control panel proxied to the helpers directly, which masked it.
  • The action-list drift guard now inspects async tool functions and fails on unreachable actions inside membership blocks; four reachable-but-unadvertised actions are now listed in the unknown-action error.

Validation

  • Full offline suite: 1066 tests (12 new), 3 known live-Resolve environmental failures only (present on clean baseline).
  • Round-trip guard on the real 2026-05-17 sample root; live headless pipeline run on synthetic media verifying rows-then-export parity, row-level corrections, and DB-first panel reads.

Breaking Changes

  • Schema v9 replaces `analysis.json` with `_soul/timeline_brain.sqlite` as the canonical source of truth for clip analysis.
View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track samuelgursky/davinci-resolve-mcp

Get notified when new releases ship.

Sign up free

About samuelgursky/davinci-resolve-mcp

MCP server integration for DaVinci Resolve

All releases →

Related context

Beta — feedback welcome: [email protected]