-
Notifications
You must be signed in to change notification settings - Fork 103
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
Cut answers are still present in the history #396
Comments
Sentences are cuted into multiple messages because the Assistant started answering in between. From my perspective, the issue is Why Assistant didn't spoke between 00:34 and 00:52? It appears that the issue happened once in the conversation, at the first message. The following one seems fine. Each time that the speech timeout is triggered (250 ms by default), voice is stored then LLM is called, and the answer is forwarded piece by piece to the TTS. This process can be interrupted at any time, but it isn't rollbacked. So, if the LLM is interrupted, for example, after the LLM response but before the TTS generation, it'll be stored into the history. A mitigation would be to implement a "transaction", technically a rollback mechanism on "answer aborted" scenario. It would remove this fractioned history with never heard responses. Do you this this would fit your need? Step by step:
|
Yes a rollback mechanism the way you describe it sounds reasonable in my ears when you explain it like that I thought it would be easier and sufficient just still having the option to interrupt the bot but even then also saving the full sentences into the conversation history. You could even mark what parts were pronounced to the user and what part of the ending sentence was used by the application but cut off from the audio. |
This contains "container voice recording 2" with clear audio
This show how normal sentences said by the user are broken up into multiple messages.
It contains examples of sentences cutting off as well
container_call_2.mp4
container_log_2_splitting_of_messages.txt
Transcript.written.before.the.call.that.i.will.follow.t.txt
The text was updated successfully, but these errors were encountered: