Onset Engine, for PMV makers

I recommend Onset Engine all over this site, so this page is the honest version in one place: what it does, what it doesn't, and how the workflow actually goes. If you've read a guide here and thought "fine, but what is this thing" — start here.

What it does

You point it at a folder of clips and a song. It analyses the track (beats, energy, structure), analyses your footage with an AI vision model, then cuts a beat-synced edit where the clips match the energy of each section — slow build on the quiet parts, hard cuts on the drops. What normally takes an evening in Vegas takes a few minutes.

The part that makes it different from the random-clip PMV scripts floating around: it actually understands what's in your clips. That's why you can tell it "use these kinds of shots on the drops" and it does something sensible.

What it doesn't do

• It doesn't find footage for you. You bring your own library. It's an editor, not a downloader.
• It doesn't do beat-bar overlays. For cock hero rounds you still add the meter in a free editor afterward — though it now exports the beat grid to make that trivial.
• It's Windows-only, and it wants a decent GPU for comfortable ingest speed.
• It's not free beyond the demo — the demo is watermarked at 720p but otherwise complete.

Why it suits this crowd specifically

• It runs entirely on your machine. Nothing uploads, ever — no cloud editor will touch this material anyway, and this one doesn't need to. There's also a Discreet Mode that blurs every thumbnail and hides the app with one keypress.
• It's built for long source scenes. Most of us feed it 20–40 minute full scenes, and it splits them into usable clips automatically.
• Performer tagging. Tag ~5 clips of someone once, and it finds every other clip of them in your library — then you can build an edit around just them.
• It speaks funscript, in both directions: export a track's beat grid for scripting, or drive an entire edit from a script you already have.

The workflow, start to finish

1. Ingest — point it at your clip folder or full scenes. It analyses everything once; after that the library is reusable for every future edit.
2. Pick a song — anything you've got. It finds the beats and the drops itself.
3. Pick a driver + preset — the driver decides which clips play at each energy level, the preset decides how it looks. Grab the free driver pack for tuned PMV, HMV, cock hero and hypno drivers.
4. Re-roll and tweak — don't like a section? Re-roll it, swap individual clips, nudge timings.
5. Export — or send it to Vegas/Resolve as a timeline if you'd rather finish by hand.

Tutorials

Walkthroughs for the parts worth learning properly:

• How to make a PMV — the full beginner path
• Beat grid export for scripters — funscript, Audacity labels, CSV
• Using the driver pack — install, then tune the drivers for your own library
• Pacing & energy curves — why an edit feels flat, and how to fix it
• Cock hero workflow — rounds, escalation, beat meters
• Hypno PMV techniques — loops, overlays, repetition

Is it actively developed?

Yes — noticeably so. Two releases shipped in the last week alone. I track each one in plain language here, focused on what each release changes for us rather than the full engineering changelog.