The first Media over QUIC CDN: Cloudflare

(moq.dev)

292 points kixelated | 1 comments | 22 Aug 25 18:24 UTC | HN request time: 0.298s | source

Show context

englishm ◴[22 Aug 25 19:11 UTC] No.44988596[source]▶

>>44987924 (OP) #

Hi! Cloudflare MoQ dev here, happy to answer questions!

Thanks for the award, kixelated. xD

replies(6): >>44989011 #>>44989230 #>>44989615 #>>44989828 #>>44990875 #>>45005783 #

VoidWhisperer ◴[22 Aug 25 20:47 UTC] No.44989615[source]▶

>>44988596 #

> No head-of-line blocking: Unlike TCP where one lost packet blocks everything behind it, QUIC streams are independent. A lost packet on one stream (e.g., an audio track) doesn't block another (e.g., the main video track). This alone eliminates the stuttering that plagued RTMP.

It is likely that I am missing this due to not being super familiar with these technologies, but how does this prevent desync between audio and video if there are lost packets on, for the example, the audio track, but the video track isn't blocked and keeps on playing?

replies(4): >>44989653 #>>44989669 #>>44989720 #>>44992530 #

1. madsushi ◴[22 Aug 25 20:53 UTC] No.44989669[source]▶

>>44989615 #

Depending on the streaming protocol (eg WARP), you can specify that the tracks (audio vs video) need to be time-aligned, so each group (chunk of video or audio) starts at the same time and lasts the same length. I think this means you'll get resync'd at the start of the next group.

↑