# Reported issues for Kinocut

Pod holds 16 of 18 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Kinocut](/mcp/kinocut).

## Most discussed

### Spec: Product and object matte on hyperframes-remove-background

# Spec: Product and object matte on existing hyperframes-remove-background

**Status:** agent-ready
**Date:** 2026-08-19
**Public guide:** `docs/PRODUCT_MATTE.md`
**Example:** `examples/product-matte/`

## Who this is for

Kinocut users who shoot **things**, not people: product photographers, shop operators, catalog studios, UGC sellers, marketplace listings. Jewelry on a turntable, shoes on a sweep, bottles on a lightbox, phones on a table, ceramics on a banding wheel, boxed SKUs on a kitchen t

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/461) · 2026-08-19 · closed · 7 comments

### Spec: Insta360 X4 360 dual-cam assembly

# Spec: Insta360 X4 360 dual-cam assembly

**Status:** ready-for-agent  
**Date:** 2026-08-13  
**Design companion:** `docs/superpowers/specs/2026-08-13-x4-360-assembly-design.md`

## Test seams (highest, existing first)

One compiler seam: **propose → validate → approve → render** a `360_assembly_plan`.

Hook it through existing surfaces only:

- **Intent** — `video_intent` with `goal=` emits the plan (no new MCP name).
- **Review** — same approve/reject contract as shorts/EDL review.
- **Rende

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/443) · 2026-08-13 · closed · 4 comments

### Wayfinder map: first-class Windows support and honest diagnostics

## Destination

The spec **[first-class Windows support and honest diagnostics](https://github.com/KyaniteLabs/kinocut/issues/447)** implemented and merged: the MCP entry point reports real import failures, doctor exercises the MCP server import path, the projectstore tests run on Windows, CI guards the platform on every PR, and Windows lock errors surface instead of hanging. The maintainers work these tickets themselves — the PR #446 contributor's scope ends at his own diff.

## Notes

- Domain

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/453) · 2026-08-15 · closed · 3 comments

### effect_noise with mode='film' produces extreme green/magenta chromatic distortion on image-based videos

# Bug Report: `effect_noise` Produces Extreme Green/Magenta Chromatic Distortion

**Repository:** KyaniteLabs/mcp-video  
**Version:** 1.4.0  
**Labels:** bug, effects

---

## Bug Summary

The `effect_noise` tool with `mode="film"` and `animated=true` applies extreme green/magenta chromatic aberration that completely destroys video content, rather than subtle film grain.

## Reproduction Steps

1. Create a video from a static image using `video_create_from_images`
2. Apply `effect_noise` with t

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/302) · 2026-05-12 · closed · 2 comments

### doctor: verify the MCP server import path

## Parent

#447

## What to build

`kino doctor` gains a check that actually imports the MCP server tool tree and reports it as its own component. On a machine where the server tree cannot import (the #445 scenario), doctor names the failing component and does not report overall OK — "OK" starts to mean the primary integration paths work, not just the ffmpeg binaries. The check is failure-isolated (a failed check can never crash doctor) and uses the same stable, privacy-safe error mapping as the

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/449) · 2026-08-15 · closed · 1 comment

### MCP mode: surface real import failures instead of 'missing mcp package'

## Parent

#447

## What to build

When `kino --mcp` fails to start because something in the MCP server tool tree cannot import, the command prints the real cause — through the project's privacy-safe error vocabulary, with a non-zero exit — instead of today's "MCP mode requires the 'mcp' package" message. Only the genuine absence of the MCP package keeps the current install hint. The lazy-import structure of the entry point and CLI startup behavior are unchanged. (This is the second half of #445

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/448) · 2026-08-15 · closed · 1 comment

### Spec: first-class Windows support and honest diagnostics (follow-ups to #445 / #446)

## Problem Statement

A Windows creator who installs Kinocut and runs `kino --mcp` — the primary integration path documented in the README — gets a startup failure that misreports its own cause: "MCP mode requires the 'mcp' package," even when the package is installed. `kino doctor` reports OK at the same time. The user has to dig the real traceback out themselves before filing a usable report (#445). PR #446 removes the immediate blocker (the Unix-only lock import), but the system properties th

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/447) · 2026-08-15 · closed · 1 comment

### MCP mode fails on Windows: projectstore/store.py imports Unix-only fcntl (error masked as missing 'mcp' package)

`kino --mcp` fails on Windows because `kinocut/projectstore/store.py` imports `fcntl`, which is Unix-only. The user-facing message points at the wrong cause, which makes this hard to diagnose.

## What happens

```
> kino --mcp
MCP mode requires the 'mcp' package.
Install with: pip install kinocut
```

That message is misleading: `mcp` **is** installed (1.29.0, pulled in by the package itself). The real error is swallowed by a broad `except ImportError` in `__main__.py`:

