I'm surprised that no one has commented on this. This is great news! It'll be a couple of years before I build a new desktop, but I'm already looking forward to using an AMD graphics card for the first time in over a decade.
this post was submitted on 02 Dec 2024
92 points (97.9% liked)
Linux
48677 readers
433 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
In not sure what difference it makes. AMD already supports VAAPI for accelerated video encoding/decoding.
The video quality for encoding has always been bad with AMD.
I'm hoping that by using Vulkan we can bypass poor quality encoders in drivers and get standardised accelerated encoders.
From my understanding, it's the hardware that produces bad results. There's no encoding logic in the drivers itself. That's why the encoding is accelerated in the first place.
E.g. if the hardware doesn't support b-frames – which for long it didn't – a new driver won't do jack. This is just about how video data gets into and out of the card, any encoding logic is handled by the hardware.
If the driver is no longer using a dedicated piece of encoding hardware thats shit, but using the Vulkan logic then surely the quality would be essentially guaranteed by it being Vulkan conformant?
The hardware wouldn't support b-frames in this scenario, and wouldn't matter because your just using the standard matrixes to encode the stream and if it didn't work then surely games would also be broken.
Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒
It's about adding API to Vulkan for access to the hardware encoding units that you're complaining about.
Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒
This is how I would read it. But if you have Mesa do it, it's in software, and you might just be using a software coded directly then, it's much easier.
I wrote Mesa but meant ffmpeg. Wishful thinking that they are able to make a generic ffmpeg encoder in Vulkan to allow it to be accelerated in hardware but not relying on bad video driver codecs.
Oh well, back to Intel.
your late to the party
what are the practical advantages/disadvantages of this over vaapi?
Cross-platform, I guess. However, the only platform of commercial interest (and that I know of) that offers Vulkan as the primary, supported API is Android.