[scott967]

The stuff on add_on data was never meant to be edited (with the exception now of the _exclusions.nfo file). So it uses hashes of the artist name. Anything you put in your local artist directory (images or override .nfo files) uses the artist's name specifically because you should be able to easily find and edit that stuff. So if you sent a local artist folder, then any images you want to use are stored in <path you specified>/<artist name>/extrafanart/ and any .nfo files you want to override (like bio and albums) go in <path you specified>/<artist name>/override. The wiki page has information on doing that, and it's still up-to-date and valid, even for 1.5.3.013 and on.

With this new method of storing artist nfos, wouldn't it be easier just to edit the stored nfo rather than creating an override nfo? Or maybe there is a chance of having the edits over-written perhaps? Also my usage scenario is that I have multiple XBMCs running in portable mode (except one on Android, not sure if that is an option). I use a local XBMC for testing and then deploy to the production copies (the media folders are on a NAS but so far I prefer to let each XBMC instance maintain its own db). So I am interested in being able to copy over all the AS data so as to not have to scrape from each instance. I'm not sure I see that having a local artist folder defined adds much value, except that it would use artist names instead of a hash. I suppose where I have multiple XBMC instances on a single machine I could use it to share the AS data. Interested in any setup ideas to best utilize AS (I mainly use the Ace skin to run AS in). In the past, when AS has misfired on an artist name from Last.FM I have gone in to Last.FM using the api in my browser and copy paste from the returned results into the nfos.

scott s.
.