7 ms·
Khronos Releases AV1 Decode in Vulkan Video with SDK Support for H.264/H.265
- westurner 3y ago[flagged]
- deleted 3y ago[deleted]
- ekianjo 3y agoAMD not even ready for the Linux support yet? that's disappointing.
- jauntywundrkind 3y agoNot 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 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.
- shmerl 3y agoI 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.
- brucethemoose2 3y agoYeah. What even is the of keeping things split? RADV even has big commercial customers now (Valve).
- kimixa 3y agoMany 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.
- shmerl 3y agoI 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.
- aaomidi 3y agoAnd meanwhile Chrome outright refuses to support vaapi outside of intel (and thats only because of chromebooks).
- Vogtinator 3y agoWith the right Mesa patch (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26165 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.
- jauntywundrkind 3y agoSeems 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 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 https://www.phoronix.com/news/Mozilla-Firefox-115
- rasz 3y agoAMD AV1 encoder is really bad, you arent missing much. https://goughlui.com/2023/12/31/video-codec-round-up-2023-part-11-hevc_amf-h-265-amd-advanced-media-framework/ https://goughlui.com/2023/12/31/video-codec-round-up-2023-pa... https://goughlui.com/2024/01/07/video-codec-round-up-2023-part-14-av1_amf-av1-amd-advanced-media-framework/ https://goughlui.com/2024/01/07/video-codec-round-up-2023-pa...
- emersion 3y agohttps://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27424 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27...
- janandonly 3y agoToo bad there is no mentioning of MacOS support.
- ShadowBanThis01 3y ago[dead]
- cm2187 3y agoHow useful are hardware decoders? My understanding is that they are not necessarily faster than software decoders (in my experience it is the opposite), so the only benefit I can see is less CPU consumption. I see the benefit when you run on a battery (laptop / smartphone) but on a desktop or server, unless you critically need the CPU at that time, I am not sure how useful it is.
- fulafel 3y agoYes, real-time decoding on a desktop is just nice-to-have, with a couple of exceptions (1) if your decoder software runs too slow for real-time decoding. I think it historically has happened every once in a while until CPUs and decoder optimizations catch up again. Eg 4k H.265 was too much for many desktops for a while. (2) you do a lot of it, in which low power decoding->saving electricity is still good eg Linux web browsers for ages had sw-only decoding at it worked mostly fine, just laptops having battery eaten in browser apps & electron based apps (videoconferencing). As codecs are historically a top source of remote code execution vulnerabilities that get our device pwned, the poor sandboxability of hw decoders makes them a security problem as well. eg as a pathway to exploit the flaky and high-privileged GPU driver code paths.
- Vogtinator 3y agoThat's exactly what makes them useful. Energy consumption is vastly reduced.
- FirmwareBurner 3y ago>I see the benefit when you run on a battery (laptop / smartphone) but on a desktop or server, unless you critically need the CPU at that time, I am not sure how useful it is. Yes it is. Very useful. The vast majority of people use laptops now, not desktop computers with 120mm tower coolers anymore, and if you want to switch to Linux then not having video decode nuke your battery life and turn your tiny fans into a Pratt & Whitney, then this is another welcome change to closing the gap to Windows. People, especially on the Linux side, need to stop viewing the world as if everyone still has desktop towers PCs tucked under their desks while disregarding the software issues and deficiencies that only plague laptops, which are the majority of the marketshare and have vastly different constrains than desktops.
- cubefox 3y agoDoes this mean they decode AV1 using a compute shader as a fallback for GPUs that don't include an AV1 ASIC?