- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
You must log in or register to comment.
I can’t really think of a better example of open source software than Jellyfin. The product, the team, the culture… always evolving and improving. I’m here for it!
Not to mention its birth. It’s the best example I can think of for how open source is supposed to work: it started as Emby, the Emby devs tried to close it off for profit, and the community fork became Jellyfin, which I’d argue has more than outgrown Emby.
You barely even hear about it anymore, it’s only ever Plex or Jellyfin.
I use Jellyfin heavily, and it’s a fantastic project, but I really wish they would address the issues with transcoding, specifically the ability to force it on.
My library contains a decent amount of HDR (lots of DV) content. On my TVs (using Nvidia Shield), it will direct play the DV content, resulting in a green picture. If I turn on burned-in subtitles or drop the bitrate and FORCE it to transcode, it’s looks perfect. I’ve resorted to just setting a low bitrate on clients so it always transcodes.
I’m really hoping a future version gives us the ability to set more fine-grained transcoding settings per-client. Even the ability to disable direct-play completely would be fantastic.
I think you can do some settings related to transcoding per user account. Maybe that will help.
10.10 included much better HDR format specificity and support. It’s possible your issue was fixed.
This is great, but as someone who uses the Jellyfin4Kodi plugin daily: 😬😬😬
Thanks for the heads up. Sounds like I will be staying on 10.9 for a little bit longer.
Being able to save trickplay images in the media folders is my most awaited feature, awesome! Edit: the setting can be found in the library settings, just fyi
Network path substitution is my jam and I am super bummed to not be able to use it. I love direct play capabilities for my clients so I am worried about upgrading to this version.
Did they abandon the Flatpak package? The Jellyfin Player Flatpak is up-to-date, but the Server package on Flathub is at 10.8.13 and no longer listed on the Jellyfin website
https://jellyfin.org/downloads/server
EDIT: Looking at an archive from earlier this year, the Flatpak was tagged as “Community”, not “Official”. So I guess I shouldn’t be too surprised that the random packagers did not keep up with releases.
https://web.archive.org/web/20240104000907/https://jellyfin.org/downloads/server/
Flatpaks really suck for anything other than GUI applications. I suggest going with docker/podman
I had no issue with it when I set it up on my Steam Deck. Setting up docker/podman through distrobox or something just seems like so much extra hassle compared to a Flatpak.
You’re running the server from the Steam deck?
Because even without Flatpak, there’s plenty of other package for different distros that are easy or easier than flatpak. You don’t have to go all the way to a docker.
It’s probably best to do it eventually but it doesn’t have to be today.
Yes, installing/running Jellyfin Server on Steam Deck. What would be the best way to install on an immutable OS like SteamOS where Flatpak is typically the go-to?
The jellyfin docker is really easy to set up. And then you get the benefit of complete portability.
If you really want it as a flatpak you could attempt to build your own with up to date versions. However that would likely take longer than using an official package.
So this WON’T break the “Jellyfin” Kodi plugin? Just making sure it’s not the same thing as “Jellyfin4Kodi”.
If you use the native mode in the Jellyfin Kodi plugin to play directly from a network share, it will break.
Ah, okay. I’ll hold off on updating then (I think I’m using native mode, but I can’t remember).
In the GitHub release, it is written: This release is still building. Please do not attempt upgrades until this section is removed.
What does it mean? When will I be able to upgrade my installation?
It means it is still building. You can upgrade your installation when that section is removed.
😂😂😂😂
Thanks, I was confused!
