2023-12-06, 02:25 PM
(2023-12-06, 09:23 AM)pixel24 Wrote: That surprises me. I installed an nVIDIA Quadro Pro in my server some time ago and set up the hardware acceleration as described in the documentation.
On a Kodi client with the normal Jellyfin plugin, the playback of H265 / 4k media generated a constant CPU load of 100%. The device became very warm. I then asked on github and was told that the normal Jellyfin plugin does not support hardware acceleration or not in conjunction with the Core i3 in my Kodi client. See here:
https://github.com/jellyfin/jellyfin/discussions/9774
I then removed the Jellyfin plugin and installed and set up JellyCon. Apart from that, nothing else was changed and the same movie was played. Now there was no significant CPU load when playing on the client.
This made the statement seem logical to me.
with best
pixel24
you needed to qualify what you meant
to clarify, i was talking about "client side" hardware acceleration being available, which negates the need for "server side" transcoding in turn no need for server side hardware acceleration
if your "client" is not capable of a codec as the github issue suggests then you needed to go into the addon settings for the "jellyfin for kodi" addon and turn on force transcode
in that case, it would use "server side" hardware acceleration
i use jellyfin for kodi with that setting and none of my clients are capable of decoding VC1 so that is the only codec i force transcode
in recap, hardware acceleration in both client and server are available but if you want transcoding done by the server you have to set it in the addon's settings and make sure you are using addon mode for playback and not native, native just opens the file directly without interaction with the server
and i have no idea how jellycon managed to work for you, there *should have been no difference