Quote:
Originally Posted by GreenEyez 
XBMC doesn`t use Ember MM, Ember Media Manager is a standalone application similar to Media Center Master for scrapping metadata for local storage. The problem is i don`t like Ember. I doesn`t have an automatic way of doing it (auto-scanning for new content, auto downloading the metadata and auto-renaming the files) these things are crucial for large libraries and for a metadata app that will sit on the backend of the HTPC, doind these things in the background, just like in the 7MC Software guide. This is my goal when it comes to metadata, in both 7MC and XBMC

XBMC doesn`t use Ember MM, Ember Media Manager is a standalone application similar to Media Center Master for scrapping metadata for local storage. The problem is i don`t like Ember. I doesn`t have an automatic way of doing it (auto-scanning for new content, auto downloading the metadata and auto-renaming the files) these things are crucial for large libraries and for a metadata app that will sit on the backend of the HTPC, doind these things in the background, just like in the 7MC Software guide. This is my goal when it comes to metadata, in both 7MC and XBMC
Spot on GreenEyez and in the main I would steer any user away from 3rd party scraping apps. Generally where the recommended folder/file naming conventions are followed, then accuracy of scrape will follow. The issues start where naming conventions become complex (whether as a result of 'scene' downloads or unusual anal retentive requirements).
3rd party scrapers are extremely prone to changes in source code which can affect the way programme reads the nfo files it produces. Unless the application dev continually keeps up to date with changes in the source code, then this can render the application virtually useless and suddenly users poster art, info etc ceases to appear..
























