- README explaining experimental/transparency purpose - faster-whisper STT backend (fw-stt.mjs, faster-whisper-server.py, install-faster-whisper.sh) - Bug fixes: Buffer alignment in on_audio, --debug-waveform URL parsing, silent fetch errors, instant dispatch timer leak - Global uncaughtException/unhandledRejection handlers in query-demo.mjs - Design docs: CHANGELOG, COMMAND-DISPATCH, INTERFACE-THEORY, VOICE-POLICY - Systemd service unit templates Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.0 KiB
Voice Policy
Project stance on voice cloning
This project ships no voice samples and endorses no specific voice. The TTS system (Chatterbox) supports voice cloning via a reference audio sample — the user provides their own.
Guidance for users: customising the voice
We provide instructions for how to prepare a voice sample. What you clone is your choice and your responsibility.
How to prepare a voice sample:
- Find audio of the voice you want — TV show, podcast, audiobook, whatever appeals to you
- Cut out a clean 10–30 second clip with clear speech, no background music, minimal noise
- Use Audacity (or equivalent) to: reduce noise, normalise loudness, export as WAV
- Pass the file as
--audio-promptor configure it invoices.yaml
Quality tips:
- Avoid clips with background music — it bleeds into the synthesised voice
- Multiple shorter clips tend to work better than one long one
- Emotional range in the source clip produces more expressive output
Public framing
We treat voice customisation similarly to ringtones: a personal preference the user configures for themselves, using material they have access to. We do not distribute voice samples, do not name or reference specific shows, actors, or productions, and do not encourage or assist with commercial exploitation of anyone's voice.
Users are responsible for complying with the laws of their jurisdiction, including right of publicity and copyright. For personal, non-commercial use this is generally low-risk. For public or commercial deployments, use a commissioned voice actor with a proper release.
Demo videos
Using a cloned voice in a demo video is low practical risk:
- No commercial transaction, no product being sold
- Transformative use — demonstrating a technical tool, not reproducing entertainment
- Amount of cloned audio is small
- Fan/hobbyist use of fictional AI voices from TV shows is extremely common and essentially never enforced
Realistic risk threshold: only if the video went massively viral and the production company or actor decided to make an example of it. For a niche open source demo this is negligible.
Recommendation: use the voice in demos freely. Do not name the project after the fictional character or actor, and do not distribute the source audio sample.
In the unlikely event of a takedown request from the production company or actor, the appropriate response is simply to comply — edit or remove the video. This is a low-friction outcome and not a legal or financial threat.
Response plan if takedown occurs:
- Comply immediately
- Publicly note who made the request and why — the Streisand effect tends to do the rest
- Remake the demo with a fully synthetic voice, cloned own voice, or commissioned voice — the project stands on its technical merits regardless of which voice is used
Project name
The project does not use a name referencing any fictional AI character, show, actor, or voice. Name TBD — working title "voice buddy" for the dispatcher component.