A practical editing guide
Remove dead air. Keep the story.
Quiet footage can hold the most important moment. Decide what each section contributes before a silence detector decides where to cut.
Silence and dead air are different
Dead air is footage that no longer earns its place in the video: waiting without useful context, a repeated explanation, or an attempt that adds nothing new. Silence is only an audio condition. A quiet ambush can matter; a loud loading screen can still be disposable.
This is Aqua Edits’ editorial guidance. The three before-and-after sequences below are illustrative editing scenarios, not clips from customer work or measured product tests. Use them to make decisions in your own timeline.
Example 1: cut a loading screen
Illustrative before → after
Before: the creator chooses a mission → a loading screen repeats a tip → the creator states the next objective.
After: the mission choice → the first clear view of the new location → the objective.
Why: the repeated tip and waiting do not add information. Keep enough of the new location to establish the scene. Listen across the cut so a sentence, music cue, or game sound does not end abruptly.
Keep it instead when: the creator explains the plan over the loading screen. You can shorten the waiting pictures while keeping that explanation, if the resulting audio and images remain clear and truthful.
Example 2: compress repetition, keep the change
Illustrative before → after
Before: failed boss attempt → identical run back → same mistake → run back → a new strategy → final attempt.
After: one failure that explains the obstacle → the decision to change strategy → enough of the final attempt to show how it goes.
Why: the run backs repeat what the viewer already knows. The decision explains progress. Keep an additional failure if it reveals something new or delivers a reaction the story needs.
Avoid a misleading cut: do not join separate attempts to imply one uninterrupted success. Use an honest transition or a brief label when viewers need to know time or attempts have passed.
Example 3: preserve a quiet payoff
Illustrative before → after
Before: the creator hears footsteps → stops talking and waits → an opponent enters view → the creator reacts.
After: keep the footsteps, the meaningful wait, the visual reveal, and the reaction together. Trim only unrelated waiting around that sequence.
Why: the pause creates anticipation and lets the viewer notice the same clue. Cutting every quiet interval would remove the cause of the reaction.
Check the picture: a health bar, map change, teammate signal, or facial reaction can explain a moment without speech. Watch candidate cuts before removing them.
A cleanup pass you can repeat
- Protect the original. Duplicate the sequence. Mark the goal, turning point, and payoff so cleanup does not erase the outline.
- Find candidates. Mark queues, menus, breaks, repeated explanations, and repeated travel. A silence detector can help locate quiet audio, but it does not establish whether the gameplay matters.
- Inspect both sound and picture. Listen for quiet speech, teammates, game cues, and unfinished sentences. If you have separate microphone and game tracks, inspect them separately. OBS documents separate-track recording for future sessions.
- Calibrate on a small selection. If your editor offers a level threshold, duration threshold, and padding, try them on a representative section first. Keep enough padding for natural word endings and breaths. There is no single useful threshold for every microphone, game, and mix.
- Review every proposed removal. Preserve quiet actions and useful speech over static screens. Keep audio and video aligned when closing gaps. Compare with the original if the new sequence changes the meaning.
- Watch each transition in context. Check that the cut explains where the player is and why the next action happens. A short audio fade can soften an abrupt edit, but cannot restore missing context.
Check what the cut still explains
- Can a new viewer understand the objective without chat or the stream title?
- Does each reaction still have its cause?
- Are strategy changes and important failures visible?
- Did a quiet gameplay cue or teammate line disappear?
- Are there clipped syllables, audio pops, sync errors, or confusing jumps?
- Does the ending reflect what actually happened?
If a faster cut is harder to follow, restore the missing setup or pause. Record review notes with version numbers and timestamps so another editor can act on them.
Download the editing brief and review checklist (TXT). For the complete process, continue with turning a Twitch VOD into a YouTube video. For a finished edit with creator review, see Aqua’s Twitch editing workflow.
Watch a complete output
See a complete video in the Pokémon Nuzlocke output example. The owner identifies this selected video as Aqua engine output with no human edits after generation. The example includes the original VOD supplied by the owner, so you can compare the source with the finished output. No editing-time or audience-performance result is claimed.