Live data from Hacker News

Jellyfin: The Free Software Media System

jellyfin.org

101–110 of 292 posts

Re: Jellyfin: The Free Software Media System

#101

Well this is very timely and relevant. I usually access jellyfin on my network devices like ` http://homecloud:8096 ` but now that I have been exploring adding other services, remembering the ports is getting tedious. I also am trying to be forward thinking about external access in the future. Looks like I could use some combination of Caddy, Nginx Proxy Manager, Tailscale? What's the simplest setup?

I like traefik

Re: Jellyfin: The Free Software Media System

#102
post #76
post #37

Bemused by the number of people complaining about a free and open source project. A quick review of the git history tells me that it’s maintained by a very small group of people who generously work on this in their free time. Luckily jellyfin does accept PRs, so if you think the project needs improvements, then perhaps folks, you can do something about it

It’s an excellent OSS project. One of the few I have donated to. In my experience, the majority of people who complain loudly about Jellyfin are tied up in the Plex ecosystem and cannot fathom leaving it for some reason. I mean, imagine living with ad-supported streaming content being injected into your private instance by default and having to tell your users to opt-out of that. Admittedly, it is hard to leave such…

I tried switching to Jellyfin. But the feature parity between Plex and Jellyfin just isn’t there. This was roughly 6-9 months ago.

I have a 5.1 surround sound setup with Dolby atmos and 4k HDR 10 with Nvidia Shield Pro android TVs as clients. I have Blu-ray rips that play completely fine on Plex, but stutter, have no sound, or downscale to 2.0 sound on JellyFin.

There are some fixes that involve using a JellyFin server and a Kodi media client on Google TV’s. This does enable DTS and Ddd+ sound. While that technically works, it is very involved and feels like many more steps than just using Plex.

If you use a basic 1080p tv with two speakers and lazy encodes of media, Jellyfin probably works great for you. If you have anything a little more complex then you will inevitably see some problems.

This is similar to other open source projects like Ashai. The basic features are easy enough to build, but the more complicated use cases always require more time and effort, and people aren’t always willing to do that complicated extra effort for free.

Re: Jellyfin: The Free Software Media System

#103
Anyone care to share their experiences with some of the less common Jellyfin frontends? Which ones are most in need of contributions?

I've had a decent experience with the Samsung TV (Tizen) client. It's annoying to not have it on the app store yet and to jump through the developer-mode hoops to get it installed, but to be fair it was a one time setup and I've been happy with it since then. Seen some occasional slightly janky menu navigation, but really it's been far better than I expected.

Re: Jellyfin: The Free Software Media System

#104
post #7

