-
Notifications
You must be signed in to change notification settings - Fork 553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
services: fix some TTS websocket service interruption handling #1272
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
|
e26c413
to
38019f5
Compare
38019f5
to
94ee664
Compare
@@ -434,6 +436,12 @@ async def _stop_frame_handler(self): | |||
|
|||
|
|||
class WordTTSService(TTSService): | |||
"""This a base class for TTS services that support word timestamps. Word |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"""This a base class for TTS services that support word timestamps. Word | |
"""This is a base class for TTS services that support word timestamps. Word |
this to work, the TTS service needs to support handling multiple requests at | ||
once (i.e. multiple simultaneous contexts). | ||
class WebsocketTTSService(TTSService, WebsocketService): | ||
"""This a base class for websocket-based TTS services.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"""This a base class for websocket-based TTS services.""" | |
"""This is a base class for websocket-based TTS services.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same typo in other docstrings.
Please describe the changes in your PR. If it is addressing an issue, please reference that as well.
@markbackman We already talked about this before. People are really hitting this issue, so even if not nice we need to support all TTS services as good as we can.
I did an optimization though. If the bot is not speaking and the user talks, we don't reconnect. We only reconnect if it's a real interruption.
Fixes #1258