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
MovPicNFO
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="Dadeo" data-source="post: 1062240" data-attributes="member: 27204"><p>Hi Scrounger;</p><p>Having just spent a ton of time developing a generic NFO grabber for MyFilms plugin that supports the many variants of the (so-called) XBMC NFO 'standard', I thought it might help if I shared what I learned. I ended up testing ~10 different apps that claim to support XBMC NFO standard <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite11" alt=":rolleyes:" title="Roll Eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /> The purpose of MyFilms NFO grabber is to allow users to use external media managers to manage their movie collection, so not intended to read MovPicNFO format, but while I was testing it I thought I would just check MovPicNFO anyways <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>As you mentioned a couple of times in this thread MovPicNFO does not conform 100% to XBMC NFO standard. TBH it isn't easy to, because the standard is not actually very complete, well defined or well documented! So each app that uses NFO files has extended the standard, plus there are numerous variations about how data is output in each tag, how multiple occurrences are handled, etc.</p><p></p><p>I realize the purpose of your plugin is mainly to support MovingPictures DB, so this is NOT a criticism or complaint. I just thought it might be helpful to let you know the major differences I noticed in MovPicNFO format from XBMC standard:</p><ul> <li data-xf-list-type="ul">As Rochess mentioned previously <writer> is not a supported tag - writers are normally output (and read from) <credits> tag. Some apps support <writer> but usually read and write <credits> as well. Of course, <credits> can include any 'person' who worked on the film (e.g. Producers). <strong>Sometimes</strong> roles are written in brackets - e.g. Scrounger (Producer) but with no consistency - e.g. could be (Writer), (Story), (Novel), etc. </li> <li data-xf-list-type="ul">There is a lot of variation re multiple occurrences (some apps repeat the tag like <genre> while others usually use a comma as separator). But I have never seen any app that supports a separator as the first character in the field like MovPicNFO uses (e.g. <director>|<name>|</director>)</li> <li data-xf-list-type="ul">The tag for studios is normally <studio> not <studios> (with occurrences often badly separated by commas which is a mess for 'Weinstein Company, The' which IMDb uses)</li> <li data-xf-list-type="ul">MovPicNFO writes AKAs to <originaltitle> which some apps use for matching since (depending on the grabber/source) the <title> may not be in English or match data on other sites. Unfortunately XBMC NFO standard does not include a definition for AKAs.</li> </ul><p>I had hoped that NFO could be a more universal format, but as more and more apps use it, it has become less and less standard. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p></blockquote><p></p>
[QUOTE="Dadeo, post: 1062240, member: 27204"] Hi Scrounger; Having just spent a ton of time developing a generic NFO grabber for MyFilms plugin that supports the many variants of the (so-called) XBMC NFO 'standard', I thought it might help if I shared what I learned. I ended up testing ~10 different apps that claim to support XBMC NFO standard :rolleyes: The purpose of MyFilms NFO grabber is to allow users to use external media managers to manage their movie collection, so not intended to read MovPicNFO format, but while I was testing it I thought I would just check MovPicNFO anyways ;) As you mentioned a couple of times in this thread MovPicNFO does not conform 100% to XBMC NFO standard. TBH it isn't easy to, because the standard is not actually very complete, well defined or well documented! So each app that uses NFO files has extended the standard, plus there are numerous variations about how data is output in each tag, how multiple occurrences are handled, etc. I realize the purpose of your plugin is mainly to support MovingPictures DB, so this is NOT a criticism or complaint. I just thought it might be helpful to let you know the major differences I noticed in MovPicNFO format from XBMC standard: [LIST] [*]As Rochess mentioned previously <writer> is not a supported tag - writers are normally output (and read from) <credits> tag. Some apps support <writer> but usually read and write <credits> as well. Of course, <credits> can include any 'person' who worked on the film (e.g. Producers). [B]Sometimes[/B] roles are written in brackets - e.g. Scrounger (Producer) but with no consistency - e.g. could be (Writer), (Story), (Novel), etc. [*]There is a lot of variation re multiple occurrences (some apps repeat the tag like <genre> while others usually use a comma as separator). But I have never seen any app that supports a separator as the first character in the field like MovPicNFO uses (e.g. <director>|<name>|</director>) [*]The tag for studios is normally <studio> not <studios> (with occurrences often badly separated by commas which is a mess for 'Weinstein Company, The' which IMDb uses) [*]MovPicNFO writes AKAs to <originaltitle> which some apps use for matching since (depending on the grabber/source) the <title> may not be in English or match data on other sites. Unfortunately XBMC NFO standard does not include a definition for AKAs. [/LIST] I had hoped that NFO could be a more universal format, but as more and more apps use it, it has become less and less standard. :( [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
MovPicNFO
Contact us
RSS
Top
Bottom