Jellyfin is pretty good, and I've been using it in place of Plex for the last few years. However, I feel like there are some underlying limitations that I just can't get past: 1. the UI jank. The thumbnail tiles are slow to load, even on a local network. Searches and filters flicker as you type and take a while to return. Scrolling fast in the web UI gets choppy/laggy. 2. The native app (at least in the case of Apple…

As a jellyfin fan myself, I'd like to address a couple of your points. For 1, 2, 3(?), 4, you appear to be referring to the Apple TV client, which is written in an entirely different language and frameworks, and entirely different authors. (This is due to the excessive limitations on languages put in place by apple in their ecosystem). Jellyfin has dozens of other platforms. In regard to #3, Jellyfin does use file wa…

Thanks for the detailed reply, I’ll look through my configuration and see if I can find where the issues are with the file watching. You’re right, many of them are likely because I have to use Infuse, due to the native Apple TV client being so bad.

When I say there is UI jank and lag, what I mean is that content re-renders and shifts around when you search, results flash in and out with loading animations. the placeholder tiles are clearly visible and I can see the tiles loading in when I scroll. This happens in both the web client and Apple TV. I believe the issue is the API design that’s dictating how clients fetch and load data, some virtualization in the frontend implementation, and a lack of prefetching/caching.

I have a 10 gig network to a very fast NAS setup and a very small media library. the image assets should be able to be cached/streamed/prefetched from the server so that I do not ever see a placeholder tile (maybe if you jump ahead like 1/2 the library, then that makes sense).

Perhaps this is one of those things where people haven’t seen what’s really possible performance-wise from a local server and they’re OK with something that feels like a webpage. But nothing feels like a native app that just has all my content there all the time. It feels like a remote service even though it’s < 1 ms away on a hardwired multigig network. Does that make sense? Do you agree with that?

Re: Jellyfin: The Free Software Media System

#105
post #54

Earlier quoted context omitted.

Every once in a while I knock around the idea of migrating off Plex and onto Jellyfin. For a long time it was that sharing libraries with friends was a pain, but now literally the only thing stopping me is that they don't have a ps5 app, and that's how one of my friends uses my plex server lol. If they get one, it's all over for plex (in my friend group).

Keep in mind that you don't necessarily need to "migrate" all at once. There's nothing wrong with running both Plex and Jellyfin pointed at the same media library, and using whichever one has the better client for a particular platform.

I tried this but using two servers means you lose or fragment all your watch history. If I have to remember where I am in a series myself, I might as well just use VLC.

Re: Jellyfin: The Free Software Media System

#106

Lot's of criticism on here, but I love Jellyfin. I came from Plex a few years ago after their login server had an outage and I was unable to access the media that was on my local computer. Before that I'd been annoyed by them pushing TV shows and since then I've heard about them giving reports on what people have watched. All in all I'm happy. My setup is Jellyfin in a docker container running on a debian machine wit…

I love jellyfin but their web model is just bizarre. Why on earth, when you go to 192.168.whatever:8096 does it ask you what server you want to connect to? Like.. THE ONE SERVING THE PAGE. Just now I decided to connect to Jellyfin over tailscale and it's asking me to add a server; on 100.xxx, which is the jellyfin server which served the UI. And it doesn't seem to want to accept any answer as to what the server URL i…

Just for what it's worth, I've never had that screen pop up on my Jellyfin instance. I'm just using the official OCI image with a pretty boring configuration. Maybe there's something weird going on? I don't think it's expected in the basic use case.

Re: Jellyfin: The Free Software Media System

#107

Well this is very timely and relevant. I usually access jellyfin on my network devices like ` http://homecloud:8096 ` but now that I have been exploring adding other services, remembering the ports is getting tedious. I also am trying to be forward thinking about external access in the future. Looks like I could use some combination of Caddy, Nginx Proxy Manager, Tailscale? What's the simplest setup?

I've been using nginx for more than a decade now, before that I used lighttpd. Both work well for the purpose of reverse proxying services like Jellyfin. I do not use Caddy because I prefer to keep certificate management centralised in its own (Proxmox-managed) container. I have about 50 services running in Proxmox-managed containers (some containers run more than a single service, others are service-specific) proxied through a single nginx instance, the setup is reliable and performs well. Since nginx is widely used there is usually a config file available which can be used to base your own installation on. Here's what it looks like in my case:

    # kijkbuis.example.org

    server {
        listen 80;
        listen [::]:80;
        server_name kijkbuis.example.org;

            include /etc/nginx/snippets/enforcehttps.conf;
        }

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name kijkbuis.example.org;

        ssl_certificate /etc/letsencrypt/live/kijkbuis.example.org/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/kijkbuis.example.org/privkey.pem;

        set $jellyfin 192.168.1.51;
        resolver 192.168.1.1 valid=30;

        add_header X-Frame-Options "SAMEORIGIN";
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Content-Type-Options "nosniff";

        # the google-related domains are there to enable chromecast support
        add_header Content-Security-Policy "default-src https: data: blob: http://image.tmdb.org; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://www.gstatic.com/cv/js/sender/v1/cast_sender.js https://www.gstatic.com/eureka/clank/108/cast_sender.js https://www.gstatic.com/eureka/clank/107/cast_sender.js https://www.gstatic.com/eureka/clank/cast_sender.js https://www.youtube.com blob:; worker-src 'self' blob:; connect-src 'self'; object-src 'none'; frame-ancestors 'self'";

        location = / {
                return 302 https://$host/web/;
        }

        location / {
                # Proxy main Jellyfin traffic
                proxy_pass http://$jellyfin:8096;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-Protocol $scheme;
                proxy_set_header X-Forwarded-Host $http_host;

                # Disable buffering when the nginx proxy gets very resource heavy upon streaming
                proxy_buffering off;
        }

        # location block for /web - This is purely for aesthetics so /web/#!/ works instead of having to go to /web/index.html/#!/
        location = /web/ {
                # Proxy main Jellyfin traffic
                proxy_pass http://$jellyfin:8096/web/index.html;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-Protocol $scheme;
                proxy_set_header X-Forwarded-Host $http_host;
        }

        location /socket {
                # Proxy Jellyfin Websockets traffic
                proxy_pass http://$jellyfin:8096;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-Protocol $scheme;
                proxy_set_header X-Forwarded-Host $http_host;
        }
    }

Re: Jellyfin: The Free Software Media System

#108
I've been happily using Jellyfin since it forked from Emby a few years ago, and whilst initially it was a bit lumpy (but so was Emby) it's been almost maintenance free for the past three-odd years.

I use it in a docker container, if that makes any difference, and my use case is almost identical to loughnane's mentioned up-thread.

Re: Jellyfin: The Free Software Media System

#109
post #27
post #7

Jellyfin is pretty good, and I've been using it in place of Plex for the last few years. However, I feel like there are some underlying limitations that I just can't get past: 1. the UI jank. The thumbnail tiles are slow to load, even on a local network. Searches and filters flicker as you type and take a while to return. Scrolling fast in the web UI gets choppy/laggy. 2. The native app (at least in the case of Apple…

I have a very different experience from most of your issues, to the point where I think something is wrong with your install. I can scroll through a page of >1000 movie cards and there's no choppiness or lag at all in the webUI. The cards have blurhash placeholders until the actual thumbnail loads, which is always very quick. Swiftfin for the Apple TV is admittedly very barebones and can be choppy when scrolling thro…

Having placeholders is part of what I’m talking about when I say lag, and jank is about dropping frames so that things do not appear smoothly animated. Not everyone is as sensitive to jank or they’re ok with it, but if you use something that lacks jank in the animations it feels better even if you don’t know what jank is.

The media detection thing might be related to Infuse and not to Jellyfin itself, since it sounds like everyone else isn’t having this issue, which is good to know.

Re: Jellyfin: The Free Software Media System

#110

Jellyfin's strategy for streaming blu-ray disc folders is to use ffmpeg to concatenate (and usually transcode) them to disc, then stream the result. It doesn't work very well - frequently, the concatenation process is sitting there running long after the client has disconnected. And the devs seem to break it entirely every second release or so, just failing to recognize the BDMV as a playable movie at all.

I'm glad they're at least trying to support disc folders, though. Plex just doesn't.
Post reply on HN