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

How to fix a loud moment or score an existing film with Riso Windowseat

Ask Claude Code to add a score or fix a timed loud passage in a riso film, checked with loudness sheets.

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

Who it is forA filmmaker whose riso film sounds wrong at a specific moment or needs a score added.

The problemFinding and correcting a loud or badly timed sound in a procedural film is slow without measurements.

The outcomeAn updated film where the named audio moment is adjusted or a score is added, with loudness checked.

What you need first

  • Git, to clone the repo
  • npm, since the setup runs npm install and npm run setup
  • Claude Code, the coding agent the README names for making new works
  • A web browser, to open the index.html files and press play

Steps

  1. git clone https://github.com/sevenevesai/riso-windowseat
  2. cd riso-windowseat/tools
  3. npm install && npm run setup && npm test
  4. Open Claude Code in the repo root and name the film and the problem, for example "The rain at 66 s is too loud." or "Score this film."
  5. Review the loudness sheets Claude Code renders with tools/ and listen to the changed passage in a browser.

Prompt for your agent

In the riso-windowseat repo, use the riso-score skill to fix <timestamp and issue> in films/<film-name>/ or to add a score to it. Expect an updated index.html and loudness sheets from tools/. Verify the named moment is quieter or scored and that AUDIO-SOURCES.md lists every audio source used.

Caveat. The README's sound kit and audio sources are CC0 or CC BY licensed, so any added recordings need their own attribution recorded in AUDIO-SOURCES.md.

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