Glad to see it will support mkv with AV1 codec. That should be the current standard.
WebM is just MKV with a different file extension and a mandated set of codecs and officially only supporting a subset of Matroska features. I have used MKVToolNix in the past and renamed the extension and it worked in browsers.
WebM and MKV are container formats.
AV1 is the codec, and can be contained within either WebM or MKV.
WebM and MKV are container formats.
No, WebM is a specification that defines a subset of the Matroska container, VP9 or AV1 video codec, and Vorbis or Opus audio codecs.
So its a container, even if its a limited one.
So its a container
No, Matroska is a container.
If you reference webmproject.org, at least reference the correct page: https://www.webmproject.org/about/
WebM defines the file container structure, video and audio formats. WebM files consist of video streams compressed with the VP8 or VP9 video codecs and audio streams compressed with the Vorbis or Opus audio codecs.
The WebM file structure is based on the Matroska container.
WebM is a digital multimedia container file format promoted by the open-source WebM Project. It comprises a subset of the Matroska multimedia container format.
It comprises a subset of the Matroska multimedia container format.
I wrote from the beginning that WebM includes a specification of a subset of Matroska it uses but that the WebM specifications also include which audio and video formats it uses. https://www.webmproject.org/about/ 100% confirms what I wrote.
You should just accept it and move on. I’m certainly moving on because discussing with someone over WebM who doesn’t even accept the contents of https://www.webmproject.org/about/ is pointless.
If only they could get jxl support…
Could be coming at some point: https://npo.nl/start/serie/nos-journaal/seizoen-25_4/nos-journaal_100709/afspelen
??? what is this link lol
Initially the copy-paste went wrong and I pasted a different link that happened to be on my clipboard, but I believe I updated it it straight after - so not sure why you still saw the other one (I assume). Maybe Fedia doesn’t understand edits? But wait, this is an edit - can you see this?
Here’s the link I meant to post again though: https://github.com/mozilla/standards-positions/pull/1064
Maybe Fedia doesn’t understand edits?
It normally can (and yes I can see the entirety of this comment), maybe there was some kind of federation hiccup - new link makes a lot more sense haha
Hahaha excellent :)
You might know uwu-speak, well this is Dutch
Appreciate the reminder to study Dutch today! Haha
Whyyyyyy
Yeah, I’ve been keeping an eye out on this: https://github.com/libjxl/jxl-rs
Isn’t it a toggle in the about:config settings?
I want FF support for HEVC, which is way more prevalent than MKV on web…
Yes, I know their position is it’s a licensing issue. I don’t care.
Firefox enables HEVC on:
- Windows from Firefox 134 using either hardware (on devices that support it, where the range is the same as Edge) or software (on Windows the user must pay for and install an extension)
- macOS from Firefox 136 using either hardware or software.
- Linux from Firefox 137 using either hardware or software (via the system ffmpeg).
- Android from Firefox 137 using hardware only.
Is this what you talking about?
Huh, I didn’t realize they finally snuck that in. I’ve been using Edge as a workaround for a long time. Thanks!
I remember wanting that a couple years ago, and finding out then that people had been pointing it out as a much wanted feature that was missing and yet easy to implement for years before that.
I love his phone reviews
