You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- ⚠️ `WebsocketTTSService` subclasses and `DeepgramSageMakerTTSService` no longer report processing metrics, which were meaninglessly reporting zero on every turn. The metric is `ProcessingMetricsData` in `MetricsFrame`, surfaced as the `processing` field of RTVI's `metrics` message. TTS services whose processing time was a real number are unaffected.
2
+
3
+
Processing time is measured around `run_tts`. For a service that requests audio and waits for it in that call, that covers the real work. `WebsocketTTSService` subclasses instead push the text onto the socket and return, leaving the audio to arrive on a separate receive task, so the measurement only ever covered the send. `DeepgramSageMakerTTSService` does the same over bidirectional HTTP/2. TTFB and TTFA measure the latency that matters for all of them, and are unaffected.
4
+
5
+
There's a new `TTSService.supports_processing_metrics` property, which defaults to `True`. Set it to `False` on a custom service whose `run_tts` returns before synthesis finishes, or back to `True` on a `WebsocketTTSService` subclass that waits for the server to signal the end.
0 commit comments