2014-01-19, 09:41
EDIT: See the 4'th post onwards, I've confirmed this is working as intended on a fresh install, something is unfortunately wrong with my build. No bug to be found here, title adjusted as such.
Hi all,
I've done extensive testing, rather than bump my old, messy, 3 page thread of discovery, I've decided to start a new one. FWIW I am using a very very recent version of XBMC nightly, XBMCSetup-20140116-23680e1-master
This is what I know so far.
* Library cleanup is working correctly as of the above build for "regular" installs (no MySQL)
* Library cleanup is NOT working correctly on my particular MySQL setup and may be indicative of a bug.
I suspected the problem might be due to old database tables in MySQL (the ones for compatibility or whatever they are?)
I've now dropped those tables in MySQL (myvideos75, myvideos76) for testing, I now only have myvideos77 in MySQL the problem persists.
If anyone out there has a fresh, blank MySQL setup for testing and the nightly I've listed above, please do the following*
* Setup a new directory with a filetype of TV Shows (TVDB)
* Put a file in said directory called for example "The Food Hospital, S01E01.AVI" (or any TV show you know will be recognised)
* Update the library, so you now see your one episode of your new show.
* Now, rename the file to "The Food Hospital, S01E01.MKV" and update the library.
* Now, rename the file to ""The Food Hospital, S01E01.MP4" and update the library.
* Finally perform a cleanup of your database manually under the settings section.
On a regular build of the latest nightly, without MySQL, the missing .MKV and .AVI version in the database will be removed.
On at least my particular MySQL build, you will be stuck with the TV episode listed 3 times, it hasn't removed the missing files in the DB.
I thought this problem was just DVD (.TS / .VOB filled directories) originally but I was incorrect, either my database has a major, weird issue or there's a cleanup bug with MySQL removals.
* I know how to setup a clean MySQL configured XBMC but it is quite damn time consuming if I recall if someone else could confirm if there's a bug or my database "impervious to cleaning" I'd appreciate it.
Hi all,
I've done extensive testing, rather than bump my old, messy, 3 page thread of discovery, I've decided to start a new one. FWIW I am using a very very recent version of XBMC nightly, XBMCSetup-20140116-23680e1-master
This is what I know so far.
* Library cleanup is working correctly as of the above build for "regular" installs (no MySQL)
* Library cleanup is NOT working correctly on my particular MySQL setup and may be indicative of a bug.
I suspected the problem might be due to old database tables in MySQL (the ones for compatibility or whatever they are?)
I've now dropped those tables in MySQL (myvideos75, myvideos76) for testing, I now only have myvideos77 in MySQL the problem persists.
If anyone out there has a fresh, blank MySQL setup for testing and the nightly I've listed above, please do the following*
* Setup a new directory with a filetype of TV Shows (TVDB)
* Put a file in said directory called for example "The Food Hospital, S01E01.AVI" (or any TV show you know will be recognised)
* Update the library, so you now see your one episode of your new show.
* Now, rename the file to "The Food Hospital, S01E01.MKV" and update the library.
* Now, rename the file to ""The Food Hospital, S01E01.MP4" and update the library.
* Finally perform a cleanup of your database manually under the settings section.
On a regular build of the latest nightly, without MySQL, the missing .MKV and .AVI version in the database will be removed.
On at least my particular MySQL build, you will be stuck with the TV episode listed 3 times, it hasn't removed the missing files in the DB.
I thought this problem was just DVD (.TS / .VOB filled directories) originally but I was incorrect, either my database has a major, weird issue or there's a cleanup bug with MySQL removals.
* I know how to setup a clean MySQL configured XBMC but it is quite damn time consuming if I recall if someone else could confirm if there's a bug or my database "impervious to cleaning" I'd appreciate it.