Common structure for NFO support in XBMC and MEDIAPORTAL

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
azzuro Offline
Junior Member
Posts: 4
Joined: Apr 2012
Reputation: 0
Post: #1
I am a user of MediaPortal, My name is Azzuro, and I come to you today, to agree a common structure for supporting the NFO, in XBMC and MediaPortal, to enable the sharing and use of movies in a home or friends !

Currently MyVideo MediaPortal is reworked. and we are stuck on the format of the NFO!

that is why, I propose an agreement on the format NFO, for "our" two program use the same encoding!

URL on Forum Mediaportal to talk NFO Support: http://forum.team-mediaportal.com/thread...ost-857752

the structure below is ofr validation !

SubCatégories : <info></info>

Code:
<title></title>                            <!-- Title used in country  -->

    <originaltitle></originaltitle>        <!-- Real title -->

    <sorttitle></sorttitle>

    <sets>                                    <!-- Collection Movie  -->

      <set>First Set Name</set>

      <set order="?">Another Set With An Order</set>

    </sets>

<usergroups>                                <!-- user Group created for MePo  -->

    <userg></userg>

</usergroups>

    <rating></rating>                          <!-- 0 - 10 rating, can be decimal -->

    <ratings>                                <!-- 0 - 10 rating, can be decimal on other scrape -->

        <rating moviedb="imdb"></rating>

        <rating moviedb="allocine"></rating>

    </ratings>

    <language></language>                    <!-- The language of movie -->

    <country></country>

    <company></company>                      <!-- The studio company that produced the movie -->

    <studio></studio>                          <!-- Synonym for company tag -->

    <country></country>                        <!-- Country the video was produced in -->

    <year></year>                            <!-- Release date -->

    <top250></top250>                          <!-- the IMDB top 250 ranking, integer 1 - 250 or empty -->

    <votes></votes>                            <!-- currently unused in YAMJ -->

    <outline></outline>                        <!-- a short plot description -->

    <plot></plot>                              <!-- a longer plot description -->

    <review></review>

    <tagline></tagline>                        <!-- The tagline for the movie -->

    <runtime></runtime>                        <!-- Time of movie in "Xh XXmn" -->

    <mpaa></mpaa>                            <!-- Motion Picture Association of America -->

    <ccoc></ccoc>                            <!-- Commission de classification des oeuvres cinematographiques = French MPAA -->

    <certification></certification>        <!-- Used for all certification that isn't MPAA and only used if imdb.getCertificationFromMPAA=false -->

    <genres>                                <!-- multiple genre records may exist, including any custom ones -->

        <genre></genre>

        <genre></genre>

    </genres>

    <trailer></trailer>                        <!-- multiple trailer records may exist -->

Subcatégories : <Scrape></scrape>

Code:
<id></id>                              <!-- the IMDB id of the movie. includes the leading "tt". Use an id of 0 or -1 to disable further internet plugin scraping. -->

    <imdb>ttXXXXXXX</imdb>

    <tmdb></tmdb>

    <allocine></allocine>                    <!-- the allocine id of the movie. This should work for other plugins-->

    <cinepassion></cinepassion>                <!-- the cinepassion id of the movie. This should work for other plugins -->

Choice : <id moviedb="tmdb">11856</id> OR <tmdb></tmdb>

Subcatégories : <staff></staff>

Code:
<credits></credits>                        <!-- Writer name, one per entry -->

    <director></director>

    <directorimdb>nmXXXXXXX</directorimdb>

    <actor>                                    <!-- Multiple actor records may exist -->

        <name></name>

        <role></role>

        <thumb></thumb>

        <imdb>nmXXXXXXX</imdb>

        <birthdate></birthdate>                <!-- Format DATE dd-mm-yyyy -->

        <birthplace></birthplace>

        <deathdate></deathdate>                <!-- Format DATE dd-mm-yyyy -->

        <deathplace></deathplace>

        <minibiography></minibiography>

        <biography></biography>

    </actor>

Subcatégorie : <picture></picture>

Code:
<thumb></thumb>                          <!-- url of poster image. use URL formatting, such as http:// for internet resources or (movie.tbn or movie.jpg)? for local resources -->

<fanart>

        <thumb></thumb>                    <!-- url of fanart image. use URL formatting, such as http:// for internet resources or (movie-fanart.jpg) for local resources -->

</fanart>

Root : <movie></movie>

Code:
<playcount></playcount>                    <!-- COunt of played movie (1) -->

    <watched></watched>                        <!-- This will mark the movie watched or unwatched (false / true) -->

    <lastplayed></lastplayed>                <!-- date format dd-mm-yyyy(hh-mm) -->

Subcatégories ; <fileinfo></fileinfo>

