Authorization notice. Speech CPP is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Remote script. The install step runs a script fetched from the internet, so review it before running.
Who it is forA content creator, teacher or developer who needs narration for a video, lesson or prototype and wants to avoid a paid voice service.
The problemRecording narration takes time, and cloud text-to-speech may be costly or send private scripts off the machine.
The outcomeA WAVE file with the spoken text, produced locally from a named voice.
What you need first
- macOS on Apple silicon, Linux on x86-64, or Windows x64
- Internet access to fetch the installer and models from Hugging Face the first time
- Free disk space for the model files, for example 1.21 GB for qwen3-tts-0.6b
- A terminal (PowerShell on Windows)
- A microphone, for live transcription
Steps
- Install speech using the installer for your platform.
- Run
speech tts qwen3-tts-0.6b --voice ryan -o hello.wav "Hello. It will be sunny in Tokyo tomorrow."to make the first file. The model is fetched the first time. - Replace the quoted text with your own sentence, or pipe a file to stdout with
speech tts qwen3-tts-0.6b --voice ryan -o -(inferred from the README's note that output can go to stdout). (inferred, check the README) - Play hello.wav and check the pronunciation.
Prompt for your agent
Using the nyosegawa/speech.cpp repo, install speech and run `speech tts qwen3-tts-0.6b --voice ryan -o <output>.wav "<script text>"`. Expected output: a WAVE file at the path given, with the script spoken in the ryan voice. Verify that the file plays and matches the script.
Caveat. The first run downloads a 1.21 GB model, so plan for that time and disk space before generating audio.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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