←back to thread

292 points kixelated | 2 comments | | HN request time: 0.001s | source
Show context
barosl ◴[] No.44989954[source]
I tested the demo at https://moq.dev/publish/ and it's buttery as hell. Very impressive. Thanks for the great technology!

Watching the Big Buck Bunny demo at https://moq.dev/watch/?name=bbb on my mobile phone leaves a lot of horizontal black lines. (Strangely, it is OK on my PC despite using the same Wi-Fi network.) Is it due to buffer size? Can I increase it client-side, or should it be done server-side?

Also, thanks for not missing South Kora in your "global" CDN map!

replies(7): >>44990127 #>>44990314 #>>44992169 #>>44992678 #>>44992792 #>>44993660 #>>44996521 #
kixelated ◴[] No.44990127[source]
Horizontal black lines? Dunno what that could be about, we render to a <canvas> element which is resized to match the source video and then resized again to match the window with CSS.
replies(3): >>44990906 #>>44991688 #>>44992989 #
chrismorgan ◴[] No.44992989[source]
What’s that like for performance and power usage? I understand normal videos can generally be entirely hardware-accelerated so that the video doesn’t even touch the CPU, and are passed straight through to the compositor. I’m guessing with this you’re stuck with only accelerating individual frames, and there’ll be more back and forth so that resource usage will probably be a fair bit higher?

An interesting and unpleasant side-effect of rendering to canvas: it bypasses video autoplay blocking.

replies(2): >>44993164 #>>44993168 #
1. kixelated ◴[] No.44993168[source]
Oh and the autoplay restrictions for <video> don't apply when muted.
replies(1): >>44993177 #
2. chrismorgan ◴[] No.44993177[source]
Depends on your configuration. Firefox has a “block audio and video” option. Which this bypasses.