How to split a long recording into consecutive clips with nothing left out
Upload the recording and tell Vizard Agent to use all of it. Vizard Agent transcribes the whole thing with word timings, analyses the pauses, builds a clip plan that breaks on sentence boundaries rather than on the clock, hunts for clips that start or end mid-thought, and rebuilds the plan around them.
What is the short version?
Most clipping is selection — find the good bits and discard the rest. Serialising is the opposite job: every second has to end up in a clip, and the only freedom you have is where the joins fall.
- Go to Vizard Agent and upload the full recording.
- Say that all of it must be used and nothing skipped.
- Give a clip length range rather than a fixed number.
What do you need before you start?
The recording and a length range. Vizard Agent needs the range rather than an exact number because sentence boundaries do not fall on round minutes, and a fixed length forces cuts in the middle of what somebody is saying.
- The recording. Hours are fine.
- The range. Forty-five to ninety seconds, for instance.
- The rule. All of it, in order, nothing dropped.
- The preference. Complete thoughts where possible.
- The output. Numbered files, usually.
What do you type into Vizard Agent?
Say "one hundred per cent" and give a range. Vizard Agent treats completeness as a hard constraint and the length as a soft one, which is the right way round — it means the joins move to fit the speech rather than the speech being cut to fit the clock.
Prompt
Variants worth knowing:
- Sentence-aware joins. Breaks at pauses, not at fixed intervals.
- A wider range. More freedom to land on good boundaries.
- Numbered output. So the order survives the download.
What does Vizard Agent actually do?
Here is the order Vizard Agent worked in on a real two-hour recording. The steps that make the difference are the twelfth and fourteenth: after building the plan, it went looking for the clips it had got wrong and rebuilt around them.
- Probes the video's specifications and checks the transcription tools.
- Transcribes the full recording with word timings.
- Extracts sample frames across the whole video and reviews them.
- Inspects the transcript's structure and its file size.
- Analyses the pauses and writes a readable version of the transcript.
- Reads the start of the transcript to get a feel for the content.
- Builds a sentence-aware clip plan across the whole recording.
- Inspects the shortest, longest and final clips the plan produced.
- Finds the clips with hanging starts or ends, inspects the mid-sentence cut and the ending, and rebuilds the plan to fix them — then times a test encode, checks the keyframes and tests a variable-frame-rate-preserving encode.
Step 9's first half is the quality check that most automated splitting skips entirely. A plan that respects sentence boundaries on average still produces a handful of clips that open mid-word, and finding those deliberately is what stops the series having three unusable episodes in it.
What does the result look like?
The recording this was built from measures 720x1280 at 50fps and runs 8178 seconds — two hours and sixteen minutes. Out of it comes a consecutive series of clips, each between forty-five and ninety seconds, together containing every second of the original and each starting and ending on something a listener can follow.
Nothing is missing and nothing is repeated. That is the property that makes this different from highlight clipping: the series is the recording, redistributed rather than reduced.
When does this not work well?
Using all of a recording means using the dull parts along with the good ones, and no amount of clever splitting by Vizard Agent rescues material that was not worth keeping in the first place. That trade is the price of complete coverage.
- Everything is included, including the weak parts. Selection is what you gave up.
- Length ranges must be realistic. Very tight ranges force awkward joins.
- Rambling speech has no boundaries. Sentence-aware splitting needs sentences.
- Long encodes take real time. Two hours is a lot of output to render.
- Variable frame rates complicate splitting. They have to be handled, not ignored.
How do you fix a result that came back wrong?
Name the clip number. Vizard Agent keeps the full transcript with word timings, the pause analysis and the clip plan, so a join can be moved without recutting the whole series or breaking the guarantee that nothing is lost.
- "Clip nine starts mid-sentence." The join is moved and its neighbours re-timed.
- "They are too long to post." The range is narrowed and the plan rebuilt.
- "One is missing." The plan is checked against the recording's full duration.
How does Vizard Agent compare to doing it yourself?
By hand this means setting markers every minute or so through a two-hour recording, listening at each one to check you are not cutting through a word, and then exporting sixty files. The listening is the part that gets abandoned around clip fifteen.
| By hand | Vizard Agent | |
|---|---|---|
| The joins | Every minute, roughly | Placed on sentence boundaries |
| Checking | Listen at each marker | Hanging starts and ends hunted down |
| Coverage | Hope nothing was skipped | Every second accounted for |
| Encoding | Export and wait | Test-encoded first for speed and quality |
Common questions
How long a recording can Vizard Agent split? Hours. Vizard Agent handled two hours and sixteen minutes on this run, transcribed in full.
Will any footage be missing? No. Vizard Agent treats complete coverage as a hard constraint and the length as flexible.
Why give a range rather than a length? Because sentences do not end on round numbers. A range lets Vizard Agent land the joins on pauses.
Will clips start mid-word? Vizard Agent specifically hunts for those after building the plan, then rebuilds it to fix them.
Can it number the output? Yes, and it should. Vizard Agent numbers them, since order is what holds the series together.
Why not just cut every sixty seconds? Because a fixed interval cuts through whatever is being said at that moment, and roughly one clip in five ends up opening mid-word. Moving the joins to the nearest pause costs nothing and fixes all of them.
Does this suit a livestream? Yes, and it is the common case. A long stream becomes a postable series without anything being discarded.
What if the speech never pauses? Then the joins fall wherever they can. Vizard Agent will tell you which clips are awkward.
Can I get a highlights cut as well? Yes. Vizard Agent builds one from the same transcript as a separate request.
Should I publish them in order? Usually yes. Vizard Agent numbers them because the series only makes sense read in sequence, and posting them out of order turns a serialised recording back into unrelated clips.
Does every clip need to stand alone? Not entirely, and it cannot. Vizard Agent prefers complete thoughts, but a serialised recording carries context forward, which is part of why the order matters so much.
Does Vizard Agent check the clips? Yes. It inspects the shortest, the longest and the final clip before delivery.