The jellyfin-tizen app freezes when decoder limitations are violated

[Keylost]

I tried to play a file with the following video parameters: H264 (High) (level 5.1), 1280x720, 23.98 fps. When pressing the "Play" button in the app, the video poster opens in full-screen mode and then freezes in that state. The poster cannot be closed without force-closing the app, video playback does not start, and the playback control buttons become unresponsive.

The browserDeviceProfile.js only considers the maximum resolution and maximum level for H264, but it does not account for combinations of these parameters. As a result, the video formally matches the DirectPlay profile. However, Samsung TVs seem to impose strict codec level restrictions depending on the resolution (see: Samsung 2024 TV Video Specifications).
Therefore, for example, H264 HD level 5.1 video cannot be played on the device, since for resolutions below FHD the maximum supported H264 level is 4.2, while level 5.1 is only allowed for UHD resolution.. For this video, Jellyfin selects DirectPlay, and no errors appear in either the server or client logs. The app simply freezes after displaying the poster and remains in that state until it is force-closed.

Server and client version: v10.10.7.

[Keylost]

Perhaps I'm mistaken and the issue is not related to the combination of resolution and codec level. Another file with the same resolution and level, which I generated using FFmpeg, works fine. Here's a short video file (10 seconds, 4.5 MB) to reproduce the issue. TV model: QE75QN800A. Tizen version: 6.0.

sample2.zip

[Keylost]

Updated to version 10.11.1. Still not working. When I try to play this file, the dashboard shows in the device info: "Direct playing. The source file is entirely compatible with this client and the session is receiving the file without modifications." However, the TV only displays a single frame and playback doesn’t start. In the web browser on my PC, Jellyfin plays this file without any issues.

[Keylost]

I tried playing this video file through the web browser on the TV (tizenbrowser) instead of the jellyfin-tizen client, and in this case, playback started correctly. The dashboard in this case shows the following client information:

Transcoding
The media is being converted into a format that is compatible with the device that is playing the media.
Framerate: 185fps
6.1 Mbps TS H264 AAC
Reason for transcoding
There was an error starting direct playback.

It seems that for some reason, when using the jellyfin-tizen client, Jellyfin doesn’t detect the problem and doesn’t switch to transcoding.

[meetURBI]

Can confirm this issue with Jellyfin app from tizen store. When hitting play button Jellyfin loads into backdrop and then seemingly freezes until the app is force closed, on tizenbrowser it starts correctly.

[meetURBI]

Seems to be related to transcode probably as each movie / show that I played and had direct streaming worked, the ones that had to be transcoded either froze the app or one even completely crashed the whole TV.

[aleksilassila]

I've had the same freezing happen randomly with some files direct played. Switching to transcoding would fix it. Also what's weird is that the app would freeze in seemingly random places after playing for couple of minutes.

[Wacheee]

I'm having the same problem on my samsung TV (QN90B - 2022 model). The only workaround is to lower the global video quality to 4-2 mbps, After that, video plays correctly