FYI NMJ does support NFO files....
Example;
Avatar.2009.Collectors.Ext.Cut.1080p.BluRay.DTS.dxva.x264.D-Z0N3 <--- Directory name
Inside this directory have the following files;
Avatar.2009.Collectors.Ext.Cut.1080p.BluRay.DTS.dxva.x264.D-Z0N3.mkv
Avatar.2009.Collectors.Ext.Cut.1080p.BluRay.DTS.dxva.x264.D-Z0N3.nfo
NMJ can and WILL be able to get the data from imdb.com
The only time it fails is if you manually look at the NFO file and it's filled with useless ASCII art in the header, I just strip it down to the basics or even just have the following line;
"
http://www.imdb.com/title/tt0499549/"
This overrides the detection algorithm in NMJ and just uses the URL as the definitive name of the content.
The nice thing about NMJ is it's easy to test. I just put the above filenames (simple text file) on a USB stick and create a database on it. On my system, I keep 2 separate drives for NMJ to test;
1 drive is properly named according to NMJ standards
1 drive is named according to the source they arrived in (torrents)
The torrent sourced drive never failed in NMJ as long as I keep the NFO accompanying the weird named mkv files.