2011-08-15, 00:39
I just noticed an interesting XBMC behavior that isn't what I expected (in a good way) that might make this script easier to manage moving forward (if someone can confirm anyway). Here goes.
I'm using XBMC 10.1 (stable) on Windows 7. I noticed tonight that I hadn't gotten the last two episodes of Falling Skies yet even though they are on the TNT web site. I looked at the files in Windows, and the problem was that they aren't named right. Apparently the TNT web site lists the last two episode as 1x108 and 1x109 (clearly not right). I decided to rename them to get XBMC to add them and then see what XBMC.MyLibrary would do with them.
When I renamed then I wasn't thinking, and I went ahead and changed the .mpg extent ion to .strm. Then I scanned for new content in XBMC. The weird thing is that XBMC happily added the .strm files to the library, and they play just fine. So at least on my install of 10.1 you apparently don't need to load the files as .mpg files and then do the database rename after the fact.
If this is all true and can be confirmed it seems like we could fork the code to do things qn easier way if you have 10.1 or have a configuration option for the version of XBMC that could bypass a huge chunk of the renaming logic.
I'm using XBMC 10.1 (stable) on Windows 7. I noticed tonight that I hadn't gotten the last two episodes of Falling Skies yet even though they are on the TNT web site. I looked at the files in Windows, and the problem was that they aren't named right. Apparently the TNT web site lists the last two episode as 1x108 and 1x109 (clearly not right). I decided to rename them to get XBMC to add them and then see what XBMC.MyLibrary would do with them.
When I renamed then I wasn't thinking, and I went ahead and changed the .mpg extent ion to .strm. Then I scanned for new content in XBMC. The weird thing is that XBMC happily added the .strm files to the library, and they play just fine. So at least on my install of 10.1 you apparently don't need to load the files as .mpg files and then do the database rename after the fact.
If this is all true and can be confirmed it seems like we could fork the code to do things qn easier way if you have 10.1 or have a configuration option for the version of XBMC that could bypass a huge chunk of the renaming logic.