(2019-09-22, 09:53)DaveBlake Wrote: But AFAIK devices set-up that way still have local userdata and hence local smart playlists.
Doesn't have to be set up like that. You can use
path substitution
to share all sorts of things around between different Kodi instances.
For instance, I share the favourites off one machine to all my others. When it's updated on the main rig, it automatically is replicated to all the others. All that is needed is an advancedsettings.xml on each of the
other machines. I also use path subs to replicate the playlists on each machine so that they are all the same. Creating or modifying a playlist on any machine is auto replicated on all the others.
I use mariadb for the database server and my media (both video and audio) is shared via NFS and SMB. The NFS shares are strictly for
my media and SMB is for the kids. This way I don't need to worry that adding something to a library might accidentally end up on the Kids Pi as it hasn't got the credentials needed to access the NFS shares.
The main instance of Kodi has all the sources added to it and that's the one that does any scraping and updating of the libraries. Because everything is done with network paths, none of the other machines need any sources adding to them. TV is also networked around the house, but that's just a case of pointing the TVH addon on each machine at the server and the backend takes care of the rest.
So yes, it is perfectly possible to have multiple instances of Kodi around your house but have them all sharing a centralized pool of data. You just have to be sensible about what you are substituting across instances. You can't substitute
special://musicplaylists/
and
special://videoplaylists/
you have to do the top level
special://profile/playlists/
and substitute the lot for it to work.