Might it be possible to compile this to wasm and decode it that way on the client?
Might it be possible to compile this to wasm and decode it that way on the client?
http://jabberfr.org/tmp/ogv.js/
Note this works fine in desktop and mobile Safari.
It would be nice to finally have a codec again that works with every (modern) platform after such a long time. The split of support for HEVC and VP9 always doubles the effort to distribute content effectively.
[1]: https://www.theverge.com/2018/1/4/16805216/google-chrome-onl...
[2]: https://www.computerworld.com/article/3199425/top-web-browse...
[3]: https://erik.itland.no/chrome-is-the-new-internet-explorer-4...
I could have sworn they used to though. You’d get an app called “Webkit”, but it functioned just like Safari for all intents and purposes.
If Netflix or YouTube want AV1 on Apple TV then they'll just implement it in their applications. Netflix has already implemented AV1 as an option in their Android application:
https://netflixtechblog.com/netflix-now-streaming-av1-on-and...
It's still a bit early to get upset about other vendors, when Google's own Pixel line doesn't have hardware decode yet.
It also doesn't support VP9, so don't hold your breath.
> Might it be possible to compile this to wasm and decode it that way on the client?
Maybe, but I doubt the performance would be tolerable.