Viewing profile — vr000m

I think being able to code by talking is going to be the future. However we need to figure out how to switch between different projects and have it do what I mean and not what i sa…

The latencies in the table are based on heuristics or averages that we’ve observed. However, in reality, based on the conversation, some of the larger latency components can be muc…

Daily now supports dial-in and dial-out, https://docs.daily.co/guides/products/dial-in-dial-out#main Which means you can connect a bot to a call, and tell it dialout to a phone num…

High level overview of how video is delivered to 100,000 participants using mesh/cascaded video routers (aka, SFUs) with 200ms latency. Servers are geographically spread, servers c…

Reminds me if the work from @lkozma in 2007, http://www.lkozma.net/wpv/

Agreed, all of the early HTTP based streaming was about HTTP progressive download. Microsoft’s smooth streaming was dominant in the early 2000s used it too. Glad that Twitch has be…

Agreed and thank you for the contribution. Alas, the work is now embroiled in breaking it apart into smaller parts.

Unfortunately modern routers made multicast unrounable, otherwise, we’d all be using mbone

All the listed protocols came after HTTP. RTSP, SIP borrowed heavily (albeit badly in retrospect) from HTTP. I do not have all the historical context (early 90s), but for WebRTC, t…

Pavlov’s comment is correct. I came to add that soon the stream can be stored on customer’s own S3. Ergo, you’d be able to do a call in real-time, store it on your S3 account and m…

In the case of QUIC, it is likely that the streaming would be over H/3 (HTTP3) or HTTP over QUIC. They may fallback to H1 or H2 but typically over a long enough time, firewall rule…

Most common browser implementations use an Open GOP. That means an IFrame is implemented when needed. On scene change or when there’s high motion. Only naive implementations would …

Webrtc protocol doesn’t dictate 1 or 2. Although browsers do implement some of their own assumptions for this. By default the client side buffer can be orders of 100s of millisecon…

ICE is needed when both parties are NATes, if one party was not mated, we’d not need ICE in webrtc either. Agree on 2. On 3. The videobridge needs state on who is on the session an…

A future blogpost will talk about all the networking work that went into optimizing for these large size participation. Webrtc uses a few protocols. RTP is very central to it, ICE …

Agreed. My calculations are totally skipping finding/updating the manifests or exchanging the SDP Offer/Answers.

Media over QUIC is interesting. For RTP or peer to peer QUIC, there is more work to be done. But you will end up engineering many of the same things as webrtc suit of protocols (IC…

Low latency HLS is creating partial segments by bucketing 200ms of frames instead of 6s segments in standard HLS. Whereas in webrtc, the endpoint is sending the frame as soon as it…

One thing to consider is if you would have One API and a few knobs to control the experience and not have to worry about the underlying protocol-, reliability-, latency- aspects to…