You're viewing a single thread.
Great googly moogly I've solved the kodi conundrum
Issue: Kodi has Very Specific Naming Conventions. So do I . We do not share these conventions. I refuse to bow to the machine.
Solution: SymlinksIssue: I have a remote fileserver, you cannot UNC hard symlinks
Solution:Kodi does fine with soft symlinksIssue: Symlinks in windows are very different to linux, where they're more like shortcuts as windows has them hard coded to the kernel. Every single machine running kodi - currently two, lounge and bedroom, possibly a third with the brewery - will need its own symbolic link of every. single. file. on my file server named correct in order to scrape them and show them. My fileserver has 12tb on it.
Solution: Script written that will ask for a share name in UNC, then drill down every subdirectory and replicate the whole tree symlink form on local machine in directory of choice.Issue: Still not in kodi naming convention
Solution: filebot portable, which is free. Rename symlinks to match TVDB. Original files untouched.Issue: faults will occur if source files are moved or renamed
Solution: I just wrote another friggin' script that will go through every single symlink and subdirectory and list all that do not resolve in a txt file called broken_links.txt. Run that once a month or so and update as required and I'm dancing.Then it's just upkeep with new symlinks as files/folders added and double checking it scrapes ok.
Why not just run jellyfin as a service on your remote server, then access that service on each local device?
Because apps are not allowed to run on Enigma.
Fair enough. I have friends with windows frustrations and I try to convert them to the joy of Linux, but I understand not everyone is in a position to do that. I opened up my jellyfin instance to friends over covid to watch movies together and that was pretty fun.
The media pcs are chiefly for multiuser purpose and familiarity- personally i run slack :P