Code:
<streamdetails>

            <videosource></videosource>                <!-- The video source of the file SCRENNERS / DVD / DVDRIP ... -->

            <videooutput></videooutput>                <!-- The video output of the file -->

            <fps></fps>                                <!-- The Frames Per Second value for the movie. NOTE: This should be a valid float value (with a ".") -->

            <video>

                <codec></codec>

                <aspect></aspect>

                <width></width>                <!-- Width of the video file -->

                <height></height>              <!-- Height of the video file -->

            </video>

            <audio>                            <!-- multiple audio stream may exist -->

                <codec></codec>

                <language></language>

                <channels></channels>

            </audio>

            <subtitle>

                <language></language>        <!-- in MKV or external subtitle (movie.en.srt if exist)  -->

            </subtitle>

        </streamdetails>
(This post was last modified: 2012-04-12 08:39 by azzuro.)
find quote
technick Offline
Junior Member
Posts: 23
Joined: Mar 2012
Reputation: 0
Location: Lyon (France)
Post: #2
I suppose that you know this : http://wiki.xbmc.org/index.php?title=Imp...rt_library
find quote
AnalogKid Offline
Fan
Posts: 645
Joined: Feb 2009
Reputation: 141
Post: #3
(2012-04-08 01:14)technick Wrote:  I suppose that you know this : http://wiki.xbmc.org/index.php?title=Imp...rt_library

I'm sure he's aware of that...

His proposal is more about rationalising the differences in NFO structure so that one NFO fits all.

The only issue I can see though is more of a philosophical one -

Just because they DO share a largely common NFO format, why should either seek to create a standard? There are other Media Centers out there too that have metadata floating around the file system, so why not gravitate to one of those 'standards' ?

I'm not saying it's a bad idea! the above is a purely philosophical comment.
I wonder how many folks use MP and XBMC (i used to, but moved to XBMC permanently about 3 years ago), and I didn't find migration a huge deal even without NFO's (if your media is well structured and well named MP and XBMC manage to work well anyway).
find quote
azzuro Offline
Junior Member
Posts: 4
Joined: Apr 2012
Reputation: 0
Post: #4
(2012-04-08 01:55)AnalogKid Wrote:  
(2012-04-08 01:14)technick Wrote:  I suppose that you know this : http://wiki.xbmc.org/index.php?title=Imp...rt_library

I'm sure he's aware of that...

yes, I based on many sources, including: XBMC (Import: Export), XBNE, MP, YAMJ (MovieJukebox)

I add things, and create "categories" for a better reading, but if it is not possibletoo bad ...

(2012-04-08 01:55)AnalogKid Wrote:  His proposal is more about rationalising the differences in NFO structure so that one NFO fits all.

The only issue I can see though is more of a philosophical one -

Just because they DO share a largely common NFO format, why should either seek to create a standard? There are other Media Centers out there too that have metadata floating around the file system, so why not gravitate to one of those 'standards' ?

I'm not saying it's a bad idea! the above is a purely philosophical comment.
I wonder how many folks use MP and XBMC (i used to, but moved to XBMC permanently about 3 years ago), and I didn't find migration a huge deal even without NFO's (if your media is well structured and well named MP and XBMC manage to work well anyway).

I do not want to remake the world, just a common format, but based on what exists, because every editing program nfo, not all the same structure.

But, initially MP only works with a database, and does not support nfo, except for the import MovingPicture ... (Personally I do not use a database), personal choice!

Now I propose to have an NFO file complete, and free choice of the software to use any information or not!

but that is the same for maintenance, sharing, and devellopement of mediacenter or independent software (NFO editors ...)

I think I have gathered all the necessary sections, now if you are missing data, or that the model does not fit you, I'm open to talk, and I am aware that I am conquered land,
find quote
azzuro Offline
Junior Member
Posts: 4
Joined: Apr 2012
Reputation: 0
Post: #5
Post 1 updated by subcatégories
find quote
NEOhidra Offline
Senior Member
Posts: 104
Joined: Dec 2011
Reputation: 1
Location: BG
Post: #6
I like the idea of one common format but it seem that there are no fans among the dev team.
find quote
RockerC Offline
Senior Member
Posts: 248
Joined: May 2011
Reputation: 3
Post: #7
I do not get why XBMC and MediaPortal not uses a standard XML (.xml) file extension instead of NFO (.nfo) file extension for metadata export and import?

I mean the content is pure XML so why not just start to use the .xml file extension naming and try to force the scene to start using that as a standard?
find quote
Montellese Offline
Team-XBMC Developer
Posts: 3,500
Joined: Jan 2009
Reputation: 32
Location: Switzerland
Post: #8
It's not always pure XML. In case of mixed NFOs containing an XML part and then a scraper URL at the end we have a totally invalid XML document. Same goes for episode NFOs with multiple episodes inside IIRC. Those have two root elements.

Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.

