LLMSkillHub
mirroredCopied from samuelgursky/davinci-resolve-mcp under MIT. samuelgursky has not claimed this page, and is not affiliated with LLM SkillHub.

samuelgursky / resolve-media-pool

Media pool ingest and organization in the DaVinci Resolve MCP. Apply when importing media, building multicam timelines, organizing/relinking clips, normalizing metadata, setting clip marks, or verifying/inventorying a card before ingest — live in a running Resolve OR offline. Routes to the live media_pool tools and the offline media front-end tool. For reading/analyzing footage content use resolve-media-analysis; for deliverable-side media QC use resolve-delivery.

0
SKILL.md
2.8 KB

Resolve Media Pool / Ingest

Thin router; depth stays in the kernel.

  • Live tool mechanics — docs/kernels/media-pool-ingest-kernel.md (the
    media_pool ingest boundary) + docs/guides/multicam-setup-guide.md.

  • Offline media front-end — resolve-advanced/README.md → the media tool.

Two servers — verify offline, import live

JobServerTools
Import / organize / relink in a running Resolvedavinci-resolve (Python, live)media_pool (`safeimportmedia
Verify / inventory / hash-seal a card with no Resolve opendavinci-resolve-advanced (Node)media (needs ffmpeg + ffprobe on PATH)

Offline media actions

  • ingest_verify — hash seal / verify / dupes-by-hash (chain of custody).
  • media_inventory — fps / codec / colorspace / TC + card-gap report.
  • sync — picture↔sound TC alignment + drift / MOS.

  • relink_manifest, rename_plan (refuses camera originals) /
    reel_normalize, turnover_package, project_hygiene.

Rule of thumb: verify + inventory the card offline before importing, then import
and organize live.

Boundaries & safety (AGENTS.md)

  • Non-media files are not imported; the kernel never creates proxies, transcodes,
    or derivatives of source media.

  • Native multicam clip creation/flattening is not in the public API — the setup
    helper preps a stacked timeline you convert in Resolve's UI (see the guide).

  • ImportMedia has no destination parameter — clips always land in the
    current folder, and an unrecognized destination argument is silently ignored.
    Create the bin, set_current_folder to it, then import. Getting this
    backwards puts clips wherever the current folder happened to be, which is
    routinely somewhere an automated step moved it.

  • MediaPoolItem.GetTimeline is 21.0.4+ (issue #131) and is not reachable
    through this server yet. A media-pool entry that is a timeline cannot be
    turned back into a timeline object on older builds — check
    resolve_control check_version_support rather than assuming.

  • Never rename or derive camera originals without explicit approval;
    rename_plan refuses them by design.