Jellyfin Tizen 2.3

[formeo]

Hello,

I've successfully installed Jellyfin on Tizen, and direct play is functioning correctly. However, I'm encountering issues with transcoding. To diagnose, I set the maximum bandwidth to 480p at 720kbps, but the video fails to load, and there are no error logs to indicate what might be wrong.

I'm running Jellyfin version 10.9.8 on Ubuntu via Docker. My TV is using the Jellyfin-web release-10.8.z from GitHub because newer versions are incompatible with my older TV model, which only displays a watch icon and closes the site upon pressing back.

Despite the compatibility with 10.8.z, transcoding is not working. This is a video of my dashboard, the video does not start: https://streamable.com/gijv1z. The TV does only show the background Image of the Video. Here are the logs from a session with transcoding settings and another with direct play:

Transcoding to 480p-720kbps:

[2024-07-25 08:08:54.209 +00:00] [INF] [31] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "***.***.***.***" request
[2024-07-25 08:08:57.741 +00:00] [WRN] [35] Jellyfin.Networking.Manager.NetworkManager: "***.***.***.***": Only loopback "::1" returned, using that as bind address.
[2024-07-25 08:09:02.833 +00:00] [INF] [35] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for "maik". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[2024-07-25 08:09:05.220 +00:00] [INF] [15] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for "maik". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[2024-07-25 08:09:47.082 +00:00] [WRN] [37] Jellyfin.Networking.Manager.NetworkManager: "***.***.***.***": Only loopback "::1" returned, using that as bind address.
[2024-07-25 08:10:23.990 +00:00] [WRN] [30] Jellyfin.Networking.Manager.NetworkManager: "***.***.***.***": Only loopback "::1" returned, using that as bind address.
[2024-07-25 08:10:40.390 +00:00] [WRN] [39] Jellyfin.Networking.Manager.NetworkManager: "***.***.***.***": Only loopback "::1" returned, using that as bind address.
[2024-07-25 08:10:49.001 +00:00] [WRN] [15] Jellyfin.Networking.Manager.NetworkManager: "***.***.***.***": Only loopback "::1" returned, using that as bind address.


Direct Play:

[2024-07-25 08:24:07.463 +00:00] [INF] [35] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for "maik". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[2024-07-25 08:24:36.060 +00:00] [INF] [39] Emby.Server.Implementations.Session.SessionManager: Playback stopped reported by app "Jellyfin for Tizen" "0.1.0" playing "Big Buck Bunny". Stopped at "16003" ms


There are no ffmpeg logs for either scenario, which is unusual since transcoding should generate some logs. Any insights or suggestions would be greatly appreciated.

Thank you!

[TheDreadPirate]

Are you using host networking or bridge networking? Is the TV connecting through a reverse proxy? Or going directly to Jellyfin?

Can you share your docker compose with us?

[formeo]

Yes, I can share the compose file. I no longer run Jellyfin in host mode because it didn't provide any improvements over simply exposing the ports. Everything works except for the Tizen client when I want to downscale (transcode) videos. The web interface, Android app, and Findroid app all function correctly. Host mode would be beneficial if DLNA worked, but it doesn't, even in host mode, so there's no reason for me to use it.

I use Cosmos as a reverse proxy and haven't encountered any issues with it. It works great. I exposed port 8096 to access the TV via the local IP address, so the proxy doesn't affect the TV connection since it's connected directly to the server's local IP.

I'm unsure why the TV client doesn't play videos when I use transcoding. Here's my Docker Compose file for Jellyfin:


