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

How to find the exact moment of a sound in a long recording with Earshot

Locate the best matching moments inside a long file and get sample trims for each.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA video editor or agent cutting a film or game that has a long ambient or field recording and needs one specific sound from it.

The problemScrubbing a long recording to find one clean hit or key press is slow and error prone.

The outcomeA short list of start and end times for the best matches, ready to trim.

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 find keys.ogg "a single mechanical key press" --top 4 to list the best moments.
  2. Note the start and end seconds of the strongest match.
  3. Run earshot describe keys.ogg to check the file as a whole before you trim. (inferred, check the README)

Prompt for your agent

Use the earshot repo at <repo path>. Run `earshot find <file> "<description>" --top 4` and return each moment as start and end seconds with its strength. Verify that each returned interval lies inside the file length before you trim.

Caveat. Results depend on the description wording, so try two or three phrasings if the top moments do not match what you hear.

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