```python
if args.mcp o

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/445) · 2026-08-15 · closed · outside contributor · 1 comment

## Most recent

### Docs: self-host Kinocut MCP behind Funnel + OAuth (reference stack)

## Context

I published an Apache-2.0 reference packaging that runs **Kinocut + HyperFrames** behind Tailscale Funnel, Caddy, and Google OAuth (mcp-auth-proxy):

https://github.com/ismailkattakath/hyperframes-selfhost

## Ask

If useful, a one-line pointer under install / deploy docs (or “community deploys”) would help operators who want a public MCP URL without opening home-router ports or using hosted cloud MCP.

Happy to open a docs PR if you prefer that shape. Not affiliated with HeyGen host

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/432) · 2026-07-29 · closed · external user · 1 comment

### fix(hyperframes): restore skip_transcribe contract without reopening MCP hang

## Summary

PR #361 correctly fixed the no-TTY Hyperframes hang by closing child stdin and setting `HYPERFRAMES_SKIP_SKILLS=1`, but it also moved `--skip-transcribe` from a conditional switch into the always-on `init` arguments.

As a result, the public `skip_transcribe: bool = False` parameter is now ignored across the engine, Python client, CLI, and MCP tool: passing `False` still emits `--skip-transcribe`.

## Current evidence

- `kinocut/hyperframes_engine.py`: `init.fixed` always includes `

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/379) · 2026-07-18 · closed · 0 comments

### [pipeline][MEDIUM] Dashboard cannot fully read repository status

## Pipeline issue-surfacing finding

This issue was created or refreshed automatically by the pipeline issue surfacing worker. It is designed to be picked up later by a fixer/triage agent without rediscovering the failure from scratch.

### Signal
- **Repo:** `KyaniteLabs/mcp-video`
- **Kind:** `dashboard_repo_error`
- **Severity:** `MEDIUM`
- **Source:** `repos/status`
- **Fingerprint:** `issue-surfacing:941515abf6f48c75bff9`
- **Generated at:** 2026-05-31T11:10:19Z

### Root cause hypothesis
D

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/337) · 2026-05-31 · closed · 1 comment

### [pipeline][MEDIUM] Dashboard cannot fully read repository status

## Pipeline issue-surfacing finding

This issue was created or refreshed automatically by the pipeline issue surfacing worker. It is designed to be picked up later by a fixer/triage agent without rediscovering the failure from scratch.

### Signal
- **Repo:** `KyaniteLabs/mcp-video`
- **Kind:** `dashboard_repo_error`
- **Severity:** `MEDIUM`
- **Source:** `repos/status`
- **Fingerprint:** `issue-surfacing:df6a6878efe094da3829`
- **Generated at:** 2026-05-28T04:43:59Z

### Root cause hypothesis
D

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/335) · 2026-05-28 · closed · 1 comment

### Add doctor/version checks for FFmpeg, Hyperframes, Node, and package skew

Version/dependency skew is too hard to diagnose before a media job starts.

During NucBox dogfood, we needed to check:

- FFmpeg installed version vs upstream/latest/Ubuntu candidate
- Hyperframes npm CLI version
- `@hyperframes/core` package presence/version
- Node/npm/npx path
- mcp-video installed version vs latest PyPI/GitHub release
- whether the local `mcp-video` entrypoint is importable

The information is available manually, but not as one MCP-video health surface. This caused avoidable 

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/316) · 2026-05-21 · closed · 0 comments

### video-quality-check falsely fails silent videos and renders empty report

## Bug

`mcp-video video-quality-check` gives a misleading empty `Overall: FAIL` report for valid silent videos.

This has now blocked/derailed the NucBox image-to-video workflow repeatedly. On the latest run, a valid 1080x1920 / 30fps / 61-frame silent MP4 was marked FAIL with an empty table, even though visual QA and Kimi review showed the clip was visually usable.

## Latest reproduction evidence

Command run on the NucBox:

```bash
/srv/external/bin/mcp-video video-quality-check \
  /srv/ext

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/311) · 2026-05-21 · closed · 1 comment

### remotion_still tool has no props parameter — renders cannot accept runtime data

### Summary

The `remotion_still` tool exposed by this MCP server accepts only: `project_path`, `composition_id`, `output_path`, `frame`, `image_format`. There is no `props` / `inputProps` / `defaultProps` parameter. As a result, every still rendered through this MCP tool uses the composition's `defaultProps` from `src/Root.tsx`, which makes the tool functionally unusable for dynamic content.

The underlying Remotion CLI (`npx remotion still`) has supported `--props=<json-or-path>` since Remotio

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/306) · 2026-05-15 · closed · external user · 1 comment

### Bug: audio_effects fails on 24-bit PCM WAV input

## Bug Report

`audio_effects` fails with an internal error when processing WAV files recorded on macOS with 24-bit PCM audio.

This was found while dogfooding mcp-video on the Mac Mini for the EP01 social teaser workflow.

### Input

48kHz, 24-bit PCM WAV files recorded via ffmpeg/avfoundation:

```bash
ffmpeg -f avfoundation -i ":0" -ac 1 -ar 48000 -c:a pcm_s24le input.wav
```

### Error

The MCP tool returns:

```json
{"success":false,"error":{"type":"internal_error","code":"internal_error","

[Read the thread](https://github.com/KyaniteLabs/kinocut/issues/262) · 2026-05-09 · closed · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/KyaniteLabs/kinocut/issues).