Sub-issue: speaker diarization
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 13d 17h
- Merged PRs (30d)
- 4
Description
## What
Add speaker diarization so transcripts can separate who said what.
## Why
Without diarization, meeting transcripts are harder to read and summaries lose context. This is one of the main feature gaps compared with Meetily.
## How
- define a diarization step in the Rust backend
- detect speaker segments from recorded audio
- attach speaker labels to transcript chunks
- render speaker-aware transcript UI in the frontend
- make it optional so local-only installs still work well on modest hardware
Parent: #51
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading parent issue #51 and tracing the existing Rust backend transcription flow and frontend transcript rendering. Define how recorded-audio speaker segments map to transcript chunks, then verify optional behavior for local-only installs and speaker-aware rendering across both areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- audio-video-rtc, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100