NMJTOOLBOX2 (FOR NMJV2) 2/3/400 Series & VTEN – 19/12/15

Updated the program to the latest MediaInfo to correctly identify Dolby Atmos files.
IMPORTANT: When you upgrade to this version it will say your version of MediaInfo is incorrect. Say ‘Yes’ to allow NMJToolbox2 to download the correct file. However, the program cannot update a dll that it is using so will report an error. You will have to manually go to your NMJToolbox2 folder and extract the mediainfo.dll overwriting the one that you currently have. NMJToolbox2 can then be relaunched and should be using the new dll file.

Error message when opening a database with no movies in it (eg a music only database).

4 thoughts on “NMJTOOLBOX2 (FOR NMJV2) 2/3/400 Series & VTEN”

  1. Love the program!

    Is it common for user created tv shows with exported nfos and pictures to not use the nfo or pictures when added back in?

  2. The program should always use the local image if there is one in the correct place. Same goes for nfo files but I have to admit that I have not thoroughly tested them as I don’t use nfo files myself. I will give it a test and see what results I get.

    I assume that these are exported by NMJToolbox2 itself not ones created by another program?

    1. Thanks for the quick response!

      Yes, the nfos and pics were exported from the toolbox. All other files seemed fine except tv shows manually entered and any movies in multiple parts show up as multiple movies. I’m guessing there is no way around the movie issue, but I’m surprised those tv shows ignore the nfo and pics. I’ve tried scanning folders and adding individually with the same results.

      It’s been a while, but I think when scanning it also skips 3D tags, maybe it’s not in the nfo?

      Thanks again! 🙂

  3. Hi Rod, You seem to have found some quirks in the nfo processing. I will have a look at them and see if I can solve the issues you raise. Certainly it should be using the local images irrespective of the nfo file (I assume it is looking in the wrong place).

    I tried to stick to what CloudMedia used as an nfo for their file browser and I also assume they don’t have a ‘3d’ value in their XML, but I can easily add that.

    I will look into it and hopefully fix some/all of these issues on a future release.

Comments are closed.