Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

[Infra] Mumble Bridge — Voice Chat Between Alexander and Timmy #858

New Issue
Closed
opened 2026-03-21 22:21:10 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 22:21:10 +00:00
Collaborator
Copy Link

Scope

Set up Mumble voice bridge so Alexander and Timmy can have voice conversations during co-play, with audio piped to the stream.

Requirements

  • Mumble server setup
  • Timmy's TTS output piped to Mumble channel
  • Alexander's microphone captured on stream when co-playing
  • Audio mixing: game audio + Timmy's voice + Alexander's voice
  • Push-to-talk or voice activity detection
  • Stream picks up mixed audio automatically

Used By

  • Phase 4 cohabitation
  • Phase 5 stream audio layer

Assignee: Kimi

## Scope Set up Mumble voice bridge so Alexander and Timmy can have voice conversations during co-play, with audio piped to the stream. ## Requirements - Mumble server setup - Timmy's TTS output piped to Mumble channel - Alexander's microphone captured on stream when co-playing - Audio mixing: game audio + Timmy's voice + Alexander's voice - Push-to-talk or voice activity detection - Stream picks up mixed audio automatically ## Used By - Phase 4 cohabitation - Phase 5 stream audio layer ## Assignee: Kimi
claude self-assigned this 2026-03-24 02:02:58 +00:00
claude commented 2026-03-24 02:19:03 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1324

What was implemented:

  • src/integrations/mumble/bridge.py — MumbleBridge singleton with full bidirectional audio pipeline:
    • speak(text) converts Timmy's TTS output (Piper → pyttsx3 fallback) to 16-bit 48 kHz PCM and transmits it to the Mumble channel
    • send_audio(pcm) for raw PCM injection (e.g. from Timmy's voice loop)
    • push_to_talk() context manager for PTT mode
    • VAD mode with configurable RMS threshold
    • add_audio_callback(fn) to receive Alexander's mic audio from Mumble
    • Pure-Python resampler (no audioop; Python 3.13+ compatible)
    • Graceful degradation when pymumble-py3 is absent
  • 9 new config settings under mumble_* prefix (all env-overridable, disabled by default)
  • docker-compose.yml — mumblevoip/mumble-server under mumble profile for easy local server: docker compose --profile mumble up mumble
  • pymumble-py3 optional dep + mumble extras group
  • 39 unit tests — all green (686 total)
PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1324 **What was implemented:** - `src/integrations/mumble/bridge.py` — `MumbleBridge` singleton with full bidirectional audio pipeline: - `speak(text)` converts Timmy's TTS output (Piper → pyttsx3 fallback) to 16-bit 48 kHz PCM and transmits it to the Mumble channel - `send_audio(pcm)` for raw PCM injection (e.g. from Timmy's voice loop) - `push_to_talk()` context manager for PTT mode - VAD mode with configurable RMS threshold - `add_audio_callback(fn)` to receive Alexander's mic audio from Mumble - Pure-Python resampler (no `audioop`; Python 3.13+ compatible) - Graceful degradation when `pymumble-py3` is absent - **9 new config settings** under `mumble_*` prefix (all env-overridable, disabled by default) - **`docker-compose.yml`** — `mumblevoip/mumble-server` under `mumble` profile for easy local server: `docker compose --profile mumble up mumble` - **`pymumble-py3`** optional dep + `mumble` extras group - **39 unit tests** — all green (686 total)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#858
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?