Thank you again.
Sorry for repeating, but what really confuses me is this:
Quote:When Kodi scans, it searches folders. If it finds nfo files, it uses them. If it finds local artwork, it caches them. If it does not find one or the other or both, then it uses the scraper.
Local comes first, then the scraper is the fallback.
Even if I delete .nfo files(all of them in the folder) it still says "Locally stored information found", and then of course it deletes watched status.I am not sure would the same happen if I deleted all .nfo files from source, but I don't want to test it and possibly loose all the data.Unless you are sure it would keep the data?
Quote:Also use it to test the WatchedList addon. I should have mentioned that this addon will only work with a correctly scraped library. It requires correct UniqueID's. As you are using nfo files, I don't know how you created them, or how old they are and if they are correct for Kodi.
I created them via Export function(one per file), but some of the data was scrapped years ago.And since there is no way that I know of to refresh it without loosing watched status, it is one more example why current way is not ideal.
Quote:Yes, with this particular situation with Play Counts, Watched status, resume points and User Ratings, Kodi could do with a bit more flexibility.
But currently that flexibility does not exist, which is why you need to use the addon.
In my humble opinion this should be primary focus, as artwork and other things can be easily rescrapped.I am only part time Kodi user, but I will allow myself a few assumptions and suggestions that may be wrong.Hope you won't mind it:
Discussions about Kodi migration, backup and restore are going a long way back, and process is still the same.Moreover when Kodi was in infant stages people used one device for playback and today most of them have multiple players.I know it is hard to change fundamentals because of compatibility reasons, but a lot has changed since Kodi first appeared.
The way I see it Kodi is (maybe to) flexible with different scrapers(among others), which leads to not being able to have one source ID, so there is always question should we use TMDB, TVDB, IMDB, or something else.Also it stores info about files, not videos.
My suggestion is to use one source(IMDB is most popular and has biggest database) as Unique ID, that could be used to store/backup/restore necessary information.WatchedList addon is step in right direction(it uses IMDB), but as you noticed there are few drawbacks, which limits its use.Additional ID-s could be added as reserve for TVDB or TMDB.
Quote:Are you using Windows? If yes, you should install another Kodi using Portable Mode... https://kodi.wiki/view/Portable_mode
You can then do your testing here, without affecting your current install, so if you ruin the library it does not matter as you have not touched your main library.
Yes, both Win and Android.I usually test with VM, but in this case SQL DB and videos are on NAS, so I don't see a way to test properly with the same configuration.