FFmpeg Squaring Away Vulkan Support For Its Next Release

[tildearrow]

This is IT, where do you work that you get sleep?

This is a voluntary work I am doing...

[shmerl]

Time for DE compositors to start using Vulkan instead of OpenGL.

[mppix]

Time for DE compositors to start using Vulkan instead of OpenGL.

Wayland over Vulkan

[DanL]

In the 5th year since the initial spec release why do mainstream desktop distros like Ubunutu still ship without vulkan enabled out of the box? Why do they require users to install it separately?

Because it's not necessary for a Live environment.

[bug77]

In the 5th year since the initial spec release why do mainstream desktop distros like Ubunutu still ship without vulkan enabled out of the box?
Why do they require users to install it seperately? It should be considered standard functionality.

Vulkan is not needed for a desktop environment. Vulkan is about fine grained control over the GPU resources and low overhead, neither of which is critical for a DE. DEs will embrace Vulkan once their underlying toolkits do, though.

For that matter, I'm wondering what Vulkan will do for LibreOffice. Or ffmpeg.

[R41N3R]

Wayland over Vulkan

Yes, short term Wayland should be priority. But long term it would be fantastic to see a competitor like kwin switching to Vulkan.

[kbios]

Wayland over Vulkan

Actually a vulkan compositor would avoid the gbm vs eglstreams problem so it would be in a good position for wayland

[bug77]

Actually a vulkan compositor would avoid the gbm vs eglstreams problem so it would be in a good position for wayland

GBM vs EGLStreams is not what's keeping users away from Wayland. That seems to be the inability to reach feature parity with X

Actually, GBM or EGLStreams is not even under Wayland's control. Wayland, being a protocol, does not require either solution. That is just an implementation choice. It's true that Weston uses GBM only, but that was just the reference compositor. Other compositors are free to use whatever they like (e.g. Mutter has been using both solutions for some time now).

[mppix]

Yes, short term Wayland should be priority. But long term it would be fantastic to see a competitor like kwin switching to Vulkan.

A window manager (kwin) still needs a protocol (Wayland) to use Vulkan..

[mppix]

GBM vs EGLStreams is not what's keeping users away from Wayland. That seems to be the inability to reach feature parity with X

Actually, GBM or EGLStreams is not even under Wayland's control. Wayland, being a protocol, does not require either solution. That is just an implementation choice. It's true that Weston uses GBM only, but that was just the reference compositor. Other compositors are free to use whatever they like (e.g. Mutter has been using both solutions for some time now).

We are abandoning X *because* of its feature set.
Yep, it would be good to see a Vulkan backend happen but that will likely take some time.