After deploying to TV, it will load the thumbnails but not actually play any content.

[Jax-Hax]

I know I am connecting, because I can sign in and see all of my available media, but when I play it just sits there loading permanently. That is really everything I have. I have tried checking logs, changing any settings I could find, enabling or disabling hardware acceleration. In some logs, I did find that ffmpeg was saying [q] command recieved, stopping, but that was about it. I installed this a long time ago on a different TV, which still works, but trying to install it again no longer does. Any help would be greatly appreciated, and I will provide more logs if you tell me what to provide!

[dmitrylyzo]

Does it play the same video in browser (on PC)? What TV model? What jellyfin-web was used? Media info of the video that is not playing.

If the video requires transcoding/remuxing, try disabling Prefer fMP4-HLS Media Container (if it is enabled). This gives me endless loading on my Tizen 4 - it looks like the TV is trying to load entire video.

[Jax-Hax]

It does play the same videos on phone, my other tv, and computer. The model is # UN65K5800DFXZA The jellyfin version is 10.8.8 on server and web, I think jellyfin tizen is 0.1.0 according to the logs, but I tried updating to latest version. I'm not sure as I tried multiple different installs, but I am assuming the latest version. I tried the following to install

1. Direct building from scratch
2. Using https://github.com/Georift/install-jellyfin-tizen
3. Using https://github.com/babagreensheep/jellyfin-tizen-docker I tried almost every movie and show in my library, some required transcoding and some direct played, and none of them loaded. I tried disabling that setting and unfortunately it is still loading, I don't think it has anything to do with transcoding as direct play videos still didn't work.

[Jax-Hax]

Here is where I am getting the q command recieved, I can provide the full logs if necessary. title : Traditional BPS : 73 DURATION : 00:53:41.092000000 NUMBER_OF_FRAMES: 891 NUMBER_OF_BYTES : 29558 _STATISTICS_WRITING_APP: mkvmerge v72.0.0 ('Minuano (Six-eight)') 64-bit _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (eac3 (native) -> aac (libfdk_aac)) Press [q] to stop, [?] for help Output #0, hls, to '/config/data/transcodes/c0f07614a167cf0b9da2c41e8265b82c.m3u8': Metadata: encoder : Lavf59.27.100 Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 23.98 tbr, 90k tbn (default) (original) Stream #0:1: Audio: aac, 48000 Hz, 5.1, s16, 640 kb/s (default) (original) Metadata: encoder : Lavc59.37.100 libfdk_aac frame= 1 fps=0.0 q=-1.0 size=N/A time=-00:00:00.02 bitrate=N/A speed=N/A [hls @ 0x55ae5d895540] Opening '/config/data/transcodes/c0f07614a167cf0b9da2c41e8265b82c0.ts' for writing [hls @ 0x55ae5d895540] Opening '/config/data/transcodes/c0f07614a167cf0b9da2c41e8265b82c1.ts' for writing frame= 320 fps=0.0 q=-1.0 size=N/A time=00:00:00.21 bitrate=N/A speed=0.438x [hls @ 0x55ae5d895540] Opening '/config/data/transcodes/c0f07614a167cf0b9da2c41e8265b82c2.ts' for writing frame= 510 fps=509 q=-1.0 size=N/A time=00:00:08.02 bitrate=N/A speed=8.01x

[q] command received. Exiting.

[hls @ 0x55ae5d895540] Opening '/config/data/transcodes/c0f07614a167cf0b9da2c41e8265b82c3.ts' for writing frame= 511 fps=503 q=-1.0 Lsize=N/A time=00:00:08.13 bitrate=N/A speed= 8x video:10656kB audio:1675kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown

[jimbot03]

This post will replace my previous posts in their entirety, for the sake of clutter and accuracy I will be removing my other posts in this thread.

This is an issue that I also ran into where on some clients but not all jellyfin buffers infinitely hopefully what fixed it for me helps anyone else who runs into this

The cause of the issue for me was inconsistent network performance which appears to effect the Tizen Client of Jellyfin more then others for some reason

Essentially if you have a external hyper-v network switch set up it changes some default network settings for your host PC Namely "large send offload v2" this setting gets used regardless of your physical network adaptors capacity for it Network cards that aren't designed to use this have awful sustained network performance causing issues with jellyfin https://superuser.com/questions/1649498/could-you-explain-how-disabling-large-send-offload-v2-fixes-slow-upload-speeds

Solution 1 : Remove hyper-v external virtual switches on Host PC

However if like me you'd rather not do that

Solution 2 : Disable "large send offload v2" on external hyper-v switches

Step 1 : Open network adaptor settings Open file explorer (Windows+E) and right click network on the bottom left then select properties On the top left of the window that pops up (Network and Sharing Center) select Change adaptor settings

Step 2 : Open the Hyper-v Network adaptor advanced settings In network adaptor settings right click the Vethernet adaptor created by hyper-v then select properties On the pop up (Properties) window select configure on the top right On the pop up (Different but also Properties) select the advanced tab at the top

Step 3 : Disable "large send offload v2" This one is simple enough under the advanced tab from the previous step find large send offload version 2 There one for Ipv4 and Ipv6 after clicking them you can disable them on the right Once done click ok

[Jax-Hax]

I don’t have a hyper v network, and also the host pc isn’t the problem I don’t think. I have several clients connected both outside and inside the network, as well as one tizen client. I’ve still been troubleshooting and I can’t seem to figure it out, seems like it is a very rare and odd issue

[woodwen]

It should be that the video needs to be transcoded, but the triggering of transcoding playback failed, because the same video can be played on the mobile phone, and it can also be played on the TV screen (after the screen projection, the transcoding is successfully triggered and the server is directly connected to the TV. Because after screen casting, you can close the mobile client at will)