Each case is different, each priority set is different.
That is why it is so difficult to recommend these options blindly to people. For that optimal local GUI performance I sacrifice features, like never having my remote access library ever be perfectly the same as my local library, but there is no solution that can be everything for everyone. My MySQL server that runs my library eats ram like a pig, but I get optimal GUI performance.
SERVIIO CONSOLE NOT WORKING SOFTWARE
Personally I hit a point where my library is so big that NONE of the major solutions work "out of the box." My options were to either deal with usage hacks (like the scan the show root trick) or throw enough extra power and software at the scalable open source solution to make it work. He has the lifetime pass, he uses it all over the place. I have a friend that SWEARS by Plex with everything. What solution works best for you depends completely on your scale. Whatever the source webserver is doesn't get hammered, and you never have to get that info again if you have to rebuild the library. With nfo files you get the info when the file downloads/rips/records one at a time instead of all at once. If nothing else they fail because the web server starts rejecting requests after a while when you slam it all at once like that. Scrapers by definition are a bit of a hack, and I never have met one that can take a 300+ show library and not quit every now and then. If you check the logs the reason probably is the scraper is failing somewhere in your huge library. Like Aikouka mentioning that scrapers work better from the show root page- I have had the same experience in multiple pieces of software. Doesn't matter the software, the scrapers are all very similar in their benefits and weaknesses. The problem with scrapers is that eventually your library gets so big that the scrapers have trouble with it. Click to expand.With Kodi you optimally go by nfo files.
0 kommentar(er)
