Desktop

Name speakers on local transcripts

OpenASR Desktop Voice ID lets you enroll a voiceprint and attach a name to that speaker on future transcripts. It runs with built-in MOSS speaker separation for multi-person meetings and interviews, fully on your machine. Voice ID is a diarization convenience feature, not authentication or identity verification.

Where it runs
OpenASR Desktop on macOS and Windows; processing stays local by default
What you enroll
A voiceprint tied to a display name for that speaker on the transcript
Separation engine
Built-in MOSS speaker separation for multi-person audio
What it is not
Not login, access control, or biometric authentication

How Voice ID fits a meeting or interview

Multi-person audio is first separated so turns can be attributed to distinct speakers. When a voice matches an enrolled voiceprint, Desktop can show the name you assigned instead of a generic speaker label.

That makes review faster when the same people recur across recordings—clients, colleagues, or recurring interview subjects—without sending audio to a remote transcription service.

Local by default

OpenASR is local-first speech-to-text. Desktop does not require an account, does not phone home telemetry, and does not route ordinary transcription through a central cloud backend.

Models come from a signed catalog. Normal transcription does not silently auto-download models; you choose what is installed and used on the machine.

Models that support Voice ID

Not every model in the marketplace is marked for Voice ID. Desktop surfaces which models support the feature so you can pick a stack that matches enrollment and naming, not guess from generic labels.

  • Enroll a voiceprint and assign a display name
  • Use MOSS separation on multi-person meetings and interviews
  • See named speakers when a match is available on a supporting model
  • Keep enrollment and transcription on-device

CLI and API counterparts

If you automate pipelines outside Desktop, the open-core CLI and local HTTP API also expose diarization and speaker enrollment paths, including a /v1/speakers API with a WeSpeaker capability pack.

Desktop Voice ID is the product-facing enrollment and naming experience; the open core remains Apache-2.0 Rust CLI plus local HTTP API for scripted workflows.

Frequently asked questions

Is Voice ID the same as logging in or verifying identity?

No. Voice ID is a diarization convenience: it helps label speakers on a transcript from enrolled voiceprints. It is not authentication, access control, or proof of legal identity.

Do I need the cloud for Voice ID?

No. OpenASR Desktop runs Voice ID and MOSS speaker separation locally by default. There is no account requirement and no central cloud transcription backend for ordinary use.

Which platforms support Desktop Voice ID?

OpenASR Desktop is available for macOS and Windows. There is no native Linux desktop app; Linux users can use the open-core CLI, local HTTP API, or container images instead.

Do all models support Voice ID?

No. Models that support Voice ID are marked in the marketplace. Choose a marked model when you need enrollment and named speakers on the transcript.

Can I do speaker work without Desktop?

Yes. The open-core CLI supports --diarize and speaker enrollment, and the local server exposes a /v1/speakers API with a WeSpeaker capability pack for automated pipelines.

Speaker diarization app Local meeting and interview separation with MOSS, with optional named speakers. Diarization docs CLI --diarize, speaker enroll, and the /v1/speakers API. Desktop Voice ID release What shipped with Desktop Voice ID and how enrollment fits the workflow. Download Get OpenASR Desktop for macOS or Windows.