Most of my peeves are addressed by this update, which is great. Jellyfin has undergone major improvements since the project's start, it really seems like an alternative for it's commercial, properietary counterparts
Unfortunately there's still no Tizen/Samsung Smart TV app for this so I'm sticking with Emby for now, although I'll give this release a go since the last few were really unstable, hopefully they've made some improvements there.
Just get a Roku or an Apple TV. The kind of people interested in setting up Jellyfin or Plex at home are nearly all the same people that will keep their TV from ever being smart by connecting it to the internet.
I would suspect most of the people that are interested in setting up Plex or Jellyfin are large consumers of media and would like to watch the media on their Plex/Jellyfin along with that available on streaming platforms. Plex has developed and regularly updates clients on almost all smart TV and streaming devices. My Plex usage is mostly on Roku TVs. My daughter accesses it while at her mother's via an Apple TV, my girlfriend via her Samsung TV and my best friend via his Xbox.
I'm not buying extra hardware so I can switch to a different platform - Emby works perfectly for me and my folks who can just about turn it on and find a TV channel. Changing inputs and using a different remote would be too much.
I just run the jellyfin container and mount a big directory videos.
Then I add a rule in my Caddyfile and can access those videos securely from my phone. The whole operation is a little more complicated than that but we're overestimating how difficult it is to run sophisticated services that have been containerized.
I can't remember exactly why, because I built it like almost a year ago now, but that was the most excruciating build process I've ever experienced. I blame Samsung for that, not Jellyfin.
Yeah, that's why I keep tizen tools installed on my PC. And with obscure error messages it's not easy to either build or sideload the app. Also with the automated updates on the TV and its preinstalled junk reinstalling itself everytime, it is hard to find the space to install in on a tv.
Glad to see big developments happening. Started my self-hosted media server journey with Emby, which worked well. But then I realized it wasn't fully FOSS. Then I found Jellyfin. Outstanding project. Other than the Samsung app build process being utterly terrible, I have no gripes with Jellyfin. Thank you, Jellyfin team.
I decided to try it out. I've been using xbmc/kodi with nfs + mysql for many years and while it works great overall there are some idiosyncracies with seeking too often causing a bitrate/speed mismatch error and slight AV desync. Also some older 480 content paradoxically doesn't play properly on newer kodi builds for some odd reason (e.g. at half speed with clipped audio despite passthrough).
First impressions are: I like the UI, it's an easy setup, but it is rather unfortunate that the native jellyfin android TV client can't play dolby vision content or I suspect HDR10. Common issue but maven's kodi build works with DV and has proper colour matching, proper passthrough without stutter on the shield TV (2019) which is huge.
I put it here for others looking into solving the problem above. For me the kodi jellyfin plugin running on a maven kodi build ( https://repo.kodinerds.net/index.php ) has no issues with this on a shield TV (2019). It seems to have solved the seek issues and stutter I had with nfs and DV & HDR+ work with passthrough. I wonder if it's the implementation of their nfs & performance vs http in jellyfin.
I'll have to setup a reverse proxy and play with transcoding.
Most of my peeves are addressed by this update, which is great. Jellyfin has undergone major improvements since the project's start, it really seems like an alternative for it's commercial, properietary counterparts
Unfortunately there's still no Tizen/Samsung Smart TV app for this so I'm sticking with Emby for now, although I'll give this release a go since the last few were really unstable, hopefully they've made some improvements there.
What kind of instability have you had? Maybe some of them aren't listed in their repo and could benefit from your experiences
For me it's mostly been usability problems like not really undestanding seasons with more than 99 episodes or the text desyncing if rotating the phone
General sluggishness, really really slow library scans, choppyness etc. I run Emby in the same VM and it works flawlessly.
Just get a Roku or an Apple TV. The kind of people interested in setting up Jellyfin or Plex at home are nearly all the same people that will keep their TV from ever being smart by connecting it to the internet.
I would suspect most of the people that are interested in setting up Plex or Jellyfin are large consumers of media and would like to watch the media on their Plex/Jellyfin along with that available on streaming platforms. Plex has developed and regularly updates clients on almost all smart TV and streaming devices. My Plex usage is mostly on Roku TVs. My daughter accesses it while at her mother's via an Apple TV, my girlfriend via her Samsung TV and my best friend via his Xbox.
I'm not buying extra hardware so I can switch to a different platform - Emby works perfectly for me and my folks who can just about turn it on and find a TV channel. Changing inputs and using a different remote would be too much.
I just run the jellyfin container and mount a big directory videos.
Then I add a rule in my Caddyfile and can access those videos securely from my phone. The whole operation is a little more complicated than that but we're overestimating how difficult it is to run sophisticated services that have been containerized.
There is a Tizen app for it but you'll have build it yourself with tizen-studio. https://github.com/jellyfin/jellyfin-tizen
I can't remember exactly why, because I built it like almost a year ago now, but that was the most excruciating build process I've ever experienced. I blame Samsung for that, not Jellyfin.
Yeah, that's why I keep tizen tools installed on my PC. And with obscure error messages it's not easy to either build or sideload the app. Also with the automated updates on the TV and its preinstalled junk reinstalling itself everytime, it is hard to find the space to install in on a tv.
Glad to see big developments happening. Started my self-hosted media server journey with Emby, which worked well. But then I realized it wasn't fully FOSS. Then I found Jellyfin. Outstanding project. Other than the Samsung app build process being utterly terrible, I have no gripes with Jellyfin. Thank you, Jellyfin team.
Is jellyfin at par with plex on Android TV? Last I tried it, small annoyances in the app drove me back to plex.
I decided to try it out. I've been using xbmc/kodi with nfs + mysql for many years and while it works great overall there are some idiosyncracies with seeking too often causing a bitrate/speed mismatch error and slight AV desync. Also some older 480 content paradoxically doesn't play properly on newer kodi builds for some odd reason (e.g. at half speed with clipped audio despite passthrough).
First impressions are: I like the UI, it's an easy setup, but it is rather unfortunate that the native jellyfin android TV client can't play dolby vision content or I suspect HDR10. Common issue but maven's kodi build works with DV and has proper colour matching, proper passthrough without stutter on the shield TV (2019) which is huge.
I put it here for others looking into solving the problem above. For me the kodi jellyfin plugin running on a maven kodi build ( https://repo.kodinerds.net/index.php ) has no issues with this on a shield TV (2019). It seems to have solved the seek issues and stutter I had with nfs and DV & HDR+ work with passthrough. I wonder if it's the implementation of their nfs & performance vs http in jellyfin.
I'll have to setup a reverse proxy and play with transcoding.