Skip to main content
中文EN
Auto-Editor: Command-line tool for automatic video and audio editing
AI WorkflowAI workflowGitHub source ZIP and repository

Auto-Editor: Command-line tool for automatic video and audio editing

Auto-Editor automatically edits video and audio by analyzing audio loudness, visual motion, and other criteria. It can remove silence, cut low-motion sections, and export a first-pass edit for further work in other editors. The project is primarily written in Nim.

Delivery

GitHub source ZIP and repository link

Project language

Nim

This is an upstream source snapshot at a fixed commit, separate from any ENHE package.

AI workflow details

This workflow comes from a GitHub repository. Review the delivery and verification status below before using it.

Application area

Video generation

Project type

Workflow

License

Unlicense

Delivery

GitHub source ZIP and repository link

GitHub stars

5,689 · 11/1/2026

Package verification

No ENHE package available

Link-only reason: This item is available as an upstream repository link only.

Workflow introduction

Workflow introduction

Review core features, use cases, and delivery details.

Project overview

Auto-Editor is a command-line application for automatically editing video and audio, primarily written in Nim. It uses methods such as audio loudness and visual motion analysis to determine which sections to keep, cut, or process with other actions. It processes existing media and can perform a first pass before detailed editing, such as removing silent gaps. It is not a tool for generating videos from text.

Use cases

- Remove silent gaps from long recordings or videos before manually refining the edit. - Filter footage by visual motion, cutting sections below a specified motion threshold. - Apply different audio conditions to multiple tracks, or combine audio and motion analysis. - Export an automatic first-pass edit to Adobe Premiere Pro, DaVinci Resolve, Final Cut Pro, ShotCut, or Kdenlive for further editing.

What it does and problems it solves

Finding and removing silent gaps section by section is repetitive work that becomes more cumbersome with longer media. Auto-Editor uses analysis conditions to make cuts automatically, reducing this manual work. The `--margin` option preserves time before and after cut boundaries to adjust pacing, while `--edit` specifies the criteria for automatic editing. The project also supports assigning actions to different labels, such as speeding up louder sections, and exporting individual media clips.

How to use

These steps assume installation is complete and the `auto-editor` command is available. 1. Prepare a video and note its file path. Enter `auto-editor path/to/your/video.mp4` in a command-line terminal, replacing the example path with your actual file path. The README specifies `audio:threshold=0.04,stream=all` as the default condition, which analyzes audio across all tracks. 2. Adjust cut boundaries if needed. Use `auto-editor example.mp4 --margin 0.2sec` to preserve 0.2 seconds before and after each boundary, or `auto-editor example.mp4 --margin 0.3s,1.5sec` to preserve 0.3 seconds before and 1.5 seconds after. Replace `example.mp4` with your actual file path. 3. To edit based on visual motion, use `auto-editor example.mp4 --edit motion:threshold=0.02` to cut sections where total motion is below 2%. You can also combine audio and motion conditions with `auto-editor example.mp4 --edit "(or audio:0.03 motion:0.06)"`. 4. For further manual editing, use `auto-editor example.mp4 --export premiere` to create an XML file that can be imported into Adobe Premiere Pro. Other export options include `--export resolve`, `--export final-cut-pro`, `--export shotcut`, and `--export kdenlive`. Use `--export clip-sequence` to export individual media clips. 5. Enter `auto-editor --help` to list all available options. To inspect material normally removed, use `auto-editor example.mp4 --when-active cut --when-inactive nil` to export the sections that would usually be cut.

Installation

1. Open the original repository from the bottom of this page and find the Installing entry in its README. The supplied README directs readers to a separate installation page and does not list complete installation commands for the main application, dependency requirements, or supported operating systems. Consult that installation guidance first. 2. Follow the installation instructions referenced by the original repository to install the main application. The supplied material is insufficient to provide a complete procedure you can follow directly or confirm which installation method suits your environment. 3. After installation, enter `auto-editor --help` in a command-line terminal to check whether it displays the available options, then follow the usage steps above to process media. 4. The README separately provides `npx skills add WyattBlue/auto-editor` under Skills. Its placement does not establish that it installs the Auto-Editor application itself; the supplied material does not further explain its prerequisites or usage.

Source and usage notes

- Original repository: https://github.com/WyattBlue/auto-editor - Source revision: ac1eb0c6f85f77fe8ebe0125478152420116cc83 This listing links to the upstream repository. It does not provide a verified download package, and the complete workflow has not been independently validated. This description was organized and translated with AI from public upstream material. Refer to the original repository for capabilities, setup requirements, costs, and license terms.

Changelog

0 records

Important version notes will be added when availability, delivery details, or usage guidance changes. Review the current page information before purchase or use.

Share this product

Scan the QR code to open this product, or copy its link to share.

User comments

Log in to comment.

FAQ

How do I get this workflow?

Use Get workflow to open the GitHub repository. ENHE does not provide a download package for this entry; follow the upstream instructions.

What should I check before using it?

Check the upstream setup instructions, runtime requirements, version, and the verification status shown on this page. A repository link does not mean ENHE has verified the complete workflow.

Does access include third-party services and permissions?

Check the upstream license and each service provider's terms. Model APIs, accounts, hosting, and other dependencies may have separate requirements or charges; follow the stated delivery scope.