All tutorials
AI editing10 min read · Vynts for Mac

Direct a complete edit with AI assistance

Use Vynts’ manager, prompt history, suggestions, and model controls to request meaningful editing work—then inspect, revise, or undo every change.

Overview

What you will learn

Use Vynts’ manager, prompt history, suggestions, and model controls to request meaningful editing work—then inspect, revise, or undo every change. Follow the workflow from the first control to a result you can confidently review and deliver.

Why it matters

Work faster, keep control

AI direction is most useful when it turns creative intent into real timeline work without hiding what happened. Vynts lets you describe the outcome, choose how the request is processed, review the proposed scope, and iterate from a visible history. You stay the editor; AI handles the time-consuming execution.

Preparation

Before you begin

  • Open a project with imported and analyzed footage.
  • Decide which sequence or media collection the instruction should affect.
  • Write down the outcome, must-keep material, limits, and intended audience in plain language.
Workflow

Step-by-step instructions

Work in order. Review what appears on screen before moving to the next step.

01

Open the AI manager

Open AI Direction from the top-level manager area. This is the control center for requests that can affect the timeline, captions, color, cleanup, or delivery versions.

  1. Open your project and select the sequence you want to work on.
  2. Choose AI Direction in the top control area.
  3. Confirm that the scope names the correct sequence or selected clips before entering a request.
What you should see

The manager opens beside the edit. You will see a prompt field, suggested prompts, recent history, a model control, and the current scope. The timeline and viewer remain visible so AI never replaces the editing workspace.

Scope
Shows exactly which sequence, clips, range, or track the next request may change.
Prompt field
Where you describe the result you want in normal language.
Suggestions
Starting points based on the current project, such as tightening pacing or creating a version.
History
A record of requests, results, and checkpoints you can reopen or compare.
02

Understand model and provider choices

A model is the reasoning engine that interprets your direction. A provider is the service that makes that model available. You do not need technical expertise to choose: the labels help you balance creative reasoning, speed, availability, and your preferred setup.

  1. Open the model control above or below the prompt field.
  2. Review available choices, which may include GLM 5.1, Nemotron, or Gemini.
  3. Notice provider labels such as OpenRouter or Nvidia; the same workflow can remain familiar even when the underlying provider differs.
  4. Use the recommended model when unsure, and change models only when you want a different balance or the current option is unavailable.
What you should see

Each available model appears with its name, provider label, and a short capability or availability note. The selected option is attached to the request in History, so you can later understand how a result was produced.

Recommended
Vynts’ practical default for the current editing task.
Model
Interprets the creative instruction and plans the editing actions.
Provider
Runs the model. Labels such as OpenRouter or Nvidia identify that connection; they are not extra editing modes.
Local / Ollama
When configured and supported, a local fallback can process compatible requests on your Mac. Availability depends on the models installed in Ollama.
03

Write a direction Vynts can act on

Write like a creative brief to a skilled assistant editor. State the goal first, then useful context, constraints, and protected material. You can refer to clips, collections, markers, or timeline ranges by name.

  1. Start with an action and outcome: build, tighten, restructure, caption, match, or create a version.
  2. Add audience, duration, tone, destination, and the part of the project in scope.
  3. Name anything that must stay, must be removed, or cannot change.
  4. Keep one request centered on one editorial objective.
What you should see

As you type, Vynts may suggest project references and clarify ambiguous names. The scope summary updates before any work runs.

Prompt exampleTighten Sequence 01 into a confident 60-second launch edit for LinkedIn. Reach the product reveal by 00:12, remove repeated setup points, and use Product B-roll to cover dialogue trims. Keep the founder’s line marked Must use. Do not change the approved caption style.

Goal + destination + measurable constraint + protected material gives the model enough freedom to edit while preserving your non-negotiables.

04

Review the plan before applying it

For meaningful timeline changes, Vynts summarizes the intended actions first. Read this summary as you would review an assistant editor’s plan.

  1. Choose Preview plan or continue from the prompt.
  2. Check the named sequence, selected range, estimated actions, and protected elements.
  3. Edit the prompt if the plan is broader than intended.
  4. Choose Apply when the scope and goal are correct.
What you should see

The manager lists planned actions such as removing repeated dialogue, trimming pauses, placing B-roll, or creating a new sequence version. No source media is destroyed.

05

Inspect the completed timeline work

When processing finishes, review both the result and the change summary. The output is real editable timeline work—not an answer trapped in a chat window.

  1. Open the new or updated sequence from the completion message.
  2. Read the change summary and any note about missing footage or unmet constraints.
  3. Play the full affected range, then inspect important cuts on the timeline.
  4. Use Compare to switch between the checkpoint before the request and the new result.
What you should see

Changed clips are highlighted temporarily, History contains the request and model used, and the timeline holds normal clips, transitions, captions, and track controls.

Compare
Lets you review the sequence before and after the AI pass.
Restore checkpoint
Returns to the saved state before a request when the direction was wrong.
Change summary
Explains what Vynts changed and flags anything it could not complete.
06

Iterate from history instead of starting over

A first result gives you something concrete to direct. Continue from that result, protect what works, and ask for one focused improvement.

  1. Open the latest item in History.
  2. Choose Refine or place the playhead around the weak section.
  3. Describe what should stay and the single change you want next.
  4. Apply the revision, compare it, then keep or restore the checkpoint.
What you should see

The new request appears as a child of the earlier direction, preserving the creative trail. Previous prompts, selected models, results, and checkpoints remain available.

Prompt exampleKeep the new opening and product reveal. In the middle section only, shorten pauses and alternate Camera A with closer Product B-roll. Leave the final call to action unchanged.

Specific refinements reduce unnecessary rework. Name the good section, the weak section, and the exact improvement.

07

Finish with manual editorial judgment

Use direct timeline tools for frame-level choices, unique emotional beats, and any adjustment that is faster to make by hand. AI direction and manual editing are complementary parts of the same workflow.

  1. Trim individual cut points while watching performance and motion.
  2. Replace any technically correct but emotionally weak shot.
  3. Check music, dialogue, graphics, and captions together.
  4. Save an approved checkpoint and give the sequence a clear version name.
What you should see

The final sequence combines AI-executed structure with your detailed decisions. History documents major directions, while the timeline remains fully under your control.

Tips

Best practices

  • Use the recommended model until you have a reason to switch.
  • Confirm scope before every large request.
  • Ask for one creative objective at a time and protect strong sections explicitly.
  • Use History as an editorial record, not merely an undo list.
  • Prefer manual trims when the decision depends on a few frames of performance or motion.
Troubleshooting

Common mistakes and fixes

Treating provider labels as editing modes

Choose the model for the task; provider labels only explain where that model is running.

Prompting without a scope

Select the exact sequence, range, or collection first and verify it in the manager.

Requesting many unrelated changes

Separate structure, captions, color, and delivery into reviewable passes.

Repeating a prompt after a weak result

Open History, identify what worked, then refine one failure with clearer constraints.

Assuming local fallback is automatic

Ollama requires a compatible local model to be installed and available; check the model menu before relying on it.

Success

Expected outcome

You can confidently use prompts, suggestions, History, model selection, provider labels, and checkpoints to direct meaningful edits while keeping every result visible, editable, and reversible.

Continue learning

Optional next steps

  • Build a complete timeline from organized source footage.
  • Polish picture, sound, pacing, and continuity on the approved edit.
  • Save useful directions as repeatable prompt patterns for future projects.
Back to all tutorials