https://bugs.kde.org/show_bug.cgi?id=456482

--- Comment #9 from Nick Korotysh <tevut...@mail.ru> ---
as I understood from the last comment on GitHub, the problem somewhere in
OpenGL context type which you get from Qt and pass to libmpv, very sad... from
my experience, it looks like Qt even may use OpenGL ES 2.0 (like on mobiles!) 
even on desktop, but I can be wrong... I almost don't have experience with
OpenGL, just "touched" it due to work.

also tried to run Haruna on Wayland - situation the same: any option except
auto seems to use software decoding (very high CPU usage), auto option very
likely uses the same generic GL/shaders implementation (CPU load is pretty low,
but more than twice higher comparing when vaapi is used, GPU load is also
pretty high, about twice more comparing to vaapi). so it is also doesn't work
on Wayland too...

for the sake of experiment, tried already mentioned SMPlayer (Qt, mpv-based)
and Celluloid (GTK3, libmpv-based) on Wayland. so, SMPlayer is unusable on
Wayland - in most cases video plays in separate window or hardware decoding
doesn't work (when I got video in the same window) or just no video at all.
from other side, Celluloid works fine, even with exactly the same options what
was set in X11 environment, and vaapi seems to work correctly (almost no CPU
usage, and GPU usage is comparable to SMPlayer in X11 environment). looks like
GTK has much better support/integration with Linux rather than Qt...

so, as so this bug seems not related to application side (unfortunately Qt may
be the reason of it), feel free to close it.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to