On Sun, 23 Apr 2023 12:49:19 +0200 Alf <alf.debian...@gmx.de> wrote:
Hi Nicholas

But that's also not true - it now works as before after switching the settings 
under
"General" -> "Video" -> "Output driver"
from "vaapi" to "libmpv" - that's all!

I only use smplayer because of the comfortable way to zap between different 
channels.

So with using "libmpv" I have definitely higher CPU-load (~12%) compared to mpv 
using
vaapi (~1-2%)., but that's no issue for me.


First of all many thanks for the hint to look for SMPlayer settings which led 
to get
it working by changing "Output driver".

Further investigating the configuration also led to a solution for the higher 
CPU load:

SMPlayer seems not to evaluate my $HOME/.config/mpv/mpv.conf where I have 
hardware accelleration enabled.
I now have set it additionally in SMPlayers configuration under

Setting-> Advanced -> Mplayer/mpv -> Options

--hwdec=vaapi

(Attention: different to mpv.conf the option needs to be prefixed with 2 dashes)

This way CPU load in SMPlayer drops down to only 1-2% - precisely as in MPV 
native.
Also logs of smplayer are similar to mpv native:
  AO: [pipewire] 48000Hz stereo 2ch floatp
  VO: [gpu] 1280x720 vaapi[nv12]
  INFO_VIDEO_DSIZE=1280x720
  MPV_VERSION=mpv 0.35.1

You can monitor GPU usage with the tool "intel-gpu-top" from the Debian-repo.
Watch the ENGINE "Video". Any output !0 indicates hardware decoding.

Also my first setting for "Video" -> "Output driver" may be changed back to 
"Default".
That gives the same result, also other selections work, i.e. "gpu" but not all 
enable
HW-decoding. Just "vaapi" throws errors.

Sorry for using this bug report to describe configuration hints for SMPlayer,
but such informnation is hardly available in the web.

Thanks,
Alf

Reply via email to