services:
  Jellyfin:
    container_name: Jellyfin
    image: lscr.io/linuxserver/jellyfin:latest
    environment:
      - PUID=1000
      - PGID=1000
      - PATH=/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      - HOME=/root
      - LANGUAGE=en_US.UTF-8
      - LANG=en_US.UTF-8
      - TERM=xterm
      - S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
      - S6_VERBOSITY=1
      - S6_STAGE2_HOOK=/docker-mods
      - VIRTUAL_ENV=/lsiopy
      - LSIO_FIRST_PARTY=true
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
    labels:
      build_version: Linuxserver.io version:- 10.9.6ubu2204-ls19 Build-date:- 2024-06-06T19:17:03+00:00
      cosmos-auto-update: "true"
      cosmos-force-network-mode: cosmos-Jellyfin-default
      cosmos-force-network-secured: "false"
      cosmos-icon: https://azukaar.github.io/cosmos-servapp...n/icon.png
      cosmos-stack: Jellyfin
      cosmos-stack-main: Jellyfin
      maintainer: thelamer
      org.opencontainers.image.authors: linuxserver.io
      org.opencontainers.image.created: 2024-06-06T19:17:03+00:00
      org.opencontainers.image.documentation: https://docs.linuxserver.io/images/docker-jellyfin
      org.opencontainers.image.licenses: GPL-3.0-only
      org.opencontainers.image.ref.name: 8b9f24ac5e026b0103a7b34fddb471d2927bbef2
      org.opencontainers.image.revision: 8b9f24ac5e026b0103a7b34fddb471d2927bbef2
      org.opencontainers.image.source: https://github.com/linuxserver/docker-jellyfin
      org.opencontainers.image.title: Jellyfin
      org.opencontainers.image.url: https://github.com/linuxserver/docker-jellyfin/packages
      org.opencontainers.image.vendor: linuxserver.io
      org.opencontainers.image.version: 10.9.6ubu2204-ls19
    ports:
      - "0.0.0.0:8096:8096/tcp"
      - ":::8096:8096/tcp"
    volumes:
      - type: bind
        source: /media/series
        target: /data/tvshows
      - type: bind
        source: /var/lib/docker/volumes/Jellyfin-config/_data/web-config.json
        target: /usr/share/jellyfin/web/config.json
      - type: volume
        source: Jellyfin-config
        target: /config
    networks:
      - cosmos-Jellyfin-default
    restart: unless-stopped
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    expose: []
    depends_on: []
    stdin_open: true
    entrypoint: /init
    working_dir: /
    hostname: b4c1d4e9847c
    network_mode: cosmos-Jellyfin-default
    healthcheck:
      test: null
      interval: 0
      timeout: 0
      retries: 0
      start_period: 0


[TheDreadPirate]

Can you enable debug logging, restart jellyfin, then replicate the problem? Then share the full log via pastebin.

In container path /config/logging.default.json you will modify the lines near the top. Replace "Information" and "Warning" with "Debug".

[formeo]

Yes I can do that tomorrow👍

[formeo]

I changed the logging level to debug, and the resulting log file was quite large. Paste Bin was unable to handle it because nginx indicated that the request was too large. Therefore, I used filetransfer.io to share the full log. I am unsure which specific information might be relevant to the problem, so I have included the entire log.

I attempted transcoding two times with Big Buck Bunny: the first time to 480p at 720kbps (did not work), then I tried direct play, which worked, and then again to 480p at 720kbps, that also did not work. Here is the link to the full log: https://filetransfer.io/data-package/8BDD00Br#link

[TheDreadPirate]

I'm not expert, but it looks like the client isn't requesting the right path for the transcodes. I'm wondering if this ticket is related to your problem.

https://github.com/jellyfin/jellyfin-tizen/issues/279

[formeo]

No, i don't think it's related to my problem, except that if they fix that, it could be that the newer version does not have this issue. I've mentioned that other newer versions beyond 10.8.z do not function properly as of now. I'm currently using 10.8.z, where it works, except for the problem you pointed out regarding the client not requesting the correct path for transcodes.
Do you think there is a solution to this?

[TheDreadPirate]

I'm not sure there is. There were a huge number of changes in 10.9. The fact that jellyfin-web 10.8.13 continued to work until 10.9.8 is baffling.

Going back a bit, why do you say that jellyfin-web 10.9.X is not compatible with your TV? AFAICT, our Tizen builds are still compatible with Tizen 2.3.

[formeo]

As you said, 10.9.x is compatible in theory, but it is not functioning on my two TVs: the UJU6700 and the UJ6200. This issue mirrors the one reported in the GitHub thread (https://github.com/jellyfin/jellyfin-tizen/issues/279). Additionally, I have encountered problems with the web version, which also fails to run, and I added a picture (with bad quality. I can not take a screenshot of the screen.)

I have reported this issues here: (https://github.com/jellyfin/jellyfin-web/issues/5756). Given that I am experiencing the same problem on two different TVs, and only with newer software versions, I suspect that the client may have been compatible with Tizen 2.3 but is no longer supported, despite the lack of updated information on this.

It appears that another (your link) user is facing the identical issue on Tizen 2.3, suggesting that versions above 2.3 are indeed compatible. The 10.8.z version remains functional, except for the transcoding feature, which is acceptable for a decade-old model. However, I had hoped for a resolution to this issue. Currently, it seems that I can play videos on 10.8.z as long as transcoding is not required.

I am hopeful that Tizen 2.3 will be supported again in the future.
Thank you for your help regarding my problem