4 ms·
"low-delay", "WebRTC" ... choose one. I really don't get why everything needs to be in a web browser nowadays. WebRTC is simply the wrong choice for low-delay
by fxtentacle 6y ago
"low-delay", "WebRTC" ... choose one.
I really don't get why everything needs to be in a web browser nowadays. WebRTC is simply the wrong choice for low-delay audio streaming. Audinate's DANTE protocol has been around for 14 years, is affordable, hardware-accelerated, and has practically no avoidable latency when sending audio over the network.
Why add 20+ms of latency just to use WebRTC?
- musicale 6y agoGood question; JackTrip normally uses UDP and I think most browsers do not support sending UDP packets directly without an extension. If you could send UDP directly then WebRTC could presumably be avoided.
- mdonahoe 6y agoDoesn’t webrtc use UDP?
- fxtentacle 6y agoIn some cases on some web browsers WebRTC can be configured to use UDP. But that's exactly the problem. Usually, nobody knows what's actually happening in that 20000+ lines of code WebRTC stack.
- deleted 6y ago[deleted]
- jdc 6y agoDante is proprietary for one thing.
- fxtentacle 6y agoHere's a GPL implementation https://github.com/jsharkey/wycliffe https://github.com/jsharkey/wycliffe
- jdc 6y agoThanks! Have you had any luck running it? It doesn't seem to have any documentation.
- Blueskytech 6y agoCompletely agree, while proprietary what Audinate has done with Dante is nothing short or a miracle. With their PCI-E FPA I have less then a 2ms round trip latency with my Hilo interface at 96Khz resolution. Additionally the virtual sound card can do 4ms latency in one direction with most modern CPUs.