3 ms·
I know there are information theory tradeoffs, but if you want to go really fast, use JPEG. Specifically, LibJpegTurbo. I have been playing around with this, a
by bob1029 6y ago
I know there are information theory tradeoffs, but if you want to go really fast, use JPEG. Specifically, LibJpegTurbo.
I have been playing around with this, and it is fast enough to encode a 1080p+ 8bpp framebuffer in under 5 milliseconds. This is fast enough for interactive applications. Most web browsers likely use something similar to this, so as long as you encode quickly on the server you can expect fast decode on the client.
- parhamn 6y agoInteresting! Do you have an example of how such a thing could be used in an interactive language?
- bob1029 6y agoThink about extreme forms of server-side rendered applications where you need to keep the client device as simple, cheap and locked-down as possible. All you need are 2 streams: 1 from client-to-server w/ all touch/keyboard events, and another from server-to-client with JPEG frames. One could easily build client devices using FPGAs or other integrated technologies with this sort of architecture. The only caveats are latency & bandwidth requirements, but there are strategies for managing this, as well as problem domains where sufficient constraints exist on both counts (i.e. secure local networks).