Posts: 5
Joined: May 2016
Reputation:
0
The remedy for this is supposedly change Settings > Player > Videos > Render Method from Auto Detect to Software but Auto Detect is the only option shown.
Posts: 5
Joined: May 2016
Reputation:
0
Thanks. I didn't realise there was anything below the Render Method line. It was a problem with scrolling on my TV box. I don't have as many entries as you show but I've turned off both entries and now it seems to play without stopping and starting but it is slightly jerky.
Posts: 164
Joined: Nov 2022
Reputation:
27
Neo1973
Team-Kodi Member
Posts: 164
Well, h265 is not trivial to decode in software. Depending on the resolution and bit rate of your video and the capabilities of your hardware stuttering can't be avoided.
Posts: 5
Joined: May 2016
Reputation:
0
Ok. Thanks for your help.
Posts: 3
Joined: Jul 2024
Reputation:
0
Hi,
I have the same problem (Debian bookworm, Kodi 21.1 standalone via backports) but I don't have those menu entries at all.
i.e. In Settings -> Player -> Video I have Hardware Decoding with Autodetect greyed out and no other entries, HD scaling = 20 percent and then nothing else in the Processing section, the next Section is Stereoscopic 3D settings
I have a Pentium J5005 with Intel 605 graphics internal.
I have a feeling I need to install some non-free drivers but Debian won't do that by default of course.
Any ideas?
Posts: 18,161
Joined: Aug 2007
Reputation:
705
Hitcher
Team-Kodi Member
Posts: 18,161
Are you still in 'Standard' settings mode? Check the cog at the bottom left of the screen.
Posts: 3
Joined: Jul 2024
Reputation:
0
hi, thanks for the reply.
Yes it's on Expert.
I also installed intel-gpu-tools and firmware-linux-nonfree in the last 10 min and rebooted but no go.
$ inxi -Gxx
Graphics:
Device-1: Intel GeminiLake [UHD Graphics 605] vendor: Dell driver: i915
v: kernel arch: Gen-9 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3184
Display: server: No display server data found. Headless machine?
tty: 80x24
Monitor-1: HDMI-A-1 model: Sharp LCD res: 1920x1080 dpi: 45
diag: 1256mm (49.5")
API: OpenGL Message: GL data unavailable in console. Try -G --display
$ inxi -Gxx --display
Graphics:
Device-1: Intel GeminiLake [UHD Graphics 605] vendor: Dell driver: i915 v: kernel arch: Gen-9
ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3184
Display: server: No display server data found. Headless machine?
Monitor-1: HDMI-A-1 model: Sharp LCD res: 1920x1080 dpi: 45 diag: 1256mm (49.5")
API: OpenGL Message: No GL data found on this system.
Posts: 3
Joined: Jul 2024
Reputation:
0
Thank you for your help.
I am not sure what is happening. It seems CPU is acceptable now (30-40 percent). I am sorry for wasting your time.
The only thing I did was: I added the user that is executing the Kodi service (my account actually) to some permission groups:
sudo usermod -a -G cdrom,audio,render,video,plugdev,users,dialout,dip,input <user account name>
I can't think of anything else that changed.
Note that your link contadino assumes X11 is installed but I havn't installed X11.
I did create debug logs and it looks like the Intel driver is initialised.
2025-01-16 20:16:07.637 T:10210 info <general>: GL_RENDERER = Mesa Intel® UHD Graphics 605 (GLK 3)
and:
2025-01-16 20:16:07.626 T:10210 debug <general>: Vaapi2 EGL interop test results: general yes, deepColor yes
2025-01-16 20:16:07.627 T:10210 debug <general>: libva info: VA-API version 1.17.0
2025-01-16 20:16:07.627 T:10210 debug <general>: libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-01-16 20:16:07.627 T:10210 debug <general>: libva info: Found init function __vaDriverInit_1_17
2025-01-16 20:16:07.628 T:10210 debug <general>: libva info: va_openDriver() returns 0
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - initialize version 1.17
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - driver in use: Intel iHD driver for Intel® Gen Graphics - 23.1.1 ()
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileMPEG2Simple
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileMPEG2Main
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileH264Main
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileH264High
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileJPEGBaseline
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileH264ConstrainedBaseline
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileVP8Version0_3
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileHEVCMain
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileHEVCMain10
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileVP9Profile0
2025-01-16 20:16:07.628 T:10210 debug <general>: VAAPI - profile VAProfileVP9Profile2
2025-01-16 20:16:07.628 T:10210 info <general>: VAAPI::Close - closing decoder context
Not sure if this has changed. Anyway, it looks much better now.
Thank you again for your suggestions.