3 ms·
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 t
by zeagle 4y ago
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 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.