Every AI clipper, ours included, picks a window by what's inside it — energy, keywords, pacing. None of them cared whether that window happened to begin in the middle of a sentence. We used to call that your job, and it took about two seconds. Then we stopped calling it your job.
What it looked like when it went wrong
We ran a two-minute cooking video through ClipEmber. The top-scoring clip — 82 out of 100 — opened with: "Well, it's really like, I guess it's a masher, you know what I mean?"
Nothing about that line is wrong. It's the middle of a thought, and a viewer who arrives at it has to spend a second working out what's being discussed. On a feed, you don't have that second.
Why it happened
The window ended cleanly and started badly, and that was one bug, not two. Our candidate windows grew word by word until they hit the length limit, and the limit doesn't care what a sentence is. So the end of a window usually landed on a full stop — and the beginning of the next one landed wherever the previous window ran out of room.
What we changed
Windows are now built out of whole sentences. We split the transcript into sentences first and only then pack sentences into a clip. Starting mid-phrase isn't prevented by a check any more — it's impossible by construction. One case survives: a single sentence longer than your clip limit has to be cut, and we mark those clips instead of pretending they open cleanly.
Then there's the sentence that clears the bar and still opens nothing: "Well, it's really like…" is grammatically a sentence and conversationally a continuation. When a clip would start on a filler word or a pronoun with no referent, it now takes the previous sentence along as a run-up. Note the direction: we add context rather than trim the weak line. That rule is wrong sometimes — "So you want to start a podcast?" is a fine hook — and when it's wrong we'd rather cost you two seconds of lead-in than a line of your video.
The same video, before and after
Two things we got wrong on the way
- Our first version fixed the openings in a pass that ran after the windows were built. On the real transcript it fired exactly zero times — windows are packed nearly to the length limit, so there is no room left to pull a sentence into. The decision has to be made at the moment the boundary is chosen, while the next window is still empty.
- Our second version treated a pause as the end of a sentence. A cook stopping to breathe mid-phrase — "…a little bit in here," then "right?" — produced a clip starting on "right?", and our own "opens cleanly" flag said it was fine. A pause is a scene hint, not a full stop. Where the transcript has no punctuation at all, pauses are the only signal there is, and we say so in the logs rather than guess.
If you cut by hand anywhere else
- Read the first line of a clip out loud before you post it.
- If it opens with "Well", "So", "And", "I guess" or a pronoun with no referent, move the start back to the previous sentence — not forward.
- You'll spend one to three seconds of the clip's length and get an opening a stranger can follow.
This issue went out in the morning as advice and is now a description of a shipped change; we've left the original example and numbers in place rather than quietly rewriting history. Why there's no percentage lift here: we haven't measured one. Four people read the first version — a number we're not going to dress up either.
Two of these a week, to everyone with a ClipEmber account. Make a clip or read the rest of the archive.