4 ms·
> Some of WebP is based on VP8 (not VP9) intra coding too Quite an understatement. "Some" here means WebP is literally a single VP8 frame shoved into a RIFF co
by floatboth 9y ago
> Some of WebP is based on VP8 (not VP9) intra coding too
Quite an understatement. "Some" here means WebP is literally a single VP8 frame shoved into a RIFF container :D
Back in the day (holy shit 8 years ago already!) there was a script that added WebP support to WebM-supporting browsers by literally changing the container. Here it is: https://github.com/antimatter15/weppy/blob/master/weppy.js https://github.com/antimatter15/weppy/blob/master/weppy.js
- clouddrover 9y agoThese days there's a WebAssembly build of libwebp which enables WebP support in browsers which don't support it natively: https://webmproject.github.io/libwebp-demo/webp_wasm/index.html https://webmproject.github.io/libwebp-demo/webp_wasm/index.h... I think it's an ideal use case for WebAssembly. It'd be a good way to roll out any future AV1-based image format until native support arrived in all browsers.
- twotwotwo 9y ago> "Some" here means WebP is literally a single VP8 frame shoved into a RIFF container :D Though it's less used than the lossy format, lossless WebP is a thing too; if I said WebP was exactly VP8 intra someone might nitpick that. There's no winning, haha!
- twotwotwo 9y agoHeh, fun consequence I just realized is that, in theory, you don't even have to wait for video-based still formats to be standardized and deployed if you're willing to play some games with single-frame videos. So, like, h.264-based "images" can be shown in most browsers now, and VP9-based in many (but not Safari or IE). And you can fake AV1 images as soon as you get AV1 video. Using video decoding in an odd way like that probably isn't especially practical or wise, but fun that the capability's there/reachable.