home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
NFO Scanner explained + issues?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="fforde" data-source="post: 524896" data-attributes="member: 52082"><p>Well the XBMC NFO format is the closest thing to a standard I am aware of; there is a semi-formal definition <a href="http://xbmc.org/wiki/?title=Import_-_Export_Video_Library#Movies" target="_blank">available on their wiki</a>. For the upcoming 0.8 release LRFalk01 has written a scraper that reads full movie details from NFO files (rather than just pulling the IMDb ID for more accurate retrieval like we do now). So with the next release it should be super easy to migrate from XBMC.</p><p></p><p>But as far as standards go and the possibility of Moving Pictures creating NFO files like this, I am not 100% certain the route we will take. The XBMC NFO "standard" is not incredibly flexible and in some places a bit limiting. For example there is no support for release date information (only release year) and the format does not take into account the fact that the release date varies from region to region. There is only one field for the certification of the movie (which is called MPAA, ignoring all the other rating bodies of the world). And then there is file specific data stored such as the path of the file, codec information etc, which I think really is not appropriate for such a file format. None of these things are really a problem for Moving Pictures at the moment, we too only store release year and we only store the rating of a single ratings body. But I think these things limit the flexibility and longevity of the format. Not that it couldn't be expanded. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p></p><p>Anyway just saying we haven't made a decision. But again, full NFO file reading is a go for 0.8.</p></blockquote><p></p>
[QUOTE="fforde, post: 524896, member: 52082"] Well the XBMC NFO format is the closest thing to a standard I am aware of; there is a semi-formal definition [URL="http://xbmc.org/wiki/?title=Import_-_Export_Video_Library#Movies"]available on their wiki[/URL]. For the upcoming 0.8 release LRFalk01 has written a scraper that reads full movie details from NFO files (rather than just pulling the IMDb ID for more accurate retrieval like we do now). So with the next release it should be super easy to migrate from XBMC. But as far as standards go and the possibility of Moving Pictures creating NFO files like this, I am not 100% certain the route we will take. The XBMC NFO "standard" is not incredibly flexible and in some places a bit limiting. For example there is no support for release date information (only release year) and the format does not take into account the fact that the release date varies from region to region. There is only one field for the certification of the movie (which is called MPAA, ignoring all the other rating bodies of the world). And then there is file specific data stored such as the path of the file, codec information etc, which I think really is not appropriate for such a file format. None of these things are really a problem for Moving Pictures at the moment, we too only store release year and we only store the rating of a single ratings body. But I think these things limit the flexibility and longevity of the format. Not that it couldn't be expanded. :P Anyway just saying we haven't made a decision. But again, full NFO file reading is a go for 0.8. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
NFO Scanner explained + issues?
Contact us
RSS
Top
Bottom