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

How to transcribe a recording with speakers and subtitles with Fish Audio Hermes

Turn a meeting or interview file into a transcript with speaker turns, timestamps and SRT subtitles.

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

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

Who it is forA person who has a meeting or interview recording and needs a written transcript and subtitle file.

The problemManual transcription is slow, and plain transcripts often do not show who said what or when.

The outcomeA transcript with speaker turns, timestamps and an SRT subtitle file for the recording.

What you need first

  • Hermes Agent installed, with the plugin install command available
  • A Fish Audio account and API key from https://fish.audio/app/api-keys
  • Fish Audio API credit, or the free s2.1-pro-free model for new accounts (free through 30 November 2026)

Steps

  1. Install the plugin with hermes plugins install fish-audio --enable and save your key with hermes fish login.
  2. Place the audio file, for example meeting.m4a, where the Hermes agent can read it.
  3. Ask the agent: "Transcribe meeting.m4a with speakers and give me subtitles."
  4. Check a few timestamps and speaker labels against the original audio before you share the transcript.

Prompt for your agent

Using the repo 100yenadmin/fish-audio-hermes, transcribe <path to audio file> with the fish_transcribe tool, asking for speaker turns, timestamps and SRT output. Expected output: a transcript with speaker labels and an SRT subtitle file. Verify that the first and last timestamps match the start and end of the audio.

Caveat. Speaker labels are produced by the transcription service, so check them against the recording before you rely on them.

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