- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
I rate it a 10.10.0 out of 10.
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.
How do you all handle these things?
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.
Is that the native paths method they removed? I never used it and didn’t understand the reason for it, but I’m guessing its useful for some users?
Yep. Kodi slows down significantly if you have a large library and play through the addon. Native paths fixed that issue by playing directly from a network share instead.
Right gotcha. My library is only a few TB so I guess it doesn’t cause issues for me.
Tbh I’m waiting for Findroid to officially released its android TV client and then if it works well I might switch over from Kodi
Shame about the network location regression. That’s the only thing that keeps my kodi device from taking 5-15 seconds to load each sub menu.
What’s this about? I didn’t hear anything about it.
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.
from the article.
