Silence cutting workflow
Cut Silence in Premiere Pro with AI: Detect, Review, Then Apply
Use Premiere Pro MCP to detect silent ranges with FFmpeg, plan review markers or a silence stringout, preview ripple removals, and verify the timeline before delivery.
Silence cutting is a review chain, not one magic click
Premiere’s scripting API does not expose waveform levels, so silence measurement in this package uses FFmpeg on a local media file. detect_silence returns silent ranges and the complementary keep segments. It analyzes only; it does not modify the project or timeline.
Editors still choose which silences to keep for pacing. The supported automation pattern is detect → plan or review → preview → apply → inspect.
Detect silences and optional dialogue candidates
After verify_premiere_connection succeeds, ask the assistant to run detect_silence on a named local media file that ffmpeg can read. Review the returned silence and keep ranges against the Source Monitor yourself.
For dialogue work with a caller-supplied transcript and optional silence ranges, analyze_dialogue_edit_candidates and review_dialogue_candidates produce deterministic keep/reject decisions without calling a model or changing Premiere. They never persist transcript text inside the tool itself.
Run verify_premiere_connection and stop if it is not ready. Call detect_silence on my approved local interview file. Summarize silence and keep ranges. Do not add markers or change the timeline.Plan markers or a new silence-cut stringout
plan_silence_review_markers maps FFmpeg-detected source silences onto one known 1x timeline placement and returns a non-mutating review plan. It never adds markers by itself. When you want markers on the sequence after review, use add_marker or add_markers_batch with the ranges you approved.
On a compatible authenticated UXP host, create_silence_cut_source_stringout_uxp can create a new single-source rough-cut stringout from reviewed silence ranges using hard-bounded linked A/V subclips. It does not preserve or rewrite an existing edited timeline; it builds a new stringout.
- Duplicate the sequence or work on a disposable copy before structural cuts.
- Confirm source in/out and 1x placement before trusting mapped silence times.
- Treat UXP stringout creation as a new assembly to review, not an in-place polish.
Preview ripple removal before applying cuts
ripple_remove_timeline_ranges can preview or apply a single-pass ripple removal for up to 50 sorted, non-overlapping timeline ranges on unlocked, sync-locked tracks. Apply requires a preview confirmation token. Integer frame rates only. Large edits need allow_large_ripple: true.
The tool refuses attached transitions or unreadable transition collections before structural edits. After apply, re-inspect the sequence. If captions already exist, Premiere caption tracks do not automatically follow ripple removals; retime_caption_file can adjust a local SRT/VTT, then re-import with create_caption_track.
On my duplicate sequence, preview ripple_remove_timeline_ranges for the silence ranges I approved. Show per-track counts and planned clip samples. Do not apply until I confirm the exact token.Questions editors ask
Does detect_silence cut the timeline?
No. It only analyzes a local media file with FFmpeg and returns ranges. Cutting requires a separate reviewed plan, preview, and apply path.
Why do I need FFmpeg on PATH?
Premiere’s scripting bridge does not expose audio-level data for silence measurement. The package uses FFmpeg for that analysis step.
Will this remove intentional pauses?
It can if you apply every detected range. Review keep/reject decisions and preview ripple effects before applying, especially on interview and narrative work.
Keep learning
A practical next step
Start with a safe Premiere connection check.
Connect your assistant, verify the local bridge without changing a project, then inspect the active sequence before requesting a supported edit.
Run a safe connection check