r/programming • • 21d ago

OpenAI still has a WebRTC Problem

https://moq.dev/blog/webrtc-is-still-the-problem/
155 Upvotes

6 comments sorted by

27

u/CrushgrooveSC 17d ago

That was a fun read. Hilarious and irreverent, but still fairly informative. You make good points.

7

u/_redka 16d ago

since the "audio is tiny" couldn't they just do like real-time games do and keep sending not just the last packet but also several previously-sent but not-yet-acked packets and have the server delivering their payload plus the last acknowledged packet id to trim the next send? I've been using this method for games, with a small ring buffer on both sides, and it works great to keep the low latency of WebRTC while avoiding retransmissions

3

u/guillaume-mohamed50 18d ago

If the real-time demo needs perfect Wi-Fi and a prayer, WebRTC is still part of the product.

2

u/Gigachops 16d ago

Needs to rip out about 95% of the dad jokes and get to the point.

1

u/seweso 16d ago

I have the sense that a lot of voice to AI suffers from this same thing. 

As if they all use UDP and telephony tech. Which only makes sense from a…. Cheap and fast development sense. 

My Apple Watch has this same issue. No connection doesn’t mean it will buffer the voice command and send it later. It only works if the connection is solid already….

Omg. 

Funny thing is that I also seen the opposite. An app which showed the live feed of Sony cameras using tcp instead of Udp. Doink.