I think it's better to join some kind of club if you want to make friends?
How OpenAI delivers low-latency voice AI at scale
61–70 of 172 posts
Re: How OpenAI delivers low-latency voice AI at scale
#62Earlier quoted context omitted.
slightly unrelated but what’s with storing the entire codebase in the root directory instead of a nested src folder? It makes getting to the README a lot more difficult
This is valid criticism. Go fanbois don't like listening to any go criticism. They were all like who needs templates in go. and now go has templates. To me go code looks like somebody vomitted stuff in the root dir and i have to wade through that every time. No namespacing. nothing
[deleted]
Re: How OpenAI delivers low-latency voice AI at scale
#63Earlier quoted context omitted.
slightly unrelated but what’s with storing the entire codebase in the root directory instead of a nested src folder? It makes getting to the README a lot more difficult
This is valid criticism. Go fanbois don't like listening to any go criticism. They were all like who needs templates in go. and now go has templates. To me go code looks like somebody vomitted stuff in the root dir and i have to wade through that every time. No namespacing. nothing
I don't like go as a personal preference but reducing them to "fanboys" is a bit reductive. I'm sure the same could be said about your own favorite language.
Re: How OpenAI delivers low-latency voice AI at scale
#64Am I reading this right that OpenAI is not using Livekit for WebRTC/audio anymore?
It does appear that way. The LiveKit server is not what you would want for this architecture anyway (as they basically say with the SFU discussion), although it does have a lot of useful stuff in the client SDKs.
Re: How OpenAI delivers low-latency voice AI at scale
#65Wait a minute... I’m genuinely happy that they are sharing this, but keep in mind that realtime audio model from OpenAI are still stuck with the 4o family in terms of capabilities, sadly. I still find them so useful, such a pity that there’s no real competitor in this segment, having the experience a real conversation has helped me so much in expressing ideas and concepts.
Still, it’s worth to keep in mind that these are not frontier models, differently from when they were released.
(Please Sam, if you read this, release the new realtime audio models)
Re: How OpenAI delivers low-latency voice AI at scale
#66if anyone is looking to get into this. pipecat is a great open-source repo and community. https://github.com/pipecat-ai/pipecat
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
Yeah Gemma4 was and is great fun to do this with - I too am building pretty much the same as yourself in Go.
https://github.com/zarldev/zarl & https://www.zarl.dev/posts/hal-by-any-other-name
Re: How OpenAI delivers low-latency voice AI at scale
#67The low latency is more of a pain point than a good thing, the way they have it implemented. Trying to have a casual conversation with it, as humans we naturally pause, and GPT will take this as you are "done" and start blabbing away. I 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 th…
Hard problem. I find myself adding in filler to stop the thing from jabbering. I also think it spends most of its iq on sounding good rather than thinking about the problem. “Yeah absolutely I can see why you’d like to…” etc. This is likely because it’s on a timer and maybe voice is more expensive to process? Text responses spend more time on the task.
Fwiw you can prompt it to respond differently to you.
Re: How OpenAI delivers low-latency voice AI at scale
#68Earlier quoted context omitted.
slightly unrelated but what’s with storing the entire codebase in the root directory instead of a nested src folder? It makes getting to the README a lot more difficult
This is valid criticism. Go fanbois don't like listening to any go criticism. They were all like who needs templates in go. and now go has templates. To me go code looks like somebody vomitted stuff in the root dir and i have to wade through that every time. No namespacing. nothing
[deleted]
Re: How OpenAI delivers low-latency voice AI at scale
#69The low latency is more of a pain point than a good thing, the way they have it implemented. Trying to have a casual conversation with it, as humans we naturally pause, and GPT will take this as you are "done" and start blabbing away. I 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 th…
This has more to do with Voice Activity Detection (VAD) than the latency described in the article
Re: How OpenAI delivers low-latency voice AI at scale
#70Am I reading this right that OpenAI is not using Livekit for WebRTC/audio anymore?
It does appear that way. The LiveKit server is not what you would want for this architecture anyway (as they basically say with the SFU discussion), although it does have a lot of useful stuff in the client SDKs.
They do link to the Livekit docs in the footnotes: https://docs.livekit.io/transport/self-hosting/kubernetes/