TTS should not be macOS-only in practice
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The README mentions macOS say, which is fine as a starting point, but Windows/Linux users will wonder what happens. A configurable TTS provider, including “disabled” as a clean option, would make the feature feel less platform-specific.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README section describing macOS say, then trace the existing TTS entry point and how it is invoked. Define a configurable provider with a disabled option and verify that Windows and Linux users have a clear, working behavior without requiring macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, python
- Domain
- audio-video-rtc, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100