Turn a four-hour stream into videos worth posting

Loud is easy to find and it is not the same as watchable. A stretch where you shout at a jump scare for four seconds is not a video.

Four signals decide, and the first carries the most weight. Topic cohesion: does this stretch keep returning to one subject across its whole length? Sustained reactions: energy spread across the block rather than one spike. Audience interaction: how much of the talk is aimed at chat. Speech continuity: a block that is mostly dead air is not an activity, however exciting its few moments are.

A long stream returns to the same activity over and over, and two stretches an hour apart can be the same bit. Early versions offered four proposals that turned out to be one video listed four times, which is worse than offering one: it fills every slot with something you have already seen and hides everything else that happened.

So it compares what was actually said in each stretch, weighting words by how rarely they appear in the rest of the recording. On a Minecraft stream the word “minecraft” is in every candidate and tells you nothing; what is left after setting those aside is what genuinely differs.

Each proposal comes with a length, a plain summary of what happens in it, and title ideas. The summary is there so you can judge a twenty-minute cut without watching twenty minutes.

Approve the ones you want and each becomes its own sequence in your project bin, with the dead air already trimmed and the off-topic runs removed if you asked for that. From there it is an ordinary Premiere timeline: trim it, caption it, post it.

Dynamic Too is our clips channel, fed from stream VODs. It passed 300 subscribers on clips found and cut with this tool and the “clip that” finder, and nothing else. That is a small number and we are not going to dress it up as more than it is, but it is real and it is the reason the tool is shaped this way.

What we learned building it: live viewers rarely arrive from the live page. They arrive from clips posted somewhere findable, which makes the bottleneck posting frequency rather than taste.