Hacker News Reader

Comment by ekianjo | Hacker News Reader

AMD not even ready for the Linux support yet? that's disappointing.

Not sure why this release is so slanted, but av1 encode on AMD Linux has been available since October. https://www.phoronix.com/news/Mesa-23.3-HQ-AV1-Radeon

How Nvidia managed to emerge looking good on this PR is a colossal surprise & fucked up-ed-ly inappropriate.

I suppose the above comment was about amdvlk. radv is indeed often ahead of it these days.

If anything, I think AMD should drop amdvlk on Linux (to collaborate on radv there) and instead try to develop radv for Windows if that's doable to replace amdvlk altogether.

Yeah. What even is the of keeping things split?

RADV even has big commercial customers now (Valve).

Many of the people working on RADV are already employed by AMD (or paid by them indirectly), so arguably it's already collaborating.

I see the amdvlk/radv drivers a bit like the windows "Radeon Pro"/"Adrenalin" driver split, one is for people who stare at solidworks all day, the other for everyone else.

I think AMD wanted to phase out that distinction for OpenGL for example, so why wouldn't they want the same for Vulkan There is no need for them to be different really in that sense.

amdvlk and radv exist for historic reasons since they started independently and amdvlk was designed to support Windows too. But today I don't really see a big point in admvlk except where radv doesn't exist.

So AMD can do what Intel does. Support radv on Linux and amdvlk on Windows for example, or as above, try to make radv work on Windows too.

And meanwhile Chrome outright refuses to support vaapi outside of intel (and thats only because of chromebooks).

With the right Mesa patch (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26...) and chromium flags to force enable vaapi, I've got working HW decode with amdgpu here.

Seems like with av1, Google had to stop self-sabotaging (turning on va-api has worked for most users for more than half a decade) & kind of had to move (because av1 is too beastly to do on cpu). Sounds like va-api has been turned on for almost a month now, but I haven't confirmed. https://www.phoronix.com/news/Google-Chrome-Wayland-VA-API

Maybe I'm missing something, but from what I could dig up it sounds like Firefox only enables va-api on Intel. https://www.phoronix.com/news/Mozilla-Firefox-115

AMD AV1 encoder is really bad, you arent missing much.

https://goughlui.com/2023/12/31/video-codec-round-up-2023-pa...

https://goughlui.com/2024/01/07/video-codec-round-up-2023-pa...

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27...

Reply on news.ycombinator.com