Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kixelated
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
Replacing HLS/Dash – Live Mass Fanout with Media over QUIC
(quic.video)
150 points
by
kixelated
3y ago
|
91 comments
62.
▲
by
kixelated
3y ago
Yeah, if you're using WebRTC only for data channels, then 100% you should switch to WebTransport with all due haste. Once Safari adds support of course.
63.
▲
by
kixelated
3y ago
Glad you liked it! It's really difficult to compare the latency of different protocols because it depends on the network conditions. If you assume flawless connectivity, then real-time latency is trivial to achieve. Pipe frames over TC
64.
▲
by
kixelated
3y ago
Absolutely! I'm doing that in my implementation: the main thread immediately transfers each incoming QUIC stream to a WebWorker, which then reads/decodes the container/codec and renders via OffscreenCanvas. I didn't real
65.
▲
by
kixelated
3y ago
Eric Kinnear (linked post; Apple) is the author of the HTTP/2 fallback for WebTransport, so it's safe to say that WebTransport will be available in WebKit at some point.
66.
▲
by
kixelated
3y ago
I'm using AudioWorklet and SharedArrayBuffer. Here's my code: https://github.com/kixelated/moq-js/tree/main/lib/playback/w... It's just a lot of work to get everything right. It&
67.
▲
by
kixelated
3y ago
I maintained the Flash video player at Twitch until I couldn't take it any longer and created an HTML5 player. Flash was a mess. :)
68.
▲
by
kixelated
3y ago
Thanks for WebCodecs! I'm still just trying to get A/V sync working properly because WebAudio makes things annoying. WebCodecs itself is great; I love the simplicity.
69.
▲
by
kixelated
3y ago
The protocol can do it, but libsctp (used by browsers) was not coalescing ACKs. I'm not sure if it has been fixed yet.
70.
▲
by
kixelated
3y ago
Are you referencing this line? > 2x the packets, because libsctp immediately ACKs every “datagram”. The section is about data channels, which uses SCTP and is ACK-based. Yes, you can use RTP with NACK and/or FEC with the media stack
71.
▲
Replacing WebRTC: real-time latency with WebTransport and WebCodecs
(quic.video)
301 points
by
kixelated
3y ago
|
77 comments
72.
▲
by
kixelated
3y ago
Not yet but one day: https://github.com/WebKit/standards-positions/issues/18#issu...
73.
▲
by
kixelated
3y ago
Hey HN, I spent some of my downtime between jobs making a proof-of-concept for a new live media protocol in development at IETF: Media over QUIC. Everything is in an extremely early stage so don't expect it to work, but now is a great
74.
▲
quic.video - Live Media over QUIC
(quic.video)
6 points
by
kixelated
3y ago
|
3 comments
75.
▲
by
kixelated
4y ago
Oh yeah, QUIC is an improvement in terms of latency and even throughput over TCP/TLS. The claim that "QUIC is horribly inefficient" centers around CPU utilization and the cost of delivering each byte. That's where hardwa
76.
▲
by
kixelated
4y ago
You can use QUIC without the HTTP/3 layer on top. It's a general purpose replacement for TCP+TLS.
77.
▲
by
kixelated
4y ago
You're right that HTTP/3 requires Alt-Svc at the moment. QUIC itself doesn't require a pre-established connection (1-RTT), which is notable for non-HTTP/3 protocols and WebTransport.
78.
▲
by
kixelated
4y ago
Kernels and hardware have been optimized for TCP. QUIC will catch up eventually.