Migration path from NAS+Kodi

[unmesh59]

I've been a long time Kodi user (since they were XBMC) but would like to migrate to a solution where the clients are lighter weight and more of the burden put on the server.

Hence jellyfin.

The Kodi clients I currently have are more powerful than the Smart TVs themselves and I'd like to keep using them in the interim instead of native Jellyfin clients.

The metadata is sitting in the current media folders, one folder per movie title, having been scraped by Ember Media Manager. As a baby step, could I spool up a Jellyfin server, point to NAS shares as the libraries and import the current .nfo and posters and fanarts instead of having everything be rescraped?

For new media, I could have Jellyfin scrape the metadata instead of Ember.

This way I could go back and forth between the native Kodi player and the Jellyfin addon to Kodi as a precursor to native Jellfin players.

Thanks.

[mcarlton00]

nfo files take precedence when populating metadata in the server, so things should more or less import directly into the server as is for you. There are some naming guidelines that will make the process more reliable if things don't scan in correctly.

https://jellyfin.org/docs/general/server/media/movies
https://jellyfin.org/docs/general/server/media/shows

[tmsrxzar]

The metadata is sitting in the current media folders, one folder per movie title, having been scraped by Ember Media Manager. As a baby step, could I spool up a Jellyfin server, point to NAS shares as the libraries and import the current .nfo and posters and fanarts instead of having everything be rescraped?

jellyfin should support all naming conventions Kodi does so the media is likely already named correctly
changes in jellyfin naming conventions are typically "in addition to" those

nfo files exported by Kodi work perfectly with Jellyfin therefor the expectation should be that if Ember creates nfo files that Kodi supports they should also work in jellyfin
*should because i have never used ember

[unmesh59]

Thanks, @mcarlton00 and @tmsrxzar

I will try it out

If I configure Jellyfin to keep metadata files in the media folders, is it possible to keep status such as "watched" or "restart video from this time" on the server in a centralized manner so that it applies to all Jellyfin clients?

[tmsrxzar]

If I configure Jellfin to keep metadata files in the media folders, is it possible to keep status such as "watched" or "restart video from this time" on the server in a centralized manner so that it applies to all Jellyfin clients?

that's not how it's "intended" to work, by default it's per user but you *might be able to use the trakt plugin to do it
the trakt plugin is configured per user and you can *probably configure the same trakt account for 2 jellyfin user accounts

purely theoretical, i have never tried to centralize watch states and i'm not sure trakt even syncs resume positions

[unmesh59]

If I configure Jellfin to keep metadata files in the media folders, is it possible to keep status such as "watched" or "restart video from this time" on the server in a centralized manner so that it applies to all Jellyfin clients?

that's not how it's "intended" to work, by default it's per user but you *might be able to use the trakt plugin to do it
the trakt plugin is configured per user and you can *probably configure the same trakt account for 2 jellyfin user accounts

purely theoretical, i have never tried to centralize watch states and i'm not sure trakt even syncs resume positions

In less than 30 minutes, I was able to spool up a Jellfin instance on an Ubuntu VM, add libraries from a CIFS share and install the client apps on a Roku and a Chromecast with Google TV! 

Thanks for your encouragement.

I will play with it some more.