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

How to generate a sound effect in code and listen to it with Earshot

Render a sound from a recipe, score it by ear and iterate until it matches the references.

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Who it is forA game or UI developer whose agent needs a custom key press, click or whoosh and has no sound file to start from.

The problemSound effects usually come from a library, so an agent cannot tune one to the exact feel of the product.

The outcomeA set of WAV variants with a report, a spectrogram comparison and an audition file to listen to in pairs.

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 forge --list to see the available recipes and reference sets.
  2. Run earshot forge keypress --refs path/to/real/keypresses/ --budget 144 --variants 4 --dir made/keypress with your own reference folder.
  3. Open made/keypress/report.md and made/keypress/audition.wav to review the picks against the references.

Prompt for your agent

Use the earshot repo at <repo path>. Run `earshot forge --list`, then run `earshot forge <recipe> --refs <folder> --dir <out>`. Report the chosen WAV files and the critic's notes from report.md. Verify that the output folder contains report.json and the WAV files before you use them.

Caveat. The reference recordings are licensed and not in the repo, so you must supply your own with --refs or a local registry, and the README says the model checks can be pleased without the sound getting better, so judge the results by ear and by the model-free measurements.

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