Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1144716" data-attributes="member: 18896">The accepted format is outlined very detailed @ <a href="http://kodi.wiki/view/Naming_video_files/Movies" target="_blank">http://kodi.wiki/view/Naming_video_files/Movies</a>&nbsp;That is only needed when you expect Kodi to recognize the movie for its own import system. When you use NFO files it changes everything, as there is no need to re-obtain the information (the NFO can contain all the textual information, and artwork is simply seperate)&nbsp;Important thing to keep in mind is that XBMC/Kodi can match the NFO file to the media file, as that one contains everything for a flawless off-line import (otherwise Kodi would import via their scraper-script system). It can technically be called &quot;movie.mp4&quot; with &quot;movie.nfo&quot;, but that the NFO file contains the actual info that it is &quot;Avatar (2009)&quot;. More details on that are available at: <a href="http://kodi.wiki/view/NFO_files/Movies" target="_blank">http://kodi.wiki/view/NFO_files/Movies</a>&nbsp;The benefit of the filenaming that you used is that you do not need to have all those NFO files if all they contain is the IMDb tt-ID reference, but that still requires an on-line import then. And that is what MovPicNFO can assist with in ensuring that the NFO files contain everything that Kodi needs exported from the Moving-Pictures database that already did the on-line importing. The problem is sometimes that syntax evolves, so keep a close tab to ensure that the files generated for your collection are still valid for the Kodi version that you use.&nbsp;PS: For example I do not know if MovPicNFO supports clear=&quot;true&quot; attribute yet, which for me is critical in moving/updating. Of course it is easy to manage that with third party tools, but you get the idea.</blockquote>

[QUOTE="RoChess, post: 1144716, member: 18896"] The accepted format is outlined very detailed @ [URL='http://kodi.wiki/view/Naming_video_files/Movies'][B]http://kodi.wiki/view/Naming_video_files/Movies[/B][/URL] That is only needed when you expect Kodi to recognize the movie for its own import system. When you use NFO files it changes everything, as there is no need to re-obtain the information (the NFO can contain all the textual information, and artwork is simply seperate) Important thing to keep in mind is that XBMC/Kodi can match the NFO file to the media file, as that one contains everything for a flawless off-line import (otherwise Kodi would import via their scraper-script system). It can technically be called "movie.mp4" with "movie.nfo", but that the NFO file contains the actual info that it is "Avatar (2009)". More details on that are available at: [URL='http://kodi.wiki/view/NFO_files/Movies'][B]http://kodi.wiki/view/NFO_files/Movies[/B][/URL] The benefit of the filenaming that you used is that you do not need to have all those NFO files if all they contain is the IMDb tt-ID reference, but that still requires an on-line import then. And that is what MovPicNFO can assist with in ensuring that the NFO files contain everything that Kodi needs exported from the Moving-Pictures database that already did the on-line importing. The problem is sometimes that syntax evolves, so keep a close tab to ensure that the files generated for your collection are still valid for the Kodi version that you use. PS: For example I do not know if MovPicNFO supports clear="true" attribute yet, which for me is critical in moving/updating. Of course it is easy to manage that with third party tools, but you get the idea. [/QUOTE]

Verification