KojakWeb
05-02-2011 15:44:45
Hi,
First off, thanks for a fantastic application it's been a real help. Like a lot of others, I've toyed with a few other such applications, but for TV this is the most common sense approach to moving/renaming/scraping I've seen. I know you've announced that you're scaling back your development this year, but I thought I would be cheeky and ask you if you had any intentions of increasing the scope of your app to encompass MediaBrowser compatibility?
Like XBMC, they scrape data from TVdb but can also used locally stored metadata. Whereas XBMC uses nfo & tbn in each of the season folders, MediaBrowser uses xml & jpeg stored in a season\metadata folder. As the source data is the same, the are broad similarities between the nfo & xml files, although some of the flag names are different, and it looks like the xml contains more fields. The tbn and jpeg files are identical, the only difference is that it's existence needs to be specified in the xml file under the <filename> flag.
First off, thanks for a fantastic application it's been a real help. Like a lot of others, I've toyed with a few other such applications, but for TV this is the most common sense approach to moving/renaming/scraping I've seen. I know you've announced that you're scaling back your development this year, but I thought I would be cheeky and ask you if you had any intentions of increasing the scope of your app to encompass MediaBrowser compatibility?
Like XBMC, they scrape data from TVdb but can also used locally stored metadata. Whereas XBMC uses nfo & tbn in each of the season folders, MediaBrowser uses xml & jpeg stored in a season\metadata folder. As the source data is the same, the are broad similarities between the nfo & xml files, although some of the flag names are different, and it looks like the xml contains more fields. The tbn and jpeg files are identical, the only difference is that it's existence needs to be specified in the xml file under the <filename> flag.