Transcoding issues and hardware acceleration

[glassy]

The third digit is a minor version.  Bug fixes and security patches only, usually.  Each 10.# version is a fairly major version change for Jellyfin with new features, API changes, and dependency upgrades.  For example, going from 10.9 to 10.10 comes with a major ffmpeg upgrade from 6.1 to 7.0.2.  There were 4 additional 10.9.X releases (10.9.11) and we are up to 10.10.6.

But the log you shared doesn't appear to match your screenshot.  In your screenshot you checked HEVC 10-bit decoding (you should also have HEVC checked) but the ffmpeg log doesn't indicate that it is hardware decoding this video.  Nor does it show you have tone mapping checked (NOT VPP tone mapping).

Hey, thanks, upgrading my jellyfin image to 10.10.6 seem to have done the trick! Only thing is now every time I switch a view (i.e. going from /dashboard to /dashboard/settings) I have to do a hard refresh. I can see in the logs that my token is invalid each time

Code:

jellyfin2  | [22:23:11] [INF] [22] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
jellyfin2  | [22:23:11] [INF] [22] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.

I doubt this is related to the transcoding I've issues but is it possible it is a known issue with this version?