caniuse VS Av1an

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme.

https://caniuse.com/?search=css3

For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com

If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?

It’s a glorified feature matrix, and usually a project of a passionate community. I approve, even if some of the memes are a bit dank.

https://caniuse.com/ is a popular tool to check what web features are working across different browsers - "can you use this and assume that it will work for others".

The article uses custom css @properties which are awesome and have 88% browser support [1].

One thing to watch out for is differences in how browsers handle setting the fallback initial-value. Chrome will use initial-value if CSS variable is undefined OR set to an invalid value. Firefox will only use initial-value if the variable is undefined. For most projects, this won't be an issue, but for a recent project, I ended up needing to use javascript to set default values in Firefox to iron out the inconsistency between browser implementations.

[1] https://caniuse.com/?search=%40property

Safari is the only browser that doesn't support extending HTML element

https://caniuse.com/?search=Custom%20Elements

You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed!

https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

https://caniuse.com/?search=webworkers

Do you happen to know where can I check out the cutoff version for each browser? https://caniuse.com/?search=wasm doesn't have it (or other things like WasmGC for that matter)

(https://caniuse.com/) A handy tool for checking the browser compatibility of HTML, CSS, and JavaScript features. Can I Use provides up-to-date support tables for various web technologies across different browsers.

Caniuse

The hardware encoders are very fast and generally better than x264 (but not by as much as you'd think with the x264 slow preset).

In addition, there are threaded AV1 encoders you may be overlooking, like SVT-AV1. For non-realtime, my favorite is av1an, which also yields better quality than is possible from aomenc: https://github.com/master-of-zen/Av1an

I specifically used https://github.com/master-of-zen/Av1an with --target-quality 100 to keep the compression as close to lossless as possible (you could probably shave even more size off if you didn’t use near-lossless compression)

There's also Av1an as suggested by someone else. It's going to produce more efficient encodes because it uses chunk-based encoding to reach the required VMAF for every single chunk, but this is also slower because every chunk will be re-encoded until the VMAF target is reached. It's also a PITA to compile, has a long list of bugs, and isn't very actively developed. One of the long-standing issues is that frames have a tendency to go missing during splitting, which IME is going to keep happening when the input files aren't standardized. And thus the recommendation is to transcode the input to lossless first, which is just completely unsustainable.

i'm still trying to figure out if av1an is the breakthrough to using large CPU counts without losing quality. but it's a ridiculously poorly documented program. i haven't gotten it to run effectively yet. https://github.com/master-of-zen/Av1an

I don't know about VVC, but I've never seen a recommendation of preset 0 for SVT-AV1. The docs say "presets 1-3 represent extremely high efficiency, for use when encode time is not important and quality/size of the resulting video file is critical". It seems like 0 is the equivalent placebo preset. But if you want AV1 with coding efficiency over all else, IIRC the typical approach is to use av1an to detect scene transitions and farm out parallel encodes with aomenc.

That might be because it doesn't work.

Have you seen Av1an? It's supposed to encode to a target VMAF.

Are you using the current version, 0.4.0, from https://github.com/master-of-zen/Av1an/releases