Eroscripts - the scripting community, explained (+ free beat markers)

Eroscripts is the home forum of the interactive-script scene: a community that writes funscripts - timing files that sync haptic devices (Handy, OSR, and friends) to videos. It's also where a lot of cock hero and PMV work gets shared, dissected, and improved. If you make beat-synced videos, sooner or later you end up there.

What actually happens on Eroscripts

• Script releases - Creators publish .funscript files synced to specific videos, rated and heatmapped by the community
• Cock hero & PMV threads - Beat-timed videos are a natural fit for scripting, so the two scenes overlap heavily
• Tooling - OpenFunscripter (OFS), motion-tracking generators, heatmap tools - it's a technical community that builds and shares its own software
• Requests & collabs - Scripters pick up requests; editors and scripters trade work

The scripter's bottleneck: finding the beat

Ask anyone who scripts music-timed content: the tedious part isn't the creative decisions, it's marking time. Tapping beats by hand in Audacity, nudging markers in OFS, re-checking drift on a 10-minute track - hundreds of placements before the real work starts.

That's a solved problem in the music-analysis world, and it's exactly what Onset Engine's audio engine does all day: a neural beat + downbeat model (Beat This!) that gives you both the beats and where each bar starts - the same grid it uses to auto-cut PMVs.

Worth flagging if you tried the beat export before v1.0.12: the downbeats used to be assumed rather than detected - every fourth beat, counted off from the first. That's fine on a straight 4/4 rock track and close to worthless on electronic music, where it measured 0-2% correct. It's a real detection now, so if you exported a grid from an EDM or phonk track and found the bar markers useless, re-export it.

Free beat export - three formats scripters actually use

Onset Engine can export any track's detected beat grid directly. One click in the audio bin (the ⇩ BEATS button), or one command:

OnsetEngine.exe export-beats song.mp3

You get three files, written next to your audio:

• song_beats.funscript - The beat grid as a metronome pattern (alternating strokes on every beat). Loads into OFS, script players, and heatmap tools as a timing reference track you script over or against.
• song_beats.txt - An Audacity label track: every beat is a point label, downbeats labeled separately so bar starts stand out. In Audacity: File → Import → Labels, and the whole grid is scrubbable.
• song_beats.csv - Plain time_s,type rows (beat / downbeat) for your own tooling.

A few honest notes:

• It runs 100% locally. Nothing uploads. Same privacy story as the rest of Onset Engine.
• It's included in the free demo - beat export isn't paywalled. Take the grid and use it in OFS even if you never render a video.
• It is not a script generator. It won't watch a video and write motion for you (motion-tracking tools on Eroscripts do that). This is beat timing - the metronome, not the choreography.

Where this meets PMV and cock hero creation

The overlap is the interesting part. A cock hero is a beat grid made visible; a funscript for one is that same grid made physical. Onset Engine works both sides:

1. Editing side - It auto-cuts your clips to the beat grid (that's the core product - see the cock hero maker page)
2. Scripting side - It hands you the same grid as funscript/labels, so the script and the edit are built on identical timing

If you release a beat-synced video and a script for it, both came from one detection pass - no drift between what viewers see and what devices do.