Live data from Hacker News

Jellyfin 12.0

jellyfin.org

281–290 of 358 posts

Re: Jellyfin 12.0

#281
post #18

Upgrade experiences, anyone? I have a ~40TB library and was still on 10.10.7 because of all the performance issues with 10.11. Upgraded straight to 12.0 and was impressed with how quick and painless it was! As the upgrade instructions warn about, some of my titles disappeared until a rescan added them back, but that was the only weirdness. The whole initial migration only took a few minutes.

yep, "just worked". Seems to be much better at properly categorizing some of the more stubborn corners of my library as well. Congrats to Jellyfin maintainers!

Re: Jellyfin 12.0

#283
post #81

Subtitles are the Achilles heel of Jellyfin (at least the Android client sending the stream to Chromecast stick connected to the TV). I can see the subtitle present but it doesn't show on the movie. Ok, I will just add manually - can't, progress indicator loops forever. Ok, I will remove the existing subtitles and add - removal succeeds - addition fails. This is the same fiddling everytime. If it works, it is a mirac…

Do you use bazarr? That’s been the final fix for me with subtitles

I wasn't aware of this - thanks, I will give it a try.

Re: Jellyfin 12.0

#284
post #23

Subtitles are the Achilles heel of Jellyfin (at least the Android client sending the stream to Chromecast stick connected to the TV). I can see the subtitle present but it doesn't show on the movie. Ok, I will just add manually - can't, progress indicator loops forever. Ok, I will remove the existing subtitles and add - removal succeeds - addition fails. This is the same fiddling everytime. If it works, it is a mirac…

Is that an old problem, or a problem that is still in this new v12?

Given v12 just came out and has a bunch of warnings regarding migration, I'm not going to jump on it yet. This is pre-v12 issue.

Re: Jellyfin 12.0

#285

Pity they still haven't finished adding support for proper database backends. SQLite is the source of all my problems with Jellyfin as it buckles under the weight of my library, behaves badly on CoW filesystems, and prevents scaling my instance to multiple nodes.

I don't even have a huge library but it performs terribly on my system due to SQLite. Would love a Postgres backend.

Huh, I always thought one of the main advantages of SQLite was supposed to be the performance. (e.g. it's one of the things they brag about on the website.)

Re: Jellyfin 12.0

#286

Earlier quoted context omitted.

Are they not paying themselves?

No. https://github.com/jellyfin/jellyfin-meta/blob/master/polici... > Jellyfin funds itself exclusively from donations by individual users. It does not and will not accept any sponsorship or other monetary compensation in exchange for features, priority access, support, or any other work by the community. They spend the donations on paying for hosting servers, etc. They don't pay anyone a salary. Their post highlight…

Note that the lead dev of the official android clients does accept personal donations (via Github Sponsors and Buy Me A Coffee), but does not take requests on how to prioritize the work because he wants to keep it strictly as a hobby.

Re: Jellyfin 12.0

#287
post #185

So what I'm getting from the thread, this is Plex, minus the cancer, but also minus the features?

Jellyfin client on android is/was just a wrapper for webplayer so no native format support.

Jellyfin server (when i last tried it 5 years ago) couldn't run on same raspberry pi that hapily ran Plex

Re: Jellyfin 12.0

#288

Earlier quoted context omitted.

Classic HN user take. While $600 is obviously a pisspoor budget, they do incredible work compared to closed source solution companies like Plex. Not everything needs to be capitalistic, in fact the product pretty much sells and safeguards itself based on being freeware with pretty quality UX. Who will replace them?

"Capitalistic" is, I'm sure, meant derogatorily. I disagree with the sentiment, and I think the Jellyfin maintainers deserve at least a living wage for their time and efforts.

The Jellyfin devs have chosen for it to be a community/hobby project in order to avoid perverse incentives. That's a completely valid choice. There's a reason JF is the only mainstream media server solution that's continuously improved without any signs of enshittification, and personally I'm inclined to agree with the devs that keeping it completely non-profit has been a boon to its ongoing health and popularity.

Re: Jellyfin 12.0

#289

Earlier quoted context omitted.

You do need a DNS service with API access for automatically creating/renewing the certificates for things that are only served over tailscale though, since they aren't publicly accessible for the letsencrypt servers to talk to.

I've got a Caddy instance setup which proxies my traffic and has dead easy integration for domain DNS registration. Super handy

Same, it's fantastic. As long as you don't need to support as many requests per second on your hardware as something like NGINX could, Caddy is the way to go.

Re: Jellyfin 12.0

#290

Earlier quoted context omitted.

If there is one thing that needs to be re-written and consolidated it is the arrs ecosystem. Replacing/consolidating the arrs themselves is pretty straightforward. The trap that quickly becomes a token incinerator is incorporating the downloader into the library manager itself. A lot of learned lessons in that sabnzbd codebase.

As someone with coding projects in the is area would you care to elaborate on "a lot of learned lessons"?

Things like when to cancel early, how to handle par2, obfuscation, rars within rars, decoding articles. Just a mountain of "huh, didn't think of that being a complex problem" that was resolved over time.

I was able to replace the arr suite + sabnzbd with my own rust+ts frankenstein but had I known how complex the usenet piece was going to be I would have separated it into two phases.

Post reply on HN