2009-03-15, 23:16
Quote: Originally Posted by RockDawg View Post
Could someone tell me what is so useful about movie.tbn & movie.nfo? I must be missing something as I've seen it requested and then implimented in XBMC and now programs like this. What is better about it than than usual old method of <file name>.tbn & .nfo?
billyad2000 Wrote:I have to admit that i've wondered about this myself. It is certainly easier for me to have the filename contained in the nfo file.
To make movie.nfo work i'm going to have to start storing the filename in the nfo file to allow me link the nfo with the media for playback, mediainfo etc
I can chime in on those two as I did the initial request and patch after movie.nfo was created, which i believe was done for mymovies.xml support.
The key reason for them deals with folder level movies.
If you have a folder, and that folder contains any valid movie file and a movie.nfo, it will load that nfo file. It doesn't care what the file name is for the movie, or what the folder name is, stacking doesn't matter, rar doesn't matter, movie.nfo says this is a movie and here are the details. It only does one check when loading into xbmc, make sure it's not a folder.
The same thing applies for movie.tbn and fanart.jpg as well as movie-trailer.<ext> .. later it was changed so that you could different extensions for the images as well.. .png, .gif, .jpg, etc instead of .tbn
The new formats make it easier to explain as well, folks don't have to understand how stacking works, or the requirements for the filename.