Scan Existing .NFO Files + Generate Blank .NFO Files.

I posted this previously in another thread. But I don't think you saw it, and it wasn't on topic with the old thread, so I am posting again...

Anyways, I noticed that in your "Things To Do" list you have listed: "22. Scan existing non xml nfo files for IMDB ID when scanning." I am very interested in this feature. I think XBMC already does this so it would be warmly welcomed within your program. One extra thing that would really make this feature pop is the ability to scan an .NFO file, grab the IMDB title, rename .NFO to .INFO, scrape for movie info, and generate XML .NFO file. That way our original .NFO files do not get overwritten. I hate when I lose the original scene .NFO, because it helps me identify a release after i've renamed it if a program arises (such as needing release-specific subs). In fact, I already renamed all my .NFO's to .INFO before I scrape with Media Companion, so maybe it would be cool if it scanned existing .INFO files as well.

One other suggestion I have is the simple ability to generate a blank .NFO for the selected movie. Sometimes you come across media that is scraped incorrectly because there are no entries for it in IMDB. In those cases you want a quick way to blank all the fields for the selected movie instead of manually deleteing each one.

What you suggest sounds reasonable, I was looking to rename existing nfo files and .info is as good as any.

billyad2000 wrote:

What you suggest sounds reasonable, I was looking to rename existing nfo files and .info is as good as any.

I'd rather the media companion files were called something else, '.xnfo" for example (to not create this problem in the first place), I assume you didn't do this top be compatable with XBMC? Could it be an option?

dbareis wrote:

billyad2000 wrote:

What you suggest sounds reasonable, I was looking to rename existing nfo files and .info is as good as any.

I'd rather the media companion files were called something else, '.xnfo" for example (to not create this problem in the first place), I assume you didn't do this top be compatable with XBMC? Could it be an option?

You are correct in your assumption, the only reason for the .nfo extension is to keep compatability with XBMC, which is after all, one of the primary purposes of the program.

It would likely have been preferable to use a different externsion in the beginning, .xnfo would have been ok, as would almost any unused (or unknown) 3 letter combination to be honest, why not just plain old .xml

Anyway, thats water under the bridge so to speak, so my only option at this time is to give people the option to rename their origional .nfo files, and .info is as good as any.

I vote for not renaming to .INFO and instead just move old NFO to a separate folder.
Because I think my movie dirs are getting too messy!

clutch9 wrote:

I vote for not renaming to .INFO and instead just move old NFO to a separate folder.
Because I think my movie dirs are getting too messy!

I know what you mean :-)

Wish all these files were created in their own subdirectory.