I just recently converted from kodi to jellyfin after a Nas hardware crash.
I run the server in a docker container on my Nas and the client on a Nvidia shield.
Works great, but there is one niggle I haven't figured out and had much better experience on kodi.
Subtitles.
I can't seem to find any adjustments for the subtitles in case they don't fit the video completely.
There is no menu I have found that allows for adjusting the timing of subtitles.
How are you all coping with this?
I use the arr stack and get subtitles through bazarr.
Probably a bad time to suggest the Jellyfin for Kodi plugin (since they removed the network paths in this version) but it's what I use for my main playback device.
All the goodies of playback via Kodi but play state and metadata gets synced from Jellyfin.
Another option of course would be to open the file(s) in MKVToolNix to add and correct the subtitle offset there.
Are you using subtitle sync in bazarr? I don't use jellyfin, but have found that bazarr has fixed most of my subtitles that were not in sync just by enabling the option. I think it's CPU intensive though, so don't do the whole library at once.
Depends on the platform you're using.
Mobile you have the integrated player that doesn't support subtitle offset and the web player that does.
Everything else is a version of the web player basically and they all support subtitle offset
Nvidia shield is a android device so it tracks that this is the mobile player without srt adjustment. That sucks though. Maybe I should look at kodi and jelly plugin...
Did you use docker compose file or just run a command to start the container?
Edit: I always use compose files. For that you can do the following:
docker compose pull
docker compose down
docker compose up -d
You don't technically need the stop, but I've found once or twice in the past where it was good to stop because of image dependencies that I forgot to put in my compose.
For running a command directly I found this website that seems to summarize it pretty well I think:
You'd place your compose file in the working dir /var/lib/sonarr. Depending on what tag you've set for the image in the compose file, it would be autoupdated, or stay fixed. E.g. lscr.io/linuxserver/sonarr:latest would get autoupdated whereas lscr.io/linuxserver/sonarr:4.0.10 would keep the container at version 4.0.10. If you want to update from 4.0.10, you'd have to change it in the compose file.
Many major enhancements to transcoding and playback, including support for software tonemapping of HDR10, HLG and DoVi, preliminary support for DoVi Profile 10, support for Dolby AC-4 audio, more stereo downmixing algorithms, QSV device selection, and more! Our FFmpeg is also now based off the upstream FFmpeg 7.0 release for additional features and improvements there.
Does that mean no grey mess anymore when playing HDR files?
Network paths in libraries have been fully removed and will no longer work. This functionality has been deprecated for a long time, and most of it was removed in 10.9.0, but this removes the remainder. See PR #12446. Third-party clients relying on this functionality should be able to re-implement it as required.
They're probably talking about Samsung TVs, not their android phones/tablets. Installing jellyfin on those things can be a chore. My experience with LG was similar. The official build was out of date and riddled with issues that didn't exist on other versions. It refused to play videos that worked well enough on other devices, transcode or no.
Speaking to #2, I'm surprised since I always use the "sign in from another device" feature, where I punch some numbers into the app on my phone and it signs me into the tv.
That said, the tv is running the desktop app.
Not sure what you mean by that. Jellyfin has had an up to date version in the play store for years.
Yes every Profile is separated into its own account, that's by design and will most likely never change. An easy PIN option in the local network existed for years. Now you can even login with your phone app by entering a displayed PIN.
I remember very few media that i had issues with in the past. Depending on the transcode hardware you have some things can be tricky
I tried Jellyfin recently and for some reason it doesn't play any media at all when I disable hardware transcoding, even though my media all is 1080 h264/h265 and I don't want to scale. On Plex it always seemed like I could just play everything natively, but Jellyfin seems like it always wants to transcode.
Even if I enable transcoding, stuff won't play nicely because I'm currently on a Pi4 (going to switch in the coming weeks to a proper server), but Plex is fine.
Echoing @Bronzie@sh.itjust.works, I downloaded the first party app right from the Play Store on my Samsung. Though I prefer the third party, Findroid, the first party app is good for the dashboard management.
When we launch Jellyfin, we are shown icons for what user, we select the user, and it opens the associated library. Similar to Netflix.
I started using Jellyfin about two years ago now, and have only encountered a codec issue here and there, but I've found it can be worked around by setting playback to another player, like VLC.
For the not all media played successfully, I found it was primarily down to transcode settings trying to hardware transcode file types my server can't hardware transcode. It's something worth playing with
It was forked but somehow lacked a huge amount of functionality that Emby had (and still has) Like I think it only supported films, not music or TV shows. The app infrastructure was awful across fire stick, Roku and android and wasn't backward compatible with the Emby apps. I just didn't see the point of forking it if you're just going to make it worse or only address the server side and neglect the clients. The whole thing has to work together with good clients and server.
when did you last try it and what clients? I've got friends/family accessing my library and I see them playing back stuff constantly and never seen or heard of any issues. This is across web, AndroidTV, Chromecast, Roku and mobile devices.