Vulkan video extensions for accelerated H.264 and H.265 encode
1–10 of 110 posts
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#2> In addition, given the high industry demand for AV1 codec support, an AV1 decode extension release is imminent, with an AV1 encode extension development also underway.
That's good.
By the way, mpv already supports Vulkan video decoding:
https://github.com/mpv-player/mpv/issues/11739
Now we need OBS and Firefox supporting Vulkan video too.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#3> In addition, given the high industry demand for AV1 codec support, an AV1 decode extension release is imminent, with an AV1 encode extension development also underway. That's good. By the way, mpv already supports Vulkan video decoding: https://github.com/mpv-player/mpv/issues/11739 Now we need OBS and Firefox supporting Vulkan video too.
On Windows/Mac Firefox uses the system hardware video decoding APIs - DXVA and Video Toolbox.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#4> In addition, given the high industry demand for AV1 codec support, an AV1 decode extension release is imminent, with an AV1 encode extension development also underway. That's good. By the way, mpv already supports Vulkan video decoding: https://github.com/mpv-player/mpv/issues/11739 Now we need OBS and Firefox supporting Vulkan video too.
On Windows/Mac Firefox uses the system hardware video decoding APIs - DXVA and Video Toolbox.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it).
On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#5[deleted]
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#6Earlier quoted context omitted.
On Windows/Mac Firefox uses the system hardware video decoding APIs - DXVA and Video Toolbox.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it). On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Why would it be a better option than VAAPI?
Decoding h264/h265 in fixed (CPU) hardware is much more efficient than on the GPU.
Don’t get me wrong, its still miles and miles better than software decode.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#7Earlier quoted context omitted.
On Windows/Mac Firefox uses the system hardware video decoding APIs - DXVA and Video Toolbox.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it). On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Beware on Windows, out-of-the-box Microsoft will ship e.g. nvidia drivers that have DirectX 12, but not Vulkan. This can lead to confusing user situations ('DirectX 12 games work fine.. but not Vulkan') and probably means DXVA would be a better choice if targeting Windows
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#8Earlier quoted context omitted.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it). On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Why would it be a better option than VAAPI? Decoding h264/h265 in fixed (CPU) hardware is much more efficient than on the GPU. Don’t get me wrong, its still miles and miles better than software decode.
Do CPUs have fixed video decoders? I thought those were only included in GPUs, including iGPUs.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#9Earlier quoted context omitted.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it). On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Why would it be a better option than VAAPI? Decoding h264/h265 in fixed (CPU) hardware is much more efficient than on the GPU. Don’t get me wrong, its still miles and miles better than software decode.
VAAPI is also using the GPU. The fixed-function video decoders are on the GPUs, not the CPU. That just happens to be using the iGPU on Intel so you don't need a discreet GPU necessarily, but this is also missing if you have a CPU-only sku like the -f suffix parts
The only difference is the vulkan spec is _in theory_ cross-platform. However, since MacOS doesn't support Vulkan and MoltenVK doesn't implement this extension (and probably won't), and this extension also isn't implemented on Android, then your scope of actual availability is quite pathetic. So it probably doesn't make sense to move off of VAAPI regardless unless you really want Linux & Windows to share a codepath, even though you have something OS-specific anyways for MacOS/iOS & Android.
Re: Vulkan video extensions for accelerated H.264 and H.265 encode
#10Earlier quoted context omitted.
On Windows Vulkan video would work. But not on macOS (that mpv thread mentions it). On Linux it should be a better option than VAAPI once drivers will support it. Since Firefox is using ffmpeg anyway, it probably shouldn't be too hard to make it an option.
Why would it be a better option than VAAPI? Decoding h264/h265 in fixed (CPU) hardware is much more efficient than on the GPU. Don’t get me wrong, its still miles and miles better than software decode.
[deleted]