2 ms·
Depends on how much you value your Kodi setup and how many "difficult to auto match" shows | movies you have. I wanted to run Kodi | JellyFin in parallel (two
by defrost 2y ago
Depends on how much you value your Kodi setup and how many "difficult to auto match" shows | movies you have.
I wanted to run Kodi | JellyFin in parallel (two Kodi client Android TV's in house) so that visitors with iPhones | Androids | Tables could browse content.
The local Kodi TV clients used the NAS box MariDB to hold meta data held in the local to content .NFO files (show ID's, descriptions, etc)
I've held off on that as the JellyFin docs are not clear and the small experiments I tried in isolation proved tricky to resolve issues.
The issues being getting JellyFin to load details from local.nfo files w/out making changes and|or getting JellyFin to not make additional .INFO files (more or less duplicates) and|or getting JellyFin to not trash existing artwork with new downloads.
I'm sure there are solutions here (eg: JellyFin can use seperate directories for it's meta-data (but then doesn't read the local .nfo files to get ambiguous shows 'right')), I've yet to put the hard hours in and these are the kinds of hiccups you may face.
It's moot if you have a small collection | don't care about existing artwork | etc.
IIRC you can disable transcoding on fly by server and trust the network | viewing client to handle full original content, etc.
I like JellyFin and used Emby in the past and use small JellyFin setups today - I just haven't resolved the issues in pointing it at a large curated collection and letting it rip making it's own parallel meta data w/out affecting pre-existing meta data.