As provided by MIP, and supported by XBMC skins AEON, Serenity, and more. This
is essentially
the ability to add MediaInfo-sourced movie file properties to the <studio> tag
in the movie's
.nfo, as follows:
<studio>studio name / resolution / video codec / audio format / number of
channels / language
/ subtitle language1/ subtitle language2... </studio>
More information (from http://www.xbmc.org/forum/showthread.php?t=50312)
1) AEON can show Media Flags for the Source, Resolution, Studio, Audio,
Subtitles and Parental
Rating portions of a Movie
2) The 'Source' of a movie CANNOT be determined from the video file itself, for
this reason AEON
will parse the FILENAME for a relevant string (see list below).
To my mind this could be improved by ALSO parsing the <Studio> tag in the NFO
file (since a
user could PUT the info in there)
3) The Resolution, Studio, Audio and Subtitle portions of a Movie are read from
the <Studio> tag
of the NFO file for a movie.
This is a kludge to overcome the limitation of tags in NFO files. I personally
would have preferred
the invention of new explicit tags, but that's just me
4) The recommended formatting of the <Studio> tag is:
<studio>studio name / resolution / video codec / audio format / number of
channels / language
/ subtitle language1/ subtitle language2... </studio>
Here's a real world example
<studio>Lionsgate / SDp / WMV3 / WMA2 / 2ch / Sub /</studio>
5) AEON is not as smart as you'd think and actually pays NO heed to the
recommended
formatting!
The way AEON finds the Resolution, Studio and Audio portions on a movie is by
simple String
searching within the <Studio> tag. This is not even EXACT matching, it's
substring matching, so
whilst AEON looks for 'Fox', it will find 'Fox' in '20th Century Fox' and
'Twentieth Century Fox'
etc.
6) AEON will deduce the Audio format of a movie by looking at BOTH the Audio
Format and the
Number Of Channels
This means that:
AC-3, 6ch = DD5.1
AC-3, 8ch = DD7.1
DTS, 6ch = DTS5.1
DTS, 8ch = DTS7.1
2ch = DOLBY (this is technically an incorrect assumption, but that's the way it
works today)
Original issue reported on code.google.com by roamer...@gmail.com on 5 Jun 2009 at 5:42
Original issue reported on code.google.com by
roamer...@gmail.com
on 5 Jun 2009 at 5:42