-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libmpv renderer backend #15
Comments
The GLES2 version is now built as default on windows in actions. |
here is my implement of d3d11 api for mpv and example https://gist.github.com/dragonflylee/5b73c0df5db85dba03488d592f1af23a |
Thanks. I don't want to use a patched mpv, and ANGLE works fine. |
But hwaccel didn't work correctly on my Yoga730 (i5-8250u UHD620), and fallback to
|
You don't need to specify gpu-context, it should select |
Currently, both the video and gui are rendering with OpenGL. To add another backend for mpv, we need to add it for imgui too. It means a lot of work to me, so I'm also considering to use the window embeding feature of mpv ( |
They don't have a way to make |
libmpv provides OpenGL renderer API only, but it does not perform best on all platforms:
gpu-next
yet: Support for libplacebo (gpu-next) in the rendering API mpv-player/mpv#10810Upstream feature requests: D3D11, Vulkan
Luckily, we can use translation layer like ANGLE, which may translate OpenGL ES API calls to a faster hardware-supported APIs to improve performance. Also, ANGLE makes ImPlay work on Virtual Machines that doesn't have a OpenGL 3 driver (example: HyperV vm has D3D driver only). The downside is, it may break HDR: mpv-player/mpv#8530
I've implemented OpenGL ES 2.0 support on the latest main branch, and it's now built in actions (tested the windows version).
The text was updated successfully, but these errors were encountered: