ogv.js

You might find this helpful: https://github.com/brion/ogv.js From the FF announcement linked elsewhere in these comments.

Yeah, that's what Wikipedia do using this https://github.com/brion/ogv.js/

>Today, there is a Python package for everything. The same could be said about CPAN and NPM. Yet Perl is basically dead and JavaScript isn't used for any machine learning tasks as far as I'm aware. WebAssembly did help bring a niche array of audio and video codecs to the ecosystem[1][2], something I'm yet to see from Python. I don't use Python, but with what little exposure I've had to it at work, its overall sluggish performance and need to set up a dozen virtualenvs -- only to dockerize everything in cursed ways when deploying -- makes me wonder how or why people bother with it at all beyond some 5-line script. Then again, Perl used to be THE glue language in the past and mod_perl was as big as FastAPI, and Perl users would also point out how CPAN was unparalleled in breadth and depth. I wonder if Python will follow a similar fate as Pe

I've been told this at least three times now on HN over the years (pretty soon I'm going to start keeping a list of URLs so people know I'm not exaggerating.) Every single time it turns out that it isn't actually true. It was added to desktop Safari. iOS Safari supports VP9 only in WebRTC. It may have changed, but I can't find any evidence that it has. If you see it working somewhere, it is almost definitely using the polyfill[1]. [1]: https://github.com/brion/ogv.js/

I believe Wikipedia has resorted to polyfilling it using this: https://github.com/brion/ogv.js That's great and all, but it has limitations, and obviously, is ludicrously less efficient than it should be.

This is great and overdue. Hopefully all major browsers will add some support for open source/royalty free codecs. Emscripten/WebAssembly actually worked rather well with audio (OPUS is just awesome) but when it comes to video it's just unfeasible, especially if you are looking at doing low latency streaming. That said, I cannot fail to mention the incredible effort done by ogv.js [1] to make a/v decoding possible almost anywhere. Looking forward to experiment with this new API. [1] https://github.com/brion/ogv.js/

You can use this in Safari https://github.com/ai/audio-recorder-polyfill https://github.com/GoogleChromeLabs/webm-wasm Safari doesn't play webm files two options for that 1). you can convert webm to MP4 with or without re-encoding(will be faster) using ffmpeg or ffmpeg-wasm (within browser) https://github.com/ffmpegwasm/ffmpeg.wasm 2). Another option is play webm directly using wasm https://github.com/brion/ogv.js

You can support a variety of formats in Safari using WebAssembly builds of the decoders. WebAssembly for audio and image formats is more than fast enough. It's even fast enough for VP9 video. WebP demo: https://webmproject.github.io/libwebp-demo/webp_wasm/index.h... Theora\VP8\VP9\Opus\Vorbis demo: https://brionv.com/misc/ogv.js/demo/ ogv.js on GitHub: https://github.com/brion/ogv.js

ogv.js does Theora, VP8, VP9, and AV1 video and Opus and Vorbis audio: https://github.com/brion/ogv.js https://brionv.com/log/ A demo which lets you select various codecs to try out. You can, for example, play 720p VP9 video in Safari with the WebAssembly build of the decoder: https://brionv.com/misc/ogv.js/demo/

> Can my web browser play FLAC or Opus out of the box? Flac isn't really for browser playback, but for lossless backup. Normal browsers should play Opus fine today. Some crippled ones might not, but for that there are projects like this as fallback: https://github.com/brion/ogv.js/ So I see no reason not to use Flac and Opus for music services.

We've already implemented this as part of a web-based AV1 analyzer tool. You provide the URL to both the image and the decoder, which is very convenient because the decoder is constantly changing [1]. Wikipedia also does this to enable video playback on Edge and Safari [2]. The idea to do this within the format itself is quite old. The very early versions of what became Vorbis had a very similar concept, with programmable passes. Matroska once had a field for a link to download the VfW decoder dll (the horror!). It's never really caught on, due to reasons already listed by sibling comments. [1] https://arewecompressedyet.com/analyzer/?maxFrames=4&decoder... [2] https://github.com/brion/ogv.js/

You may be interested in the following project from the Wikimedia Foundation: https://github.com/brion/ogv.js/

Video decoding in JS is very impressive - really highlights the speed of modern interpreters. I especially love that a Björk track from the 90's is featured. I recently worked on a personal project which had to play back .webm files, and I used a similar utility: https://github.com/brion/ogv.js/ It decodes .webm files and plays them in the web. I believe it's also used by Wikipedia to play bag Ogg files.

This is a little different than codec support, though as other replies indicate, that can be done too. This is just demuxing the stream in one format, re-muxing it in a different format, and feeding it into <video> to actually do the decoding and playback. On the other hand, something like https://github.com/brion/ogv.js/ is actually doing all of the decoding and playback in JavaScript/asm.js, using C libraries compiled with Emscripten. Anyhow, yes, it probably would be possible to package up extensions that would apply one of these automatically to <video> tags with unsupported codecs or container formats. It's just a simple matter of programming.

Yes, in fact it's even deployed on Wikipedia: https://github.com/brion/ogv.js/