[Image: badge.gif]
find quote
zag Offline
Team-XBMC Member
Posts: 1,551
Joined: Oct 2007
Reputation: 18
Location: UK
Post: #9
Its a historical thing and just unfortunate it uses the .nfo extension. Or some would say fortunate as its easy to search for an IMDB link in a scene nfo or a xbmc nfo.

Media portal should make their files compatible.

When I helped with MeediOS we adopted the XBMC nfo standard because it was so popular. Its actually very easy to parse.

HTPC - XBMC Gotham, OpenELEC, Harmony Smart Remote, Intel Haswell NUC, 40gb intel SSD, Core i3, 4gb RAM
Storage - 2 x qnap 8tb 419p+ NAS
Display LG 46" LCD + Casio Bulbless projector [PICS]
[Image: widget]
find quote
RockerC Offline
Senior Member
Posts: 248
Joined: May 2011
Reputation: 3
Post: #10
(2012-04-19 13:49)Montellese Wrote:  It's not always pure XML. In case of mixed NFOs containing an XML part and then a scraper URL at the end we have a totally invalid XML document. Same goes for episode NFOs with multiple episodes inside IIRC. Those have two root elements.
Yes but when you do an export from XBMC then the output is pure XML, so not only export the output using a .xml file extension?

At least make using a .xml file extension the default when exporting from XBMC, and make .nfo optional a via advance settings option?

If XBMC would make start using .xml file extension as a standard for metadata exporting then I am sure that the scene will follow Big Grin
find quote
YodaEXE Offline
Fan
Posts: 453
Joined: May 2010
Reputation: 0
Post: #11
(2012-04-20 16:10)RockerC Wrote:  
(2012-04-19 13:49)Montellese Wrote:  It's not always pure XML. In case of mixed NFOs containing an XML part and then a scraper URL at the end we have a totally invalid XML document. Same goes for episode NFOs with multiple episodes inside IIRC. Those have two root elements.
Yes but when you do an export from XBMC then the output is pure XML, so not only export the output using a .xml file extension?

At least make using a .xml file extension the default when exporting from XBMC, and make .nfo optional a via advance settings option?

If XBMC would make start using .xml file extension as a standard for metadata exporting then I am sure that the scene will follow Big Grin

Who cares about what the scene does? And why should XBMC change? What they're currently doing works fine, and they are under no obligation to make their files work with anything else.
find quote
Robotica Offline
Banned
Posts: 1,202
Joined: Aug 2010
Post: #12
(2012-04-20 16:10)RockerC Wrote:  
(2012-04-19 13:49)Montellese Wrote:  It's not always pure XML. In case of mixed NFOs containing an XML part and then a scraper URL at the end we have a totally invalid XML document. Same goes for episode NFOs with multiple episodes inside IIRC. Those have two root elements.
Yes but when you do an export from XBMC then the output is pure XML, so not only export the output using a .xml file extension?

At least make using a .xml file extension the default when exporting from XBMC, and make .nfo optional a via advance settings option?

If XBMC would make start using .xml file extension as a standard for metadata exporting then I am sure that the scene will follow Big Grin

As you know, a few years ago there was this patch: http://trac.xbmc.org/ticket/5944
find quote
Maxoo Offline
Fan
Posts: 342
Joined: Mar 2010
Reputation: 12
Location: Paris, France
Post: #13
@YodaEXE : A unified NFO strucutre would bring a lot of good things. And someone's gotta make the first move. This guy did it, why not let XBMC be part of it ?

Advantages that first came up :
- Ability to share files easily with friend WITH infos. Even if they don't use XBMC.
- Easier scraper design, you only got to support one structurre file, not one per software.
- Also that would render the nfo you get with .torrent not so useless (as they would probably use that new structure).
- Third party software too. Now, you got to switch option/software if you switch players. After, you can have any third party that use the new structure, whatever player you use.

Admin @ Passion-XBMC
(official french community)
(This post was last modified: 2012-04-20 20:08 by Maxoo.)
find quote
spiff Offline
Retired Developer
Posts: 12,386
Joined: Nov 2003
Post: #14
The whole point to it being xml is extensibility. Add whatever you need to the existing format, and it is all good. Breaking established patterns without a very good reason is quite counter-productive imo.
find quote
azzuro Offline
Junior Member
Posts: 4
Joined: Apr 2012
Reputation: 0
Post: #15
Hi XBMC Team/Users.
Sorry for times...
Now MP(1.3 beta) support NFO, Out Of Box. based on XBMC and standard structures.
i should post an templates file,

Thx
find quote