v0.8: TCP transport via gatuna tunnel, session IDs, pre-synth playback, server Rust rewrite
This commit is contained in:
+21
@@ -0,0 +1,21 @@
|
||||
# Robovoice Backlog
|
||||
|
||||
## Second-order PTT
|
||||
|
||||
When a game is running, it has its own PTT button (e.g. a voip push-to-talk
|
||||
key). Robovoice should simulate pressing the game's PTT key before TTS audio
|
||||
output begins, and release it after playback finishes.
|
||||
|
||||
This lets the TTS audio be transmitted through the game's voip channel to
|
||||
other players.
|
||||
|
||||
### Considerations
|
||||
|
||||
- Needs a configurable "game PTT key" (separate from Robovoice's own PTT key)
|
||||
- Use `SendInput` or `keybd_event` to synthesize the keypress
|
||||
- Press the game PTT key right before buffered audio starts playing
|
||||
- Release it after `AudioOutput` finishes playback (need a playback-complete
|
||||
signal — currently `Flush()` doesn't provide one)
|
||||
- Edge cases: what if the user presses Robovoice PTT while game PTT is still
|
||||
held from a previous utterance? Flush should release game PTT too.
|
||||
- Should this be a per-output-device setting? (CABLE Output vs speakers)
|
||||
Reference in New Issue
Block a user