-
Notifications
You must be signed in to change notification settings - Fork 583
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
Support Multisegments for TTS input #1288
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 95a6fbe The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@utils.log_exceptions(logger=logger) | ||
async def _run_segments(): | ||
async for input_stream in self._segments_ch: | ||
await self._run(input_stream) |
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 will not reuse the existing connection? (I know Cartesia supports having multiple segments without disconnecting, 11labs may too but I'm not sure)
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.
I don't think 11labs supports it, I've updated code for rest of plugins to reuse ws connection
6aa7514
to
37bbfcc
Compare
tests/test_tts.py
Outdated
stream.end_input() | ||
stream.flush() | ||
if i == 1: | ||
stream.end_input() | ||
|
||
frames = [] | ||
is_final = False |
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.
each segment should have its own is_final
This PR implements support for multiple segments in tts input