Movie library is borked, suddenly has >200 movies name "Playlist", "Video" , "Stream" - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228) +---- Thread: Movie library is borked, suddenly has >200 movies name "Playlist", "Video" , "Stream" (/showthread.php?tid=359630) |
Movie library is borked, suddenly has >200 movies name "Playlist", "Video" , "Stream" - CaptainTivo - 2021-01-06 I run an Unraid server with my media on it and run Mariadb on the server to serve the database to multiple client (PC and Fire TV). This has worked well for over 6 years. I recently moved to version 18.9.0 to fix the problem of lost texture file URLs pointers. Then, I got a wild hare and did a "Library update", something I NEVER do and now my Movie library has hundreds of movies with tiles like "Playlist", "Video" and "Stream" some with around 200 duplicates! When I get "Information", the library entries point to internal files of DVD and Bluray such as VTS_15_1.VOB, etc. Details: The bogus movies come in sets, all with the same title. Movie title:"Playlist" There are 182 entries with "Playlist" as the title of the movie. "Information" shows the filename is a one of the .mpls files in the PLAYLIST folder of "Batman vs Superman" bluray rips. For example: "smb://Tower/Videos/Movies/Bluray/BATMAN_V_SUPERMAN_DOJ /BDMV/PLAYLIST/00697.mpls, etc. Movie title:"Stream", 240 movies with filenames like: "smb://Tower/Videos/Movies/Bluray/Total Recall (2012) /BDMV/STREAM/00628.m2ts, etc. In other words a movie entry from each stream file. Movie title: "They Live", 14 movies with filenames: "smb://Tower/Videos/Movies/DVD/They Live (1988)/VIDEO_TS/VTS_06_0.IFO, etc. Movie title: "Video Girl", 14 movies with filenames: "smb://Tower/Videos/Movies/DVD/They Live (1988)/VIDEO_TS/VTS_06_0.IFO, etc. Movie title: "Video", filenames: "smb://Tower/Videos/Movies/DVD/The Wolf of Wall Street (2013)/VIDEO_TS/VTS_13_1.VOB, etc. Movie title: "The Wolf of Wall Street", 19 files with names like: smb://Tower/Videos/Movies/DVD/The Wolf of Wall Street (2013)/VIDEO_TS/VTS_13_1.VOB I don't really see a pattern. It looks like the scraper decided to re-scrape a couple of movies into multiple movie entries from every file in the folder. I checked the log and found tons of errors like this: Quote:2021-01-05 14:15:41.334 T:46796 ERROR: InputStream: Error opening, smb://Tower/Videos/Movies/Bluray/BATMAN_V_SUPERMAN_DOJ/BDMV/PLAYLIST/00002.mplsBut I don't see why that would bork the database. I also just checked and these movies actually play fine so I don't understand the error, either. Anyway, the question is what to do? I started running the Backup plugin a few months ago so supposedly have library backups, but I have never done a restore so I don't know if that would even work. Should I try to restore, or re-scrape it all or what? Many thanks for any help. Here is the log. RE: Movie library is borked, suddenly has >200 movies name "Playlist", "Video" , "Stream" - CaptainTivo - 2021-01-06 (2021-01-06, 00:26)CaptainTivo Wrote: I run an Unraid server with my media on it and run Mariadb on the server to serve the database to multiple client (PC and Fire TV). This has worked well for over 6 years. I recently moved to version 18.9.0 to fix the problem of lost texture file URLs pointers.OK, so I fixed it. Here is what I did: First, I tried cleaning the database (Settings/Media/Clean Library). This did not work because it found a valid filepath associated with each bogus Movie entry I then renamed the movie folders in the source directories which contained the files pointed to by the bogus movie entries by appending ".hide" to each one (there were only 4). The I ran "clean library" again. This time, since it did not find the files pointed to by the movie entries, it deleted those entries. Now the database is correct again. Of course, the question is still: what caused this in the first place? I have had this problem before in the distant past (older versions) and fixed it manually by removing each bogus title from the library. But I have searched and not found anyone else reporting this particular weird error. |