feat: initial commit - Jhonny Editor

- Adicionado estrutura completa do projeto - Configurado MCP server para Premiere Pro - Adicionado documentação e skills - Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00
commit b541f502ba
1507 changed files with 387650 additions and 0 deletions
@@ -0,0 +1,29 @@
+# Silence review marker plan
+
+## Repository-fit gap
+
+`detect_silence` already makes a local FFmpeg analysis available, but its returned
+timecodes are explicitly relative to the source media. It could not translate a
+silence into a timeline position when the source had been trimmed before it was
+placed, leaving an editor or agent to do the arithmetic manually.
+
+## External comparison
+
+The current [PremiereProMCP `workflow_clean_silence` implementation](https://github.com/CaYatur/PremiereProMCP/blob/main/server/src/tools/workflow.ts)
+detects source silences and sends marker-add commands using those source-derived
+timestamps. That is useful automation, but direct marker mutation is unsafe if
+the source range or placement does not match the assumed timeline mapping.
+
+## Chosen improvement and benefit
+
+`plan_silence_review_markers` produces bounded candidate ranges for exactly one
+known 1x placement. It clips each silence to the supplied source in/out range,
+maps the retained range to a timeline start, redacts the local source path, and
+does not create markers or modify a sequence. This removes manual trim-offset
+math while preserving a human review step before any editorial change.
+
+## Explicit boundary
+
+The plan does not infer speed changes, remapping, reverse playback, multicam,
+nested sequences, or rendered timeline audio. Those cases require Premiere-host
+evidence rather than arithmetic from a decoded source file.
@@ -0,0 +1,28 @@
+# Marker-anchored review frames
+
+## Repository-fit gap
+
+The server already exports evenly spaced sequence review frames and clip-midpoint
+frames, while `list_markers` exposes marker positions separately. An editor or
+agent wanting a visual receipt for existing review markers therefore has to list
+the markers and make one individual frame-export call for every marker. Evenly
+spaced sampling can miss the annotated moments entirely.
+
+## Competitive observation
+
+The current [Adobe Premiere Pro MCP catalog](https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP/blob/main/README.md)
+promotes marker discovery and batch-oriented editing as first-class workflow
+building blocks. Its source also implements bounded, per-item batch requests
+such as [`add_to_timeline_batch`](https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP/blob/main/src/tools/index.ts).
+That supports the product need for marker-based batch handoff, but this project
+does not reuse the competitor implementation or its unsupported-host claims.
+
+## Chosen improvement and benefit
+
+`export_sequence_marker_review_frames` reads the active sequence's existing
+markers once, sorts and bounds the matches, and exports a file-verified
+composite frame at each selected marker start in the same bridge request. It
+can narrow by marker type and time range, reports truncation and partial file
+failures, and never changes any Premiere marker. This turns an N+1 bridge-call
+review loop into one bounded call while keeping the returned frame paths and
+verification scope explicit.