I run an extension that allows to automatically request h.264 streams from YouTube even when av1 is also available. Saves a lot of CPU, at the cost of some bandwidth.

▲

cosmic_cheese a day ago | parent | next [-]

It’s funny that this kind of browser extension has recurred over the years. Originally it was to replace the awful CPU hog flash player with an HTML5 h.264 player[1], then it was to sidestep YouTube’s insistence on VP* codecs, and now it’s to sidestep AV1.

[1]: https://web.archive.org/web/20110302145602/http://www.vertic...

▲

ryandrake a day ago | parent [-]

In a beautiful world, there would be a link to each codec to let the user decide, or the browser itself would override the web site's preference and provide such links. It's sad that we keep having to resort to browser extensions to circumvent terrible web site and browser software.

	▲	alex_duf a day ago \| parent [-]
		I guess in a beautiful world we'd have hardware accelerated, patent free codecs. Which is almost what AV1 is, native hardware decoding is slowly slowly progressing

▲

lxgr a day ago | parent | prev | next [-]

Assuming you have hardware support for VP9 as well, setting media.webrtc.codec.video.av1.enabled to false on about:config achieves the same outcome without an extension.

▲

yonatan8070 a day ago | parent | prev [-]

What's the name of the addon?

I recall h264ify but not sure about it

▲

wing-_-nuts a day ago | parent | next [-]

Yep, that's what I use. It took youtube from using 100% cpu, to the point where my little xps13 was thermal throttling, to 50% cpu running 1080p at 2-3x speed.

	▲	yonatan8070 a day ago \| parent [-]
		Out of curiousity, what CPU do you have in that XPS 13?

▲

nine_k a day ago | parent | prev [-]

What I run is https://github.com/alextrv/enhanced-h264ify

I looked now and noticed that I actually reject VP8 and VP9 and accept AV1. I run Linux on a Ryzen 4750U, for the record. It did not have trouble chewing through VP8 / VP9 without skipping frames, but it ran unpleasantly hot.