WebRTC doesn't give up on late audio. This isn't factually correct. WebRTC has NACKs[0]. The receiver (AI Inference server) decides when to either accept the gap in RTP packets or if it sends the NACK and waits.
This article doesn't describe how Voice AI systems I work on operate. For speech-to-speech I am working at 20ms/200ms chunks and doing inference. So I don't want buffers
What I find frustrating about these sales pitches that conflate the different parts of WebRTC. WebRTC is protocol, sdk/software and a API in the browser. So if one part has an issue it is important to explain it with detail.
It's like attacking HTTP by saying 'HTTP is bad because this server doesn't have Y setting'.
If I were "Sean-Der," I would not reply. The "being wrong on the Internet causes smart people to write smarter stuff that's interesting to read" discourse is over. You have to own how much of a waste of time it is.
Sean is not the only developer who has used WebRTC, and conferencing is not the only thing MoQ can be used for. I'd really like to see more devs weighing in, especially those with WebRTC experience
The moq people, and they are loud and obnoxious, have this incredible ability to ignore the practical experience that led to the defaults of various systems being what they are while believing the solution is to expose every possible to dial to them so they can eventually rediscover the same results, which presumably they will smugly and obnoxiously broadcast as new discoveries to celebrate their brilliance.
It's like that famous saying about a certain group of people: you can always rely on them to do the right thing, after they've tried every other possibility. They could at least exhibit some level of self awareness.
This article doesn't describe how Voice AI systems I work on operate. For speech-to-speech I am working at 20ms/200ms chunks and doing inference. So I don't want buffers
[0] https://webrtcforthecurious.com/docs/06-media-communication/...
It's like attacking HTTP by saying 'HTTP is bad because this server doesn't have Y setting'.
I respond because incorrect info will cause developers to make bad decisions/build the wrong thing.
It's like that famous saying about a certain group of people: you can always rely on them to do the right thing, after they've tried every other possibility. They could at least exhibit some level of self awareness.