© 2026 The ChroniclerHelpFor AI assistantsPrivacyTermsImpressumWiderrufAGBVerträge hier kündigen / Cancel contracts hereSupport
The Chronicler
HelpOpen the app
Help centre / Sessions

Name speakers and voices

Tell The Chronicler who each detected voice is once; confirmed speakers are reused in later sessions and never relabelled.

On this page

  1. When review is asked for
  2. Where to do it
  3. What confirming does
  4. If the mapping is wrong

Transcription labels each distinct voice speaker_0, speaker_1 and so on, numbered per recording — so speaker_1 in one session is not necessarily the same person as speaker_1 in the next. Speaker detection then tries to match those labels to the people and characters it already knows from your campaign. Where it is confident, the session carries on. Where it is not, the session is flagged for review.

When review is asked for

A session needs speaker review when any detected speaker is unconfirmed, has no display name, has a role of unknown, or when the automatic matching isn't confident who the GM is. The session page shows Name voices with the note that highlights and recaps use speaker labels until you do; you also get an email and, if configured, a Discord post.

Transcript-only sources (pasted or uploaded documents, past-session notes) skip detection. YouTube captions arrive as one speaker, so they always need a pass.

Where to do it

  • Wrap-up page (the Review link on the session, or Overview → Catch up). The first section, Speakers — who is who, lists each voice with a sample quote. Type the character or real name and the speaker is confirmed.
  • Full speaker roster (/campaigns/<your-campaign>/speakers) shows every label the campaign has met, grouped under the recording it was heard in. Each card has a Display name and a Role of GM, Player or Unknown; edits save when you click away. You can add a speaker by hand too — a Label (required, e.g. speaker_0), the Recording it belongs to (or Every recording for a campaign-wide default), a display name and a role.

What confirming does

A confirmed speaker carries forward: the next session's detection starts from what you have already named, and processing never overwrites a confirmed row. A name you confirm against one recording stays attached to that recording, because the numbering is per recording. Recaps written in the story form use character names and remove players' real names.

If the mapping is wrong

See Speakers are mislabelled.

Still stuck?

Email support@thechronicler.app and tell us which campaign and session you were looking at.

More in Sessions 8

Record at the table

Record a session straight from the browser. Audio is saved in one-minute pieces as you go, so a dropped connection does not lose the night.

Upload a recording

Upload an audio file up to 500 MB, a transcript file, or a Craig recording link from Discord. Long sessions should be exported as MP3 or M4A first.

Import a transcript or notes

Paste a transcript from Foundry VTT, Roll20, Fantasy Grounds or plain text, import a Roll20 chat log or YouTube captions, or turn old session notes into a session.

What processing does

Upload or record a session and we take care of the rest — transcribing it, working out who's speaking, and writing your recap and an updated wiki, usually within minutes.

Recaps and the three summary forms

Each processed session gets a Review, a Bullets and a Story version of the recap, all written from the same understanding of what happened.

Recap release — who sees a recap and when

Recaps are held from players until released. Choose automatic release the day before your next session, immediate release, or hold for review.

Wrap up a session and lock canon

A short per-session checklist — speakers, new entries, merges, spellings — ending in Lock canon, after which nothing regenerates.

Highlights, handouts and PDFs

Approve the moments worth remembering, generate a "Previously on…" handout for the next game, and download a session as PDF.

← Back to the help centre