4K Bluray Remuxes buffer on shield 2019 pro

[reaming830]

Hello all,

I recently ported over my previous server, which ran jellyfin on bare metal, to using proxmox, which I now host jellyfin in a VM, and is running via docker, and I configured it to use CIFS to serve the files.

Well, everything works great, but I can't for the life of me to get 4K remuxes to stream. Within seconds, it starts stuttering/constantly buffering. I can confirm it is direct playing, and NOT transcoding, or at least the web UI tells me it's direct playing, and am hard wired (in fact, I have no wifi at my apartment, everything is hard wired), and am using the same ethernet cables as I had been before when everything worked.

Things I have tried to get this working:

• I have tried removing the audio tracks from files
  
• I enabled HDMI-CEC audio
  
• I have replaced the hdmi cord that goes into the receiver, and the receiver that outputs to the tv
  
• I have tried BOTH vimu player and the default player
  
• I have tried BOTH using my nfs and smb shares
  

I have also confirmed that other 4K files, such as a TV show, play fine without buffering. The same files, when I use my shield to go directly to both the NFS and SMB shares with KODI it can actually play the files without buffering or lag. This happens on every 4K film I have - which I am personally using MakeMKV to produce.

my log edit: removed some sensitive info

Here is my log specifically from today. I did notice that I am getting a lot of Invalid token responses, but don't know what that could be from (I suspect jellyseer), but I think it's irrelevant. I don't think this log reflects it because I think I did it yesterday, but one time I just left it playing and let it sttuter for minutes, and I had been keeping my eye on the admin dashboard on my computer, and the timestamp was ticking up on the web ui, but on the shield it said the timestamp was only at 39 seconds.

McCabe and Mrs. Miller seems to be my go to test here, so I'll post the media info on that one.


Any help is appreciated. It's driving me absolutely nuts. I'm going to keep trying/attempting to fix in the mean time. I can provide more information if needed as well. Thanks!

[TheDreadPirate]

Can you share the docker config for the Jellyfin container?

[reaming830]

Sure - I've tried two - the official one:

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    user: 1001:1001
    network_mode: 'host'
    volumes:
      - /configs/jellyfin:/config
      - /cache/jellyfin:/cache
      - type: bind
        source: /mnt/drive/media
        target: /media
    restart: 'unless-stopped'
    environment:
      - JELLYFIN_PublishedServerUrl=MYDOMAINWENTHERE

Redacted my domain, of course. This is the first one I had set up.

I have also tried this one

Code:

services:
  jellyfin:
    restart: always
    container_name: jellyfin
    image: ghcr.io/hotio/jellyfin
    ports:
      - "8096:8096"
    environment:
      - PGID=1001
      - PUID=1001
      - UMASK=002
      - TZ=Etc/UTC
    volumes:
      - /configs/jellyfin:/config
      - /mnt/drive/media:/data

Regardless of the image, I have the same issue.

[TheDreadPirate]

Try repackaging the file.

Code:

/usr/lib/jellyfin-ffmpeg/ffmpeg -fflags +genpts+igndts -i "/data/owned_movies/McCabe And Mrs. Miller (1971)/McCabe and Mrs. Miller (1971) [4K].mkv" -map 0 -codec copy newFile.mkv

[reaming830]

Can you share the docker config for the Jellyfin container?

Try repackaging the file.

Code:

/usr/lib/jellyfin-ffmpeg/ffmpeg -fflags +genpts+igndts -i "/data/owned_movies/McCabe And Mrs. Miller (1971)/McCabe and Mrs. Miller (1971) [4K].mkv" -map 0 -codec copy newFile.mkv

Unfortunately no luck repackaging McCabe with that. I also tried repacking a smaller remux with no dice either.

[TheDreadPirate]

Does the smaller remux also have a huge bit rate? I'm wondering if the bit rate is too high for the shield's decoder.

[Bond_009]

Did you try switching to the second audio track? PCM_S24LE support is new in Android TV 0.17 and maybe the shield doesn't play nice with it?

[reaming830]

Does the smaller remux also have a huge bit rate?  I'm wondering if the bit rate is too high for the shield's decoder.

So I guess the weird thing some of the files were playing ok before I went to the vm. And playing the file from KODI when connected with the SMB plays flawlessly (also - I had also tried the jellyfin plugin and connecting to the jellyfin server, it will stutter too), so it's just leaving me scratching my head.




Here are a couple other lower sized files/bitrates.

Did you try switching to the second audio track? PCM_S24LE support is new in Android TV 0.17 and maybe the shield doesn't play nice with it?

So, I just tried it and it didn't help. It buffered for a little bit and played smoothly for a few seconds after switching but went back to stuttering. I had also tried yesterday removing the audio tracks completely.



Oh, and speaking of the VM, don't know if this says anything or relevant but I bumped it to 3 cores, 6gb memory from 2 cores/4gb


The big cpu spike was me restarting, the second was playing Kwai, then the second spike was playing McCabe (which are two spikes with network/memory).

[reaming830]

I made a discovery - out of curiosity I connected to the server through it's local ip and not through my domain name (which is set up as a subdomain via nginx proxy manager), and the movies play without buffering. I am trying to figure out what settings might be bottlenecking it and what I can change, but hey, found the issue there.

For clarity - my settings are basically just 'block common exploits' and websockets support, and am forcing ssl. I'll try to do some research into whats going on, but am obviously also open to suggestions as well!

edit:
real quick edit here, but I applied all the settings in the jellyfin docs for NPM and it still is buffering, still doing some research, but just wanted to mention my settings now match what is in the docs.

[TheDreadPirate]

Does your router support NAT Loopback/hairpin? It sounds like your traffic is going out to the Internet and coming back in. If you enable NAT loopback on your router it will keep traffic local when your hostname resolves to a local PC.