ogv.js
web-codecs
ogv.js | web-codecs | |
---|---|---|
7 | 15 | |
1,182 | 910 | |
- | 2.1% | |
7.2 | 8.3 | |
3 days ago | 4 days ago | |
JavaScript | HTML | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ogv.js
-
"MP3 is dead" missed the real, much better story (2017)
Yeah, that's what they do using this https://github.com/brion/ogv.js/
- Making Python 100x faster with less than 100 lines of Rust
-
Google and Mozilla are working on iOS browsers that aren't based on WebKit
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/
-
How to stream OGG on iOS?
I found a library "ogv.js" that says it decodes .ogg/.webm using WebAssembly, and this demo plays on my iPhone SE3 in Safari.
-
Anti-innovative effects of Apple's prohibition of alternative browser engines
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.
-
Privacy analysis of FLoC
We already have JS/WebGL video decoders (e.g: Broadway.js, OGOV.js). Much of the earlier video playback/acceleration work was getting it accelerated on GPUs-- using DirectX, OpenGL, or other GPU programming standards.
-
WebCodecs is a flexible web API for encoding and decoding audio and video
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/
web-codecs
-
Replacing WebRTC: real-time latency with WebTransport and WebCodecs
Encoding alpha, please! https://github.com/w3c/webcodecs/issues/672
-
Real-Time Video Processing with WebCodecs and Streams
From developer.mozilla.org [0]
> WebCodecs API
> The WebCodecs API gives web developers low-level access to the individual frames of a video stream and chunks of audio. It is useful for web applications that require full control over the way media is processed. For example, video or audio editors, and video conferencing.
And from w3c [1]:
> The WebCodecs API allows web applications to encode and decode audio and video
All this looks really promising, I wouldn't have thought that we could use browsers directly to render videos. Maybe Puppeteer could then stream the content of the page it is rendering, for example a three.js animation.
[0] https://developer.mozilla.org/en-US/docs/Web/API/WebCodecs_A...
[1] https://github.com/w3c/webcodecs
-
Microsoft Clipchamp
As I understand it, Web Codecs is quite a ways away from being a web standard - it is currently just a draft[1] for a recommendation for a possible future standard.
Just beware of any major API changes or any indication that it might be dropped in its entirety!
[1]:https://w3c.github.io/webcodecs/
-
Chrome 94 Beta: WebCodecs, WebGPU, Scheduling, and More
WebCodecs has Mozilla and Microsoft coauthors: https://w3c.github.io/webcodecs/
WebGPU was chartered in 2017, with more Apple people in the initial membership than Mozilla or Google people: https://gpuweb.github.io/admin/cg-charter.html
Google specifically has approached Apple for input about scheduler.postTask(), and they say they've presented the proposal before at a working group that Apple is part of: https://lists.webkit.org/pipermail/webkit-dev/2021-June/0319...
I won't disagree that there's a ton that can be improved about the process, but it seems pretty unsubstantiated to claim that Google is "rushing forwards as fast as possible" given that they've been spending years working on these APIs in public. You can see from the rest of the post that they're running some experiments which they're specifically choosing not to enable by default, though they could.
-
Show HN: I made a meme creator that makes around $4k a month
I work for PaperlessPost.com, and for our Flyer product we export mp4s from ffmpeg compiled to WASM, which is similar to ffmpeg.js but optimized for our use case which sounds similar. We have this WebAssembly method working well but iOS 15 (and the other major browsers) now support MediaExporter which might be a better way to go if you have something else to convert these files. This becomes and issue because you can't control the format MediaRecorder is recording to but the management of memory, the image quality, the compression, the performance hit will be more ideal than these other methods. OMGgif is very slow and will produce large files or very bad looking ones. Keep in mind that GIFs limit the colors so something that looks nice on the screen might not look the same after it is saved. The other thing to look out for is the WebCodecs APIs which should be the ultimate way to handle all of this in the future but it is only working in Chrome I think https://github.com/w3c/webcodecs
-
Loading Audio in Node JS
While in theory it might be possible to run ffmpeg through emscripten and run it in a web worker (I certainly assume someone has done this), it's not necessarily practical to try and use the same technique from node to transcode audio on the web. The good news is that the w3c has chartered a working group to focus on web codecs. While this is at the time of writing still in early stages, the working group is powering ahead on designing and proposing an API to enable media transcoding on the web, and hopefully that will become available to us in the near future.
- WebCodecs
- What's the deal with the WebCodecs and InsertableStreams APIs?
- WebCodecs is a flexible web API for encoding and decoding audio and video
What are some alternatives?
Broadway - A JavaScript H.264 decoder.
web-bugs - A place to report bugs on websites.