User:Karellen/scratchpad: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:
|4. '''[[NFO_files|NFO Files]]'''
|4. '''[[NFO_files|NFO Files]]'''
<!--:*'''[[NFO_files/movies|Movies]]'''
<!--:*'''[[NFO_files/movies|Movies]]'''
:*'''[[NFO_files/tvshows|TV Shows]]''' -->
:<!--*'''[[NFO_files/tvshows|TV Shows]]''' -->
:*'''[[NFO_files/music|Music]]'''
:*'''[[NFO_files/music|Music]]'''
<!--:*'''[[NFO_files/musicvideos|Music Videos]]'''-->
<!--:*'''[[NFO_files/musicvideos|Music Videos]]'''-->
Line 20: Line 20:
|}
|}
{{mininav|[[Video library]] {{l2| [[Music library]] }} }}
{{mininav|[[Video library]] {{l2| [[Music library]] }} }}




Line 43: Line 42:
*There is no XML tag for ''votes'' of individual Songs. This can only come from the music file tags. Album ''votes'' can come from either online or local nfo scraping.
*There is no XML tag for ''votes'' of individual Songs. This can only come from the music file tags. Album ''votes'' can come from either online or local nfo scraping.
*FLAC rating contained within the Music File Tag is scored out of 100. Kodi converts this value to its equivalent value out of 10. Values less than 10 in the FLAC music file tag will return a rating of 0 in Kodi.<br />
*FLAC rating contained within the Music File Tag is scored out of 100. Kodi converts this value to its equivalent value out of 10. Values less than 10 in the FLAC music file tag will return a rating of 0 in Kodi.<br />
{{Red|The information in the remainder of this section is provided for technical interest only. It can be safely disregarded if you have no technical interest in certain functions}}<br />
*The data within the nfo file should, theoretically, all go to/come from somewhere in the database but, because the content source of the data field can be diverse, the data does not always come from a single source or go to a single database field. Scanning is not just about reading data but processing it too. As some fields are initially set from tags and can then be overwritten by nfo data, there is also a merge process involved in scraping.<br />
*There exist peculiarities with some XML tags in the nfo files:
**'''<name>''' in artist.nfo can overwrite the name of the artist in the artist table, if "prefer online info" is "enabled", but does not change that name anywhere else
**'''<releasedate>''' is required as part of the internal function of the online scraping process. It does not map directly to any db field, and nothing (currently) happens with its data. Exporting the library to nfo files will create an empty XML tag. It is not used during import/scrape.
**'''<artistdesc>''' tag in the album.nfo file is related to the strArtists field of the album table of the database. It is derived from ALBUMARTIST and ALBLUMARTISTS tags from the music file tags. If those two tags are empty, then it will be derived from ARTIST and ARTISTS tags in the music files. It is exported to album.nfo as <artistdesc> but the value is not imported/scraped.
**'''<releasetype>''' appears in the album.nfo by mistake. It is an internal flag that, in nfo files, will always be output as ''<releasetype>album</releasetype>'', and it is ignored during import/scrape of the nfo file. It relates to the strReleaseType field of the album table in the database. It does '''not''' relate to the RELEASETYPE tag in the MusicFile, which connects to ''<type>'' in album.nfo.
**'''<track>''' XML tag, and its children tags in the album.nfo, are not related in any way to the songs in the music library or in the Song table of the database. This XML tag and its children are related to the [[Databases#albuminfosong|albuminfosong]] table which simply provides more descriptive details of the album, which can be displayed by some skins. The presence of ''<musicBrainzTrackID>'' under ''<track>'' is a mistake and is always empty. It is recommended that when creating your own nfo, that these XML tags be omitted from the album.nfo. These XML tags have been removed in v18.<br />
*There are music file tags that are not saved to the database, therefore there are no XML tags. The music file tags are accessed by the music player at the commencement of playback.
{|class="prettytable"
! Music File Tags Not Stored In DB
|-
|MUSICBRAINZ_TRACKID
|-
|CUESHEET
|-
|LYRICS
|-
|REPLAYGAIN_TRACK_GAIN
|-
|REPLAYGAIN_ALBUM_GAIN
|-
|REPLAYGAIN_TRACK_PEAK
|-
|REPLAYGAIN_ALBUM_PEAK
|-
|METADATA_BLOCK_PICTURE or COVERART or COVERARTMIME
|}
*In music the only XML tags with a qualifier is ''Rating'' and ''User Rating''. It limits the maximum score that is possible for the given rating. This is relevant as Kodi switched from a maximum 5 rating to a maximum of 10 rating.
*A FLAC file can have a cuesheet embedded in the CUESHEET tag. In v17 and prior there is a Cue table in the Database to make possible replaygain handling during playback for those kinds of files, but this slowed down Kodi for all users, even when no cuesheets were in the music file. v17 removed ReplayGain handling, so there is no replay gain applied for songs from FLAC with embedded cuesheets. This made the songs node 30% faster. This function has been redesigned and will be re-implemented in v18.




Line 91: Line 55:
However the algorithm does not work for collaboration albums, those that have more than one album artist e.g. "Riding with the King" by Eric Clapton and BB King, or classical music with composer, orchestra and conductor given as the album artist. Also if you have not kept all songs by an artist under a unique folder, then the artist directory will probably be mis-identified. The result is that Kodi can find the wrong artist.nfo file, and give the artist some other artist's information, or fail to fine the artist.nfo you created}}
However the algorithm does not work for collaboration albums, those that have more than one album artist e.g. "Riding with the King" by Eric Clapton and BB King, or classical music with composer, orchestra and conductor given as the album artist. Also if you have not kept all songs by an artist under a unique folder, then the artist directory will probably be mis-identified. The result is that Kodi can find the wrong artist.nfo file, and give the artist some other artist's information, or fail to fine the artist.nfo you created}}


<div style="{{linear-gradient|top|#a1f5e4, #f5f5a1}}">
<div style="{{linear-gradient|bottom|#f5d3ff, #12b2e7}}">
'''''Naming & Saving conventions for your Music Artist *.nfo files:'''''
'''''Naming & Saving conventions for your Music Artist *.nfo files:'''''
{|
{|
Line 106: Line 70:




<div style="{{linear-gradient|top|#f5f5a1, #a1f5e4}}">
<div style="{{linear-gradient|top|#f5d3ff, #12b2e7}}">
'''''Naming & Saving conventions for your Music Album *.nfo files:'''''
'''''Naming & Saving conventions for your Music Album *.nfo files:'''''
{|
{|
Line 429: Line 393:


{{collapse bottom}}
{{collapse bottom}}
= Technical Details =
{{Red|The information in this section is provided for technical interest and reference only. It can be safely disregarded if you have no technical interest in nfo and database functions}}<br />
*The data within the nfo file should, theoretically, all go to/come from somewhere in the database but, because the content source of the data field can be diverse, the data does not always come from a single source or go to a single database field. Scanning is not just about reading data but processing it too. As some fields are initially set from tags and can then be overwritten by nfo data, there is also a merge process involved in scraping.<br />
*There exist peculiarities with some XML tags in the nfo files:
**'''<name>''' in artist.nfo can overwrite the name of the artist in the artist table, if "prefer online info" is "enabled", but does not change that name anywhere else
**'''<releasedate>''' is required as part of the internal function of the online scraping process. It does not map directly to any db field, and nothing (currently) happens with its data. Exporting the library to nfo files will create an empty XML tag. It is not used during import/scrape.
**'''<artistdesc>''' tag in the album.nfo file is related to the strArtists field of the album table of the database. It is derived from ALBUMARTIST and ALBLUMARTISTS tags from the music file tags. If those two tags are empty, then it will be derived from ARTIST and ARTISTS tags in the music files. It is exported to album.nfo as <artistdesc> but the value is not imported/scraped.
**'''<releasetype>''' appears in the album.nfo by mistake. It is an internal flag that, in nfo files, will always be output as ''<releasetype>album</releasetype>'', and it is ignored during import/scrape of the nfo file. It relates to the strReleaseType field of the album table in the database. It does '''not''' relate to the RELEASETYPE tag in the MusicFile, which connects to ''<type>'' in album.nfo.
**'''<track>''' XML tag, and its children tags in the album.nfo, are not related in any way to the songs in the music library or in the Song table of the database. This XML tag and its children are related to the [[Databases#albuminfosong|albuminfosong]] table which simply provides more descriptive details of the album, which can be displayed by some skins. The presence of ''<musicBrainzTrackID>'' under ''<track>'' is a mistake and is always empty. It is recommended that when creating your own nfo, that these XML tags be omitted from the album.nfo. These XML tags have been removed in v18.<br />
*There are music file tags that are not saved to the database, therefore there are no XML tags. The music file tags are accessed by the music player at the commencement of playback.
{|class="prettytable"
! Music File Tags Not Stored In DB
|-
|MUSICBRAINZ_TRACKID
|-
|CUESHEET
|-
|LYRICS
|-
|REPLAYGAIN_TRACK_GAIN
|-
|REPLAYGAIN_ALBUM_GAIN
|-
|REPLAYGAIN_TRACK_PEAK
|-
|REPLAYGAIN_ALBUM_PEAK
|-
|METADATA_BLOCK_PICTURE or COVERART or COVERARTMIME
|}
*In music the only XML tags with a qualifier is ''Rating'' and ''User Rating''. It limits the maximum score that is possible for the given rating. This is relevant as Kodi switched from a maximum 5 rating to a maximum of 10 rating.
*A FLAC file can have a cuesheet embedded in the CUESHEET tag. In v17 and prior there is a Cue table in the Database to make possible replaygain handling during playback for those kinds of files, but this slowed down Kodi for all users, even when no cuesheets were in the music file. v17 removed ReplayGain handling, so there is no replay gain applied for songs from FLAC with embedded cuesheets. This made the songs node 30% faster. This function has been redesigned and will be re-implemented in v18.





Revision as of 02:41, 9 September 2017

Steps to create your Music Library
1. Music File Tagging
2. Scanning Music Into Library
3. Scraping Additional Music Information
4. NFO Files
5. Music_artwork

Report NFO corrections:
[https:// here in the forum]

Home icon grey.png   ▶ Video library
▶ Music library
▶ scratchpad


Requirements

As the Music section of Kodi has many differences to the Video section of Kodi, please read this section to ensure your music and artwork are correctly scraped and displayed.


Understanding the Music Library

Adding Music to Library

Music nfo Specific Requirements

  • A number of database fields can be populated initially by music file tags, but then be overwritten by online or nfo scraping. Whether this occurs depends on the setting Prefer Online Information in Settings>Media Settings>Music. If disabled, these fields will remain with the data scanned from the Music File tags. If enabled these fields will be overwritten by information obtained from either the online or local nfo file scrape. The affected fields are shown below in the section Available nfo Tags.
  • In the album.nfo the top level <artist> tag has been deprecated and is not shown in any sample nfo files. Applies to v12 and prior.
  • There is no XML tag for votes of individual Songs. This can only come from the music file tags. Album votes can come from either online or local nfo scraping.
  • FLAC rating contained within the Music File Tag is scored out of 100. Kodi converts this value to its equivalent value out of 10. Values less than 10 in the FLAC music file tag will return a rating of 0 in Kodi.


nfo Placement

Music will fetch additional album and album artist information from nfo files.

For additional album information each album needs to be in its own unique folder, and have a separate album.nfo file located there. See the first table below.

For additional album artist information each artist needs a separate artist.nfo file located in what Kodi determines as the unique common folder for that artist. Kodi does not fetch additional artist data for artists that only feature on songs, either on compilation albums or as guest artists on songs in albums by others, and you do not have any albums by them in your collection.

Note: There are weaknesses in the way that Kodi determines the location of the artist folder. It looks for the folder that is common to all the songs with that album artist, the name of that folder is irrelevent. If you have multiple albums by an artist all under an artist folder then this works perfectly. However the algorithm does not work for collaboration albums, those that have more than one album artist e.g. "Riding with the King" by Eric Clapton and BB King, or classical music with composer, orchestra and conductor given as the album artist. Also if you have not kept all songs by an artist under a unique folder, then the artist directory will probably be mis-identified. The result is that Kodi can find the wrong artist.nfo file, and give the artist some other artist's information, or fail to fine the artist.nfo you created

Naming & Saving conventions for your Music Artist *.nfo files:

Saved Artist as File Name Save Location
Artist\Album\Songs artist.nfo f:\MyMusic\Stevie Nicks\artist.nfo


Naming & Saving conventions for your Music Album *.nfo files:

Saved Album as File Name Save Location
Artist\Album\Songs album.nfo f:\MyMusic\Stevie Nicks\Crystal Visions\album.nfo


Available nfo Tags

The following two tables list the available tags that can be used in each nfo file. The Album nfo section includes an example nfo for collaboration type albums.


Artist nfo

nfo (XML) Tag Required Overwrites Multiple ** Notes
<name></name> Yes Yes No Overwrites artist name in artist table, when "prefer online info" is "enabled". Does not change that name anywhere else
<musicBrainzArtistID></musicBrainzArtistID> No No No
<genre></genre> No Yes Yes
<style></style> No No Yes
<mood></mood> No No Yes
<theme></theme> No Yes Yes
<yearsactive></yearsactive> No No Yes
<born></born> No No No
<formed></formed> No No No
<instruments></instruments> No No No
<biography></biography> No No No
<died></died> No No No
<disbanded></disbanded> No No No
<thumb preview="path"></thumb> No No Yes Path to available online artwork
<path></path> No No No
<fanart></fanart> No No Yes Path to available online artwork
<album>
  <title></title>
  <year></year>
</album>
No No Yes Path to artwork in use
<art>
  <fanart></fanart>
  <thumb preview="path"></thumb>
</art>
No No Yes Path to artwork in use
Notes
** With multiple value fields those values are entered using XML tag per value, and when no data exists, the XML tag will not be created on export



Album nfo

nfo (XML) Tag Required Overwrites Multiple Notes
<title></title> Yes Yes No
<musicBrainzAlbumID></musicBrainzAlbumID> No Yes No
<artistdesc></artistdesc> Yes No No XML Tag created on Export, not used on Import
<genre></genre> No Yes Yes
<style></style> No Yes Yes
<mood></mood> No Yes Yes
<theme></theme> No Yes Yes
<compilation></compilation> Yes Yes No
<review></review> No Yes No
<type></type> No Yes No
<releasedate></releasedate> No No No Empty XML Tag created on Export, not used on Import/scrape
<label></label> No Yes No
<thumb preview="path"></thumb> No No Yes
<path></path> Yes No No
<rating max="10"></rating> No Yes No
<userrating max="10"></userrating> No No No
<votes></votes> No Yes No
<year></year> No Yes No
<albumArtistCredits>
  <artist></artist>
  <musicBrainzArtistID></musicBrainzArtistID>
</albumArtistCredits>
Yes Yes Yes
<track>
   <musicBrainzTrackID></musicBrainzTrackID>
   <title></title>
   <position></position>
   <duration></duration>
 </track>
Yes Yes Yes Not related in any way to the songs in the music library.

It is used by the albuminfosong table which simply provides descriptive data used by some skins.
musicBrainzTrackID is exported in error and will always be empty.
Can be safely ignored if creating your own nfo files.

<releasetype></releasetype> No No No Appears by mistake. Is not used
Notes
** With multiple value fields those values are entered using XML tag per value, and when no data exists, the XML tag will not be created on export



Sample nfo Files

An example of the artist.nfo and the album.nfo are provided. Use these as a guide to create your own nfo files, or to determine errors in your own files.


Artist nfo

Sample Music Artist nfo. Click the Expand button, to the right, to view


Music Album nfo

Sample Music Album nfo. Click Expand, to the right, to view.


Technical Details

The information in this section is provided for technical interest and reference only. It can be safely disregarded if you have no technical interest in nfo and database functions

  • The data within the nfo file should, theoretically, all go to/come from somewhere in the database but, because the content source of the data field can be diverse, the data does not always come from a single source or go to a single database field. Scanning is not just about reading data but processing it too. As some fields are initially set from tags and can then be overwritten by nfo data, there is also a merge process involved in scraping.
  • There exist peculiarities with some XML tags in the nfo files:
    • <name> in artist.nfo can overwrite the name of the artist in the artist table, if "prefer online info" is "enabled", but does not change that name anywhere else
    • <releasedate> is required as part of the internal function of the online scraping process. It does not map directly to any db field, and nothing (currently) happens with its data. Exporting the library to nfo files will create an empty XML tag. It is not used during import/scrape.
    • <artistdesc> tag in the album.nfo file is related to the strArtists field of the album table of the database. It is derived from ALBUMARTIST and ALBLUMARTISTS tags from the music file tags. If those two tags are empty, then it will be derived from ARTIST and ARTISTS tags in the music files. It is exported to album.nfo as <artistdesc> but the value is not imported/scraped.
    • <releasetype> appears in the album.nfo by mistake. It is an internal flag that, in nfo files, will always be output as <releasetype>album</releasetype>, and it is ignored during import/scrape of the nfo file. It relates to the strReleaseType field of the album table in the database. It does not relate to the RELEASETYPE tag in the MusicFile, which connects to <type> in album.nfo.
    • <track> XML tag, and its children tags in the album.nfo, are not related in any way to the songs in the music library or in the Song table of the database. This XML tag and its children are related to the albuminfosong table which simply provides more descriptive details of the album, which can be displayed by some skins. The presence of <musicBrainzTrackID> under <track> is a mistake and is always empty. It is recommended that when creating your own nfo, that these XML tags be omitted from the album.nfo. These XML tags have been removed in v18.
  • There are music file tags that are not saved to the database, therefore there are no XML tags. The music file tags are accessed by the music player at the commencement of playback.
Music File Tags Not Stored In DB
MUSICBRAINZ_TRACKID
CUESHEET
LYRICS
REPLAYGAIN_TRACK_GAIN
REPLAYGAIN_ALBUM_GAIN
REPLAYGAIN_TRACK_PEAK
REPLAYGAIN_ALBUM_PEAK
METADATA_BLOCK_PICTURE or COVERART or COVERARTMIME
  • In music the only XML tags with a qualifier is Rating and User Rating. It limits the maximum score that is possible for the given rating. This is relevant as Kodi switched from a maximum 5 rating to a maximum of 10 rating.
  • A FLAC file can have a cuesheet embedded in the CUESHEET tag. In v17 and prior there is a Cue table in the Database to make possible replaygain handling during playback for those kinds of files, but this slowed down Kodi for all users, even when no cuesheets were in the music file. v17 removed ReplayGain handling, so there is no replay gain applied for songs from FLAC with embedded cuesheets. This made the songs node 30% faster. This function has been redesigned and will be re-implemented in v18.




Return to top