what i learned from making a webrtc+kubernetes game streaming product: - openai is wrong. almost of the issues they described are issues with libwebrtc, not with webrtc, kubernetes, network architecture, etc. the clue was when they said "the conventional one-port-per-session WebRTC model." - there are no alternatives worth trying. everything else open source in the ecosystem, like pion, coturn, stunner, are too immat…
How OpenAI delivers low-latency voice AI at scale
21–30 of 172 posts
Re: How OpenAI delivers low-latency voice AI at scale
#22I also suffer from finding the appropriate word I want as I've gotten older and slower, and this fast-voice-gpt just ends up frustrating me more than helping. I have to sit there and think out the whole sentence in my head before I say anything -- not very natural.
Re: How OpenAI delivers low-latency voice AI at scale
#23Re: How OpenAI delivers low-latency voice AI at scale
#24If a transceiver crashes during a stream, how is the active session recovered? Does the system automatically re-establish the context in a new WebRTC session?
Re: How OpenAI delivers low-latency voice AI at scale
#25Earlier quoted context omitted.
I wish I had known about Pipecat a lot sooner. I found out about it a few weeks back, and since Gemma 4 launched, I've been building my own entirely local voice assistant using Gemma 4 + Kokoro TTS + Whisper from scratch - https://github.com/pncnmnp/strawberry . Pipecat's smart turn model is really good for VAD - https://huggingface.co/pipecat-ai/smart-turn-v3
What do you have going on the hardware side? I want to plug this into hass but don’t know what hardware I need for reasonable latency
Re: How OpenAI delivers low-latency voice AI at scale
#26Re: How OpenAI delivers low-latency voice AI at scale
#27Re: How OpenAI delivers low-latency voice AI at scale
#28what i learned from making a webrtc+kubernetes game streaming product: - openai is wrong. almost of the issues they described are issues with libwebrtc, not with webrtc, kubernetes, network architecture, etc. the clue was when they said "the conventional one-port-per-session WebRTC model." - there are no alternatives worth trying. everything else open source in the ecosystem, like pion, coturn, stunner, are too immat…
Even for clients you have things like libpeer that libwebrtc can't hit.