DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to score a launch film's audio against pro launch films with earshot

Run a scorecard that lists timestamped fixes for your film's soundtrack and mix.

Seen in the wild

Evidence: X, Oct 2026 · X, Oct 2026

Similar to what people reported. The steps and prompt below are AI written, not copied from those posts.

Who it is forFounder or motion designer finishing a launch video and unsure if the mix is up to standard

The problemThere is no objective way to know if the soundtrack is too quiet, too thin or late compared to professional launch films.

The outcomeA verdict with scored metrics and a numbered list of timestamped fixes, worst first.

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. Export your film as a video file with audio.
  2. Run earshot critique film.mp4 on it.
  3. Read the VERDICT and the FIX FIRST list.
  4. Apply the top fixes in your audio code or editor, then run the critique again.

Prompt for your agent

Run earshot critique on <film.mp4> and summarize the verdict and the top three timestamped fixes. Verify by re-running critique after the changes and comparing how many metrics are in range.

Caveat. The scorecard compares against a profile of 7 professional launch films, so it suits launch and promo styles, not every genre.

About earshot

Gives coding agents ears: they can listen to audio, review it and generate sound. Runs on a plain CPU and is open source. View Leonxlnx/earshot on GitHub.

More with earshot

See all use cases for Leonxlnx/earshot

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