Chrome 94 Released With WebGPU For Testing, WebCodecs API Now Official

[Sonadow]

VAAPI is just borked depending on the hardware. none of my older intel laptops work with it. but brave browser works fine.

VAAPI and VDPAU is not worth the effort.

According to LFS, if Mesa is updated, VAAPI and VDPAU and every other library or application that depends on them need to be recompiled as well.

Way too much work for me when all I want to do is just to build the latest Mesa release. So it stays wilfully broken on my system. Considering how an Apollo Lake-era Atom has enough juice to play a 1080p video on software, it's a reasonable tradeoff.

[evasb]

VAAPI works fine on my Firefox and my mpv.

[intelfx]

VAAPI and VDPAU is not worth the effort.

According to LFS, if Mesa is updated, VAAPI and VDPAU and every other library or application that depends on them need to be recompiled as well.

That just can't be true. Can you prove it? I can prove the inverse.

$ pacman -Qi mesa | egrep 'Name|Version|Date'
Name : mesa
Version : 21.2.1-1
Build Date : Fri Aug 20 09:33:11 2021
Install Date : Sat Aug 21 16:29:46 2021

$ pacman -Qi intel-media-driver | egrep 'Name|Version|Date'
Name : intel-media-driver
Version : 21.3.2-1
Build Date : Sat Aug 21 17:37:05 2021
Install Date : Mon Aug 23 22:31:09 2021

$ pacman -Qi libva | egrep 'Name|Version|Date'
Name : libva
Version : 2.12.0-1
Build Date : Fri Jun 18 22:36:34 2021
Install Date : Mon Jun 21 07:10:08 2021

Way too much work for me when all I want to do is just to build the latest Mesa release. So it stays wilfully broken on my system. Considering how an Apollo Lake-era Atom has enough juice to play a 1080p video on software, it's a reasonable tradeoff.

Sorry, not everyone is living tethered to the electrical outlet. Hardware offload is vital for power efficiency.

[Sonadow]

That just can't be true. Can you prove it? I can prove the inverse.

There is nothing to prove. LFS outright says so. https://www.linuxfromscratch.org/blf...vn/x/mesa.html

libva-2.12.0 (to provide VA-API support for some gallium drivers, note that there is a circular dependency. You must build libva first without EGL and GLX support, install this package, and rebuild libva),

Sorry, not everyone is living tethered to the electrical outlet. Hardware offload is vital for power efficiency.

A laptop whose battery cannot even spare that bit of power to supply a 6w processor with enough juice to play a 720p or 1080p video for a few minutes deserves to be thrown to the trashcan.

[intelfx]

There is nothing to prove. LFS outright says so. https://www.linuxfromscratch.org/blf...vn/x/mesa.html

Well, I wanted you to prove the claim itself, not the mere fact that LFS claims something.

libva-2.12.0 (to provide VA-API support for some gallium drivers, note that there is a circular dependency. You must build libva first without EGL and GLX support, install this package, and rebuild libva),

But anyway. You seem to be misreading the manual. It simply says that there is a circular dependency, not that "if Mesa is updated, VAAPI and VDPAU and every other library or application that depends on them need to be recompiled as well".

Circular dependencies do not imply any sort of API/ABI instability.

A laptop whose battery cannot even spare that bit of power to supply a 6w processor with enough juice to play a 720p or 1080p video for a few minutes deserves to be thrown to the trashcan.

[emphasis mine -- intelfx]

And again you project your own usecases onto everyone. Also, not all laptop processors are 6w.

[Sonadow]

Well, I wanted you to prove the claim itself, not the mere fact that LFS claims something.



But anyway. You seem to be misreading the manual. It simply says that there is a circular dependency, not that "if Mesa is updated, VAAPI and VDPAU and every other library or application that depends on them need to be recompiled as well".

Circular dependencies do not imply any sort of API/ABI instability.
.

The fact that libva needs to be rebuilt after a change to Mesa already means that there is no guarantee that libva will continue to call Mesa normally without any breakage or issues. So any library or application that is already built against libva can also no longer guarantee that they won't break when calling the unmodified libva which in turn calls the modified Mesa.

[intelfx]

The fact that libva needs to be rebuilt after a change to Mesa <...>

Where did you find this "fact"? It does not follow from the manual you quoted.

[Sonadow]

Where did you find this "fact"? It does not follow from the manual you quoted.

Isn't it clear?

Most distributions ship libva with EGL and GLX enabled. The manual says that if libva is desired, it must first be built without EGL and GLX support. So a user must first create a libva build without EGL and GLX, overwritting the distrbution-provided libva. This is the first build of libva, to be made against the existing Mesa version.

Next, the updated version of Mesa must be built and installed.

Finally, libva must be built again, this time against the updated Mesa and with EGL and GLX support enabled, to overwrite the first build of libva sans EGL and GLX support. This clearly is a complete rebuild of libva.

And since there is no guarantee that other applications or libraries that are built against the original distribution-provided libva will still work against the rebuilt libva, the only real assurance is to rebuild them against this rebuilt libva. The LFS manual even states this clearly in the libva section: https://www.linuxfromscratch.org/blf...ver.html#libva

If you are reinstalling this package, you will need to remove the older versions of the libraries. These are in the form of libva*.so.1 and any symbolic links pointing to them. In addition, any packages that use these files need to be rebuilt.

This is way too much effort for too little payoff.

[birdie]

Does anyone here have an actual brain? The fact that Firefox has workarounds means there are websites which work properly in Chrome but don't work in Firefox. Oh, god.

[birdie]

You're an absolute prick. And to think, I was thinking to myself "Man, birdie has been posting awesome shit lately."

Loser in life and not a single soul respects you online. Try way harder and never quote me again. Not interested in anything you have to say.

I don't understand the insults, I gave you the correct answer. Yeah, really, stop quoting me as well, thank you very much.

Speaking of "no one respects me online" - maybe it's just you and some rabid open source fans.