How to build a sound kit for a code-made film with earshot

Who it is forDeveloper making a code-rendered film or app demo who needs whooshes, hits and clicks fast, with no recordings

The problemHunting for and syncing sound effects by hand is slow, and the agent cannot hear what it picked.

The outcomeA kit.json plus rendered takes for every role, each with measured onset, peak and end times.

What you need first

• Python
• CPU only, no GPU needed
• Local models load on first call (about 20 to 40 seconds per CLI call)
• No account or paid key for core features
• Optional Gemini key only for the `llm` command
• Reference recordings for `forge --refset` are not in the repo; bring your own with `--refs DIR`

Steps

1. Run earshot sfx list to see the bank of 201 sounds.
2. Run earshot kit init to start a kit and choose a sound and level per role in kit.json.
3. Run earshot kit render to render the cached takes, then earshot kit check to read the measured sync points.
4. Run earshot sfx render ID -o x.wav to aim any single sound at a moment with --dur, --apex or --pitch.

Prompt for your agent

Use earshot kit to build a sound kit for <film description> with one bank sound per role, render it, and report the measured onset and peak of each. Verify with `earshot kit check` that no role is missing.

Caveat. The sfx and kit commands need no models and no network, but the v0.3 bank is new and the README says no blind-test score for v2 sounds is published yet.

• Markdown version
• JSON version