Show HN: Real-time AI Voice Chat at ~500ms Latency
81–90 of 238 posts
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#82Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#83Earlier quoted context omitted.
> where it processes the incoming speech in real time and responds when it's confident it has heard enough to understand the meaning. I'm not an expert on LLMs but that feels completely counter to how LLMs work (again, _not_ an expert). I don't know how we can "stream" the input and have the generation update/change in real time, at least not in 1 model. Then again, what is a "model"? Maybe your model fires off multi…
You're right, this is not solvable with regular LLMs. It's not possible to mimic natural conversational rhythm with a separate LLM generating text, a separate text-to-speech generating audio, and a separate VAD determining when to respond and when to interrupt. I strongly believe you have to do everything in one model to solve this issue, to let the model decide when to speak, when to interrupt the user even. The onl…
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#84I did some research into this about a year ago. Some fun facts I learned: - The median delay between speakers in a human to human conversation is zero milliseconds. In other words, about 1/2 the time, one speaker interrupts the other, making the delay negative. - Humans don't care about delays when speaking to known AIs. They assume the AI will need time to think. Most users will qualify a 1000ms delay is acceptable…
A lot better techniques exist now days than pure silence detection - 1. A special model that predicts when a conversation turn is coming up (e.g. when someone is going to stop speaking). Speech has a rhythm to it and pauses / ends of speech are actually predictable. 2. Generate a model response for every subsequent word that comes in (and throw away the previously generated response), so basically your time to speak…
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#85This is great. Poking into the source, I find it interesting that the author implemented a custom turn detection strategy, instead of using Silero VAD (which is standard in the voice agents space). I’m very curious why they did it this way and what benefits they observed. For folks that are curious about the state of the voice agents space, Daily (the WebRTC company) has a great guide [1], as well as an open-source f…
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#86I did some research into this about a year ago. Some fun facts I learned: - The median delay between speakers in a human to human conversation is zero milliseconds. In other words, about 1/2 the time, one speaker interrupts the other, making the delay negative. - Humans don't care about delays when speaking to known AIs. They assume the AI will need time to think. Most users will qualify a 1000ms delay is acceptable…
What about on phone calls? When I'm on a call with customer support they definitely wait for it to be clear that I'm done talking before responding, just like AI does.
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#87I did some research into this about a year ago. Some fun facts I learned: - The median delay between speakers in a human to human conversation is zero milliseconds. In other words, about 1/2 the time, one speaker interrupts the other, making the delay negative. - Humans don't care about delays when speaking to known AIs. They assume the AI will need time to think. Most users will qualify a 1000ms delay is acceptable…
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#88After interrupt, unspoken words from LLM are still in the chat window. Is LLM even aware that it was interrupted and where exactly?
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#89Call me when the AI can interrupt YOU :)
Re: Show HN: Real-time AI Voice Chat at ~500ms Latency
#90Kind of surprised nobody has brought up https://www.sesame.com/research/crossing_the_uncanny_valley_... It interacts nearly like a human, can and does interrupt me once it has enough context in many situations, and has exceedingly low levels of latency, using for the first time was a fairly shocking experience for me.
Didn't expect it to be that good! Nice.