DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check a launch film's sound and sync with an agent with Earshot

Score a launch video's sound, find where it misses, and get timestamped fixes.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code

Who it is forA developer or agent that generated a product demo or launch film in code and needs to check whether its sound lands on the picture.

The problemAn agent can write the code that renders a film but cannot hear whether a hit lands on its cut or whether the music swells in the right place.

The outcomeA scorecard with a verdict, a list of fixes with timestamps, and an annotated picture of the sound.

What you need first

  • Python and a working earshot install (the install steps are not in the README excerpt provided)
  • A CPU; earshot runs locally on CPU and needs no GPU
  • Sound files to test (WAV, OGG or MP4 with audio)
  • Optional: your own licensed reference recordings for forge (not included in the repo)

Steps

  1. Run earshot critique film.mp4 to get the verdict and the fixes with timestamps.
  2. Run earshot timeline film.mp4 to read the listening transcript with events, sections and sync. (inferred, check the README)
  3. Run earshot sheet film.mp4 -o sheet.png to get an annotated picture the agent can read. (inferred, check the README)

Prompt for your agent

Use the earshot repo at <repo path>. Run `earshot critique <film.mp4>` and `earshot sheet <film.mp4> -o sheet.png`, then list the top fixes with their timestamps and the verdict. Verify that each fix time falls inside the film duration before you edit the render code.

Caveat. The critique compares against a profile of 7 professional launch films, so its scores describe closeness to those films, not an absolute quality grade.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page