DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to transcribe a recording and show who spoke when with Paddock

Get a transcript and a speaker timeline for a recording of up to 10 minutes on your own machine.

Authorization notice. Paddock is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA researcher, journalist or team lead who needs a written record of a short interview or meeting with clear speaker turns.

The problemSorting out who said what in a transcript is tedious, and uploading recordings to a hosted service may not suit the content.

The outcomeA transcript with speaker turns shown on a timeline, including overlapping speech, produced locally.

What you need first

  • An NVIDIA GPU with the NVIDIA driver installed, or an Apple Silicon Mac running macOS 26 or later
  • Download access to the Paddock release page on GitHub (Windows, Linux, Linux arm64 on DGX Spark, or macOS)
  • Disk space for the model checkpoints you choose to download
  • For cloud comparison: an account with an OpenRouter or other OpenAI-compatible endpoint, if you want to compare against a cloud model

Steps

  1. Run paddock and open the Studio.
  2. Download Qwen3-ASR 1.7B for transcription and Nemotron 3 Diarization for speaker turns.
  3. Open the recording in the Studio, keeping it under 10 minutes for diarization.
  4. Run transcription and diarization on the recording.
  5. Read the speaker timeline and correct any turns that look wrong.

Prompt for your agent

Using the Paddock repo at truespar/paddock, transcribe the audio file <path-to-audio> and run speaker diarization on it. Return the transcript with speaker labels. Verify that the audio is under 10 minutes long before running diarization.

Caveat. The README says diarization works on recordings up to 10 minutes, so longer meetings will need to be split first.

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