Official Kodi Wiki - User contributions [en]

Basic playlists

2016-09-27T21:54:49Z

Imsodin: Mention that playlist should not go directly into the given locations.

{{mininav|[[Playlists]] }} {{to do}}
<section begin="intro" />Kodi supports both basic playlists and '''[[smart playlists]]'''. A basic playlist is a normal text file that lists one or more media files (Audio or Video), and plays them in succession. You can either create your own or use existing playlists from other sources, such as a playlist generated from Winamp, iTunes, or other sources. Basic playlists can be created and edited directly from Kodi's GUI.<section end="intro" />

== Basic playlists ==
The main way to create and manipulate playlists in Kodi is through the playlist editors (both for normal and smart playlists).

=== How to create a normal playlist ===
[[File:Playlist queue.png|500px|right]]
You can add videos/songs or entire folders with the "Queue" action of your remote/keyboard ({{keypress|Q}} on a keyboard) or the '''"Queue Item"''' option in the context menu can be used. Kodi will add the selected item to the playlist and then advance to the next item in the window.

To see the currently loaded playlist, bring up the context menu. The currently playing/queued playlist is accessible via the '''"Current playlist"''' item in the left hand sidebar menu. If the playlist is currently empty then that option will not be visible in the sidebar menu.

While in the "Current playlist" window and pressing the '''Select''' or the '''Play''' button will start playback of your playlist.

When in the "Current playlist" view, you can save your playlist by bringing up the options in the left hand sidebar menu. Playlists are, by default, saved in a subfolder of [[userdata]]/playlists (separate folder for music, video and mixed playlists).
{{-}}

=== Current playlist window ===
{{anchor|Now Playing}}
The current playlist is a special window for the current audio or video playlist. This list is accessible from the left hand sidebar menu and [[Music#OSD .28On Screen Display.29|music OSD]]. Selecting an entry will start playback.
{{-}}<br />

==== Sidebar menu ====
[[File:Now playing 3.png|500px|right]]
On the default skin (Confluence) you can bring up these options by bringing up the sidebar menu (press {{keypress|left}} on a keyboard or remote).
;Shuffle
:Shuffles the currently playing playlist
;Repeat
:Repeats the currently playing playlist, options are: '''All''' songs/videos, '''One''' song/video or '''Off''' for no repeating.
;Save
:Saves the currently playing playlist
;Clear
:Clears the currently playing playlist
{{-}}<br />

==== Context menu ====
[[File:Now playing 2.png|500px|right]]
The context menu (press {{keypress|C}} on a keyboard) within the current playlist allows you to move the order of items or remove them.

On a [[keyboard]] you can also use:
* {{keypress|U}} - Move selected up
* {{keypress|D}} - Move selected down
* {{keypress|DEL}} - Remove from playlist.

A remote control with the proper [[keymap]] additions can also use those actions.
{{-}}

== Party Mode playlists ==
{{see|Party Mode}}

== Smart playlists ==
{{main|Smart playlists}}
{{#lst:Smart playlist|intro}}

== Other supported playlist ==
Kodi supports [http://en.wikipedia.org/wiki/PLS_%28file_format%29 PLS], Winamp [http://en.wikipedia.org/wiki/M3U M3U], [http://en.wikipedia.org/wiki/Cue_sheet Cue Sheets], and [[Smart playlists|Kodi Smart Playlist (XSP)]] playlists.

== Playlist folder location ==
The playlists should be placed into a folder named “music“, “mixed” or “video” in the following location:
* '''Windows XP:''' <code>Documents and Settings\<your_user_name>\Application Data\Kodi\userdata\playlists\</code>
* '''Vista/Windows 7:''' <code>Users\<your_user_name>\AppData\Roaming\Kodi\userdata\playlists\</code>
* '''Mac OS X:''' <code>/Users/<your_user_name>/Library/Application Support/Kodi/userdata/playlists/</code>
* '''iOS:''' <code>/private/var/mobile/Library/Preferences/Kodi/userdata/playlists/</code>
* '''Linux:''' <code>$HOME/.Kodi/userdata/playlists/</code>

{{Helix updated}}

[[Category:Video library]]
[[Category:Music library]]
[[Category:Manual]]

NFO files/Movies

2016-07-02T08:34:08Z

Imsodin: Explanation for credits

{{mininav|[[NFO files]]}}
=== Video .nfo Files containing XML data ===
1. The *.nfo file is an XML file containing the data for inclusion in the library.

movie.nfo will override all and any .nfo files in the same folder as the media files if you use the "Use foldernames for lookups" setting. If you don't, then moviename.nfo is used.
If there is only one .nfo file in a folder, The scraper will use it for all media files in that folder. If there are multiple media files in a folder, the *.nfo should be named exactly the same as the video file it is representing (ie. '''moviename.avi''' and '''moviename.nfo''').

<section begin="stacking note" />{{note|In the case of multi-part (stacked) video '''[[file stacking]]''', name the file either '''moviename.nfo''' or '''moviename-CD1.nfo''' where the first filename is '''moviename-CD1.avi'''.}}<section end="stacking note" />

{{note|If your movie is ripped as VOB's and stored in a 'VIDEO_TS' folder, you will have to name the file 'VIDEO_TS.nfo' and place it in the same directory with the VIDEO_TS.ifo file.}}

Additionally the 'set' tag can be used to help sort movies that are [[Movie Sets|part of a series or collection]] (ie Harry Potter, James Bond films). This sort of collection tagging must be done in the .NFO file before the movie is scanned into the library.

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Who knows</title>
<originaltitle>Who knows for real</originaltitle>
<sorttitle>Who knows 1</sorttitle>
<set>Who knows trilogy</set>
<rating>6.100000</rating>
<year>2008</year>
<top250>0</top250>
<votes>50</votes>
<outline>A look at the role of the Buckeye State in the 2004 Presidential Election.</outline>
<plot>A look at the role of the Buckeye State in the 2004 Presidential Election.</plot> 
<tagline></tagline>
<runtime>90</runtime> //runtime in minutes
<thumb>http://ia.ec.imdb.com/media/imdb/01/I/25/65/31/10f.jpg</thumb>
<mpaa>Not available</mpaa>
<playcount>0</playcount>
<id>tt0432337</id>
<filenameandpath>c:\Dummy_Movie_Files\Movies\...So Goes The Nation.avi</filenameandpath>
<trailer></trailer>
<genre></genre>
<credits></credits> 
<fileinfo>
<streamdetails> 
</streamdetails>
</fileinfo>
<studio>Dummy Pictures</studio>
<director>Adam Del Deo</director>
<actor>
<name>Paul Begala</name>
<role>Himself</role>
</actor>
<actor>
<name>George W. Bush</name>
<role>Himself</role>
</actor>
<actor>
<name>Mary Beth Cahill</name>
<role>Herself</role>
</actor>
<actor>
<name>Ed Gillespie</name>
<role>Himself</role>
</actor>
<actor>
<name>John Kerry</name>
<role>Himself</role>
</actor>
</movie>
</syntaxhighlight>

=== Video .nfo files containing a URL ===
2. The *.nfo file contains a URL of the information page to scrape.
The file can include other information (i.e. scene info), Kodi will scan through it and use a relevant URL if a match is found.

The scraper tries to match URL's to all scrapers of the content type a directory is set to. e.g. if you set the content type to movies, all movie scrapers check .nfo files for a matching URL. This means that .nfo files override the scraper setting. I.e. a directory is set to use the IMDB scraper but you have a German movie in it. Simply create an .nfo for that movie with the OFDB link in it and you are sorted!

* <code>Moviename.nfo</code> placed next to Moviename.avi where Moviename is the name of the movie file.

* <code>movie.nfo</code> if you use the "Use Foldername for Lookups" option, movie.nfo takes priority over any other .nfo files.

If you use the "Movies are in separate folders that match the movie title" [[Set Contents (Video Library)#Options After Selecting Scraper|scraper setting]] Kodi will use the first nfo file it finds in the folder (other than the .nfo files described above) and apply it to any valid video file it finds in the same folder.

=== Video .nfo files containing a mix of XML and URL ===
You can also create .nfo files that contain both XML data and an URL.
This is useful for instance, if you want the entry in your database to have another name than the one officially provided by the scraper, for the movie to sort differently or the movie to be a part of a movie set.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Sin City (Recut, Extended, Unrated)</title>
<runtime>147 min.</runtime>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Star Wars (1977 Original Theatrical Release)</title>
<runtime>121 min.</runtime>
<set>Star Wars Saga</set>
<sorttitle>Star Wars1</sorttitle>
</movie>
http://www.imdb.com/title/tt0076759/
</syntaxhighlight>

By default the xml entry is '''added''' to the scraped entry in the database and may result in some duplicates. If you want to completely override the scraped result you need to set a clear attribute for the relevant xml tag in the .nfo file.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<genre clear="true">Action</genre>
<genre>Horror</genre>
<genre>Thriller</genre>
<director clear="true">Frank Miller</director>
<director>Robert Rodriguez</director>
<director>Quentin Tarantino</director>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

Currently supported tags for the clear attribute are genre, director, studio, actor, credits and artist for Music Videos.

=== Movie sets ===

<syntaxhighlight lang="XML" enclose="div">
<movie>
<title>Hellboy - Uncut Extended</title>
<set>Hellboy Collection</set>
<sorttitle>Hellboy 1</sorttitle>
</movie>
http://www.themoviedb.org/movie/1487
</syntaxhighlight>
* Get the URL at the end by searching the movie on your favorite movie DB site (but you need a [[scraper]] for Kodi of this site) and copy the link from the address bar of the browser.
* Doing it this way has the advantage, to get all other information like cast, poster, fanart, rating, etc. automatically from the movie DB site, while being able to specify the exact title.<br />''This is especially helpful for example for the themoviedb.org, which does not recognise "Uncut", "Extended Version", etc. in the movie title.''
* '''Only single movie sets are supported'''

==== Editing the .NFO file ====
The two tags we’re interested in are shown on the [[NFO files/movies]] page, but not really explained. They are:
* '''<sorttitle>''': This tag is used to give a secondary ’sort title’ that will be used to order the movies when sorting the movies by name. The easiest way to handle this is to just use “Die Hard 1″, "Die Hard 2″, etc.
Since Kodi also remembers views for different folders, you could also just sort this folder by movie year, rather than name, and achieve the same result.
* '''<set>''': This tag is used to give a name to the set, or series, so that it can be listed in your Movies view.

For the Die Hard example we would add the following tags to each .NFO file in the movie series.
<syntaxhighlight lang="XML" enclose="div">
<sorttitle>Die Hard 1</sorttitle>
<set>Die Hard Collection</set>
</syntaxhighlight>
''Note that the sorttitle tag is an option tag that is not specific to sets. You only need it if you want your movies to sort by a different name other than their actual title. It is safe to leave it out if you would rather just use the date sort.''

=== Movie tags ===
To add a movie to one or multiple tags an [[NFO files|NFO file]] can be created and for every tag an XML tag can be added like this
<syntaxhighlight lang="XML" enclose="div">
<movie>
...
<tag>Name of the tag</tag>
...
</movie>
</syntaxhighlight>
If there's no tag with the specified name it will be automatically created and the tag will be attached to the movie. A movie can be added to multiple tags by adding it multiple times.

{{tip|See '''[[Video library tags]]'''}}
{{frodo updated}}

[[Category:Scraper]]
[[Category:Video library]]
[[Category:Manual]]

NFO files/Movies

2016-07-02T08:20:38Z

Imsodin: Add studio tag for completeness

{{mininav|[[NFO files]]}}
=== Video .nfo Files containing XML data ===
1. The *.nfo file is an XML file containing the data for inclusion in the library.

movie.nfo will override all and any .nfo files in the same folder as the media files if you use the "Use foldernames for lookups" setting. If you don't, then moviename.nfo is used.
If there is only one .nfo file in a folder, The scraper will use it for all media files in that folder. If there are multiple media files in a folder, the *.nfo should be named exactly the same as the video file it is representing (ie. '''moviename.avi''' and '''moviename.nfo''').

<section begin="stacking note" />{{note|In the case of multi-part (stacked) video '''[[file stacking]]''', name the file either '''moviename.nfo''' or '''moviename-CD1.nfo''' where the first filename is '''moviename-CD1.avi'''.}}<section end="stacking note" />

{{note|If your movie is ripped as VOB's and stored in a 'VIDEO_TS' folder, you will have to name the file 'VIDEO_TS.nfo' and place it in the same directory with the VIDEO_TS.ifo file.}}

Additionally the 'set' tag can be used to help sort movies that are [[Movie Sets|part of a series or collection]] (ie Harry Potter, James Bond films). This sort of collection tagging must be done in the .NFO file before the movie is scanned into the library.

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Who knows</title>
<originaltitle>Who knows for real</originaltitle>
<sorttitle>Who knows 1</sorttitle>
<set>Who knows trilogy</set>
<rating>6.100000</rating>
<year>2008</year>
<top250>0</top250>
<votes>50</votes>
<outline>A look at the role of the Buckeye State in the 2004 Presidential Election.</outline>
<plot>A look at the role of the Buckeye State in the 2004 Presidential Election.</plot> 
<tagline></tagline>
<runtime>90</runtime> //runtime in minutes
<thumb>http://ia.ec.imdb.com/media/imdb/01/I/25/65/31/10f.jpg</thumb>
<mpaa>Not available</mpaa>
<playcount>0</playcount>
<id>tt0432337</id>
<filenameandpath>c:\Dummy_Movie_Files\Movies\...So Goes The Nation.avi</filenameandpath>
<trailer></trailer>
<genre></genre>
<credits></credits>
<fileinfo>
<streamdetails> 
</streamdetails>
</fileinfo>
<studio>Dummy Pictures</studio>
<director>Adam Del Deo</director>
<actor>
<name>Paul Begala</name>
<role>Himself</role>
</actor>
<actor>
<name>George W. Bush</name>
<role>Himself</role>
</actor>
<actor>
<name>Mary Beth Cahill</name>
<role>Herself</role>
</actor>
<actor>
<name>Ed Gillespie</name>
<role>Himself</role>
</actor>
<actor>
<name>John Kerry</name>
<role>Himself</role>
</actor>
</movie>
</syntaxhighlight>

=== Video .nfo files containing a URL ===
2. The *.nfo file contains a URL of the information page to scrape.
The file can include other information (i.e. scene info), Kodi will scan through it and use a relevant URL if a match is found.

The scraper tries to match URL's to all scrapers of the content type a directory is set to. e.g. if you set the content type to movies, all movie scrapers check .nfo files for a matching URL. This means that .nfo files override the scraper setting. I.e. a directory is set to use the IMDB scraper but you have a German movie in it. Simply create an .nfo for that movie with the OFDB link in it and you are sorted!

* <code>Moviename.nfo</code> placed next to Moviename.avi where Moviename is the name of the movie file.

* <code>movie.nfo</code> if you use the "Use Foldername for Lookups" option, movie.nfo takes priority over any other .nfo files.

If you use the "Movies are in separate folders that match the movie title" [[Set Contents (Video Library)#Options After Selecting Scraper|scraper setting]] Kodi will use the first nfo file it finds in the folder (other than the .nfo files described above) and apply it to any valid video file it finds in the same folder.

=== Video .nfo files containing a mix of XML and URL ===
You can also create .nfo files that contain both XML data and an URL.
This is useful for instance, if you want the entry in your database to have another name than the one officially provided by the scraper, for the movie to sort differently or the movie to be a part of a movie set.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Sin City (Recut, Extended, Unrated)</title>
<runtime>147 min.</runtime>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Star Wars (1977 Original Theatrical Release)</title>
<runtime>121 min.</runtime>
<set>Star Wars Saga</set>
<sorttitle>Star Wars1</sorttitle>
</movie>
http://www.imdb.com/title/tt0076759/
</syntaxhighlight>

By default the xml entry is '''added''' to the scraped entry in the database and may result in some duplicates. If you want to completely override the scraped result you need to set a clear attribute for the relevant xml tag in the .nfo file.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<genre clear="true">Action</genre>
<genre>Horror</genre>
<genre>Thriller</genre>
<director clear="true">Frank Miller</director>
<director>Robert Rodriguez</director>
<director>Quentin Tarantino</director>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

Currently supported tags for the clear attribute are genre, director, studio, actor, credits and artist for Music Videos.

=== Movie sets ===

<syntaxhighlight lang="XML" enclose="div">
<movie>
<title>Hellboy - Uncut Extended</title>
<set>Hellboy Collection</set>
<sorttitle>Hellboy 1</sorttitle>
</movie>
http://www.themoviedb.org/movie/1487
</syntaxhighlight>
* Get the URL at the end by searching the movie on your favorite movie DB site (but you need a [[scraper]] for Kodi of this site) and copy the link from the address bar of the browser.
* Doing it this way has the advantage, to get all other information like cast, poster, fanart, rating, etc. automatically from the movie DB site, while being able to specify the exact title.<br />''This is especially helpful for example for the themoviedb.org, which does not recognise "Uncut", "Extended Version", etc. in the movie title.''
* '''Only single movie sets are supported'''

==== Editing the .NFO file ====
The two tags we’re interested in are shown on the [[NFO files/movies]] page, but not really explained. They are:
* '''<sorttitle>''': This tag is used to give a secondary ’sort title’ that will be used to order the movies when sorting the movies by name. The easiest way to handle this is to just use “Die Hard 1″, "Die Hard 2″, etc.
Since Kodi also remembers views for different folders, you could also just sort this folder by movie year, rather than name, and achieve the same result.
* '''<set>''': This tag is used to give a name to the set, or series, so that it can be listed in your Movies view.

For the Die Hard example we would add the following tags to each .NFO file in the movie series.
<syntaxhighlight lang="XML" enclose="div">
<sorttitle>Die Hard 1</sorttitle>
<set>Die Hard Collection</set>
</syntaxhighlight>
''Note that the sorttitle tag is an option tag that is not specific to sets. You only need it if you want your movies to sort by a different name other than their actual title. It is safe to leave it out if you would rather just use the date sort.''

=== Movie tags ===
To add a movie to one or multiple tags an [[NFO files|NFO file]] can be created and for every tag an XML tag can be added like this
<syntaxhighlight lang="XML" enclose="div">
<movie>
...
<tag>Name of the tag</tag>
...
</movie>
</syntaxhighlight>
If there's no tag with the specified name it will be automatically created and the tag will be attached to the movie. A movie can be added to multiple tags by adding it multiple times.

{{tip|See '''[[Video library tags]]'''}}
{{frodo updated}}

[[Category:Scraper]]
[[Category:Video library]]
[[Category:Manual]]

NFO files/Movies

2016-07-01T22:00:56Z

Imsodin: Explanation of outline and plot differences.

{{mininav|[[NFO files]]}}
=== Video .nfo Files containing XML data ===
1. The *.nfo file is an XML file containing the data for inclusion in the library.

movie.nfo will override all and any .nfo files in the same folder as the media files if you use the "Use foldernames for lookups" setting. If you don't, then moviename.nfo is used.
If there is only one .nfo file in a folder, The scraper will use it for all media files in that folder. If there are multiple media files in a folder, the *.nfo should be named exactly the same as the video file it is representing (ie. '''moviename.avi''' and '''moviename.nfo''').

<section begin="stacking note" />{{note|In the case of multi-part (stacked) video '''[[file stacking]]''', name the file either '''moviename.nfo''' or '''moviename-CD1.nfo''' where the first filename is '''moviename-CD1.avi'''.}}<section end="stacking note" />

{{note|If your movie is ripped as VOB's and stored in a 'VIDEO_TS' folder, you will have to name the file 'VIDEO_TS.nfo' and place it in the same directory with the VIDEO_TS.ifo file.}}

Additionally the 'set' tag can be used to help sort movies that are [[Movie Sets|part of a series or collection]] (ie Harry Potter, James Bond films). This sort of collection tagging must be done in the .NFO file before the movie is scanned into the library.

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Who knows</title>
<originaltitle>Who knows for real</originaltitle>
<sorttitle>Who knows 1</sorttitle>
<set>Who knows trilogy</set>
<rating>6.100000</rating>
<year>2008</year>
<top250>0</top250>
<votes>50</votes>
<outline>A look at the role of the Buckeye State in the 2004 Presidential Election.</outline>
<plot>A look at the role of the Buckeye State in the 2004 Presidential Election.</plot> 
<tagline></tagline>
<runtime>90</runtime> //runtime in minutes
<thumb>http://ia.ec.imdb.com/media/imdb/01/I/25/65/31/10f.jpg</thumb>
<mpaa>Not available</mpaa>
<playcount>0</playcount>
<id>tt0432337</id>
<filenameandpath>c:\Dummy_Movie_Files\Movies\...So Goes The Nation.avi</filenameandpath>
<trailer></trailer>
<genre></genre>
<credits></credits>
<fileinfo>
<streamdetails> 
</streamdetails>
</fileinfo>
<director>Adam Del Deo</director>
<actor>
<name>Paul Begala</name>
<role>Himself</role>
</actor>
<actor>
<name>George W. Bush</name>
<role>Himself</role>
</actor>
<actor>
<name>Mary Beth Cahill</name>
<role>Herself</role>
</actor>
<actor>
<name>Ed Gillespie</name>
<role>Himself</role>
</actor>
<actor>
<name>John Kerry</name>
<role>Himself</role>
</actor>
</movie>
</syntaxhighlight>

=== Video .nfo files containing a URL ===
2. The *.nfo file contains a URL of the information page to scrape.
The file can include other information (i.e. scene info), Kodi will scan through it and use a relevant URL if a match is found.

The scraper tries to match URL's to all scrapers of the content type a directory is set to. e.g. if you set the content type to movies, all movie scrapers check .nfo files for a matching URL. This means that .nfo files override the scraper setting. I.e. a directory is set to use the IMDB scraper but you have a German movie in it. Simply create an .nfo for that movie with the OFDB link in it and you are sorted!

* <code>Moviename.nfo</code> placed next to Moviename.avi where Moviename is the name of the movie file.

* <code>movie.nfo</code> if you use the "Use Foldername for Lookups" option, movie.nfo takes priority over any other .nfo files.

If you use the "Movies are in separate folders that match the movie title" [[Set Contents (Video Library)#Options After Selecting Scraper|scraper setting]] Kodi will use the first nfo file it finds in the folder (other than the .nfo files described above) and apply it to any valid video file it finds in the same folder.

=== Video .nfo files containing a mix of XML and URL ===
You can also create .nfo files that contain both XML data and an URL.
This is useful for instance, if you want the entry in your database to have another name than the one officially provided by the scraper, for the movie to sort differently or the movie to be a part of a movie set.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Sin City (Recut, Extended, Unrated)</title>
<runtime>147 min.</runtime>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

<syntaxhighlight lang="xml" enclose="div">
<movie>
<title>Star Wars (1977 Original Theatrical Release)</title>
<runtime>121 min.</runtime>
<set>Star Wars Saga</set>
<sorttitle>Star Wars1</sorttitle>
</movie>
http://www.imdb.com/title/tt0076759/
</syntaxhighlight>

By default the xml entry is '''added''' to the scraped entry in the database and may result in some duplicates. If you want to completely override the scraped result you need to set a clear attribute for the relevant xml tag in the .nfo file.

Example:
<syntaxhighlight lang="xml" enclose="div">
<movie>
<genre clear="true">Action</genre>
<genre>Horror</genre>
<genre>Thriller</genre>
<director clear="true">Frank Miller</director>
<director>Robert Rodriguez</director>
<director>Quentin Tarantino</director>
</movie>
http://www.imdb.com/title/tt0401792/
</syntaxhighlight>

Currently supported tags for the clear attribute are genre, director, studio, actor, credits and artist for Music Videos.

=== Movie sets ===

<syntaxhighlight lang="XML" enclose="div">
<movie>
<title>Hellboy - Uncut Extended</title>
<set>Hellboy Collection</set>
<sorttitle>Hellboy 1</sorttitle>
</movie>
http://www.themoviedb.org/movie/1487
</syntaxhighlight>
* Get the URL at the end by searching the movie on your favorite movie DB site (but you need a [[scraper]] for Kodi of this site) and copy the link from the address bar of the browser.
* Doing it this way has the advantage, to get all other information like cast, poster, fanart, rating, etc. automatically from the movie DB site, while being able to specify the exact title.<br />''This is especially helpful for example for the themoviedb.org, which does not recognise "Uncut", "Extended Version", etc. in the movie title.''
* '''Only single movie sets are supported'''

==== Editing the .NFO file ====
The two tags we’re interested in are shown on the [[NFO files/movies]] page, but not really explained. They are:
* '''<sorttitle>''': This tag is used to give a secondary ’sort title’ that will be used to order the movies when sorting the movies by name. The easiest way to handle this is to just use “Die Hard 1″, "Die Hard 2″, etc.
Since Kodi also remembers views for different folders, you could also just sort this folder by movie year, rather than name, and achieve the same result.
* '''<set>''': This tag is used to give a name to the set, or series, so that it can be listed in your Movies view.

For the Die Hard example we would add the following tags to each .NFO file in the movie series.
<syntaxhighlight lang="XML" enclose="div">
<sorttitle>Die Hard 1</sorttitle>
<set>Die Hard Collection</set>
</syntaxhighlight>
''Note that the sorttitle tag is an option tag that is not specific to sets. You only need it if you want your movies to sort by a different name other than their actual title. It is safe to leave it out if you would rather just use the date sort.''

=== Movie tags ===
To add a movie to one or multiple tags an [[NFO files|NFO file]] can be created and for every tag an XML tag can be added like this
<syntaxhighlight lang="XML" enclose="div">
<movie>
...
<tag>Name of the tag</tag>
...
</movie>
</syntaxhighlight>
If there's no tag with the specified name it will be automatically created and the tag will be attached to the movie. A movie can be added to multiple tags by adding it multiple times.

{{tip|See '''[[Video library tags]]'''}}
{{frodo updated}}

[[Category:Scraper]]
[[Category:Video library]]
[[Category:Manual]]

MySQL/Advanced notes

2016-06-26T11:52:07Z

Imsodin: Update information on multiple profiles

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
__TOC__
{{-}}
==advancedsettings.xml==
For a full listing of the advancedsettings.xml parameters, see [[advancedsettings.xml#<musicdatabase>/<videodatabase>]]

==MySQL speed-up tweaks==
For Kodi/XBMC ≤ v12 (Frodo) and/or MySQL 5.0 or lower: with MyISAM as the default storage engine, the following tweaks are necessary:<br />
[http://xbmcstuff.bossanova808.net/2011/03/summary-of-xbmc-mysql-database.html?m=1 MySQL speed-up tweaks for Kodi/XBMC] - See Comments for more information.<br />
[http://forum.kodi.tv/showthread.php?tid=212806&pid=1875330#pid1875330 More MySQL speed-up tweaks for Kodi/XBMC]<br />
<br />
For MySQL 5.5 or latest: with InnoDB as the default storage engine and/or v13 (Gotham)/Kodi+ only the following two tweaks are necessary.
=== In advancedsettings.xml: ===
Use the IP address and NOT the hostname of your MySQL server<br />
eg.: 192.168.1.105 <<IP address>> instead of \\SERVER

=== In my.cnf (my.ini for older versions): ===
The named file is located at /etc/mysql/my{{dot}}cnf<br />
1. $sudo nano /etc/mysql/my{{dot}}cnf<br />
2. Scroll down to '''[mysqld]''' section and add:<br />
# skip-name-resolve<br />
3. Press Ctrl+X, type y and hit Enter to validate changes and exit nano<br />
4. Restart your MySQL server. $sudo restart mysql

[[File:mysql.PNG|400px]]

==Automated Backup ==
=== Windows ===
This will allow you to make a regular backup of your MySQL database using the schedule of your choosing and saving the backups for however many days you choose. Recommend performing daily backups and saving for a minimum of 7 days. This will give you enough time to discover a problem with the DB and restore to a previous version that did not have problems.

To begin, go ahead and download the [http://www.7-zip.org/download.html command line version of 7zip]. We will use this to compress our MySQL dumps. Create a new folder in your C directory named KODISQLBACKUP. So you should have a C:\KODISQLBACKUP\ location now. In this location, create another new folder and name it zip. So you should now have C:\KODISQLBACKUP\zip. Extract the contents of the 7zip download to this location. Once complete you should have:
<br>
<pre>C:\KODISQLBACKUP\zip\7za.exe

C:\KODISQLBACKUP\zip\7-zip.chm

C:\KODISQLBACKUP\zip\license.txt

C:\KODISQLBACKUP\zip\readme.txt</pre>

We're going to create a down and dirty batch file to perform the actual backup, then we'll execute the batch script with the task scheduler built into Windows. For the purpose of these instructions, it is assumed that you are running MySQL 5.5 installed to the default location. If not, be sure to adjust your path(s) accordingly. It's also a good idea to save your backups to a network location to protect against local drive failure, so the paths here will reflect this. So here are the batch file contents:

<syntaxhighlight lang="winbatch" enclose="div">
:: All lines that start with 2 colons are comments, they do not affect the script itself. These comments are explanations of each command, as well as instructions for the things that you will need to edit. Pay close attention to all comments.

:: These lines do not NEED to be edited
set year=%DATE:~10,4%
set day=%DATE:~7,2%
set mnt=%DATE:~4,2%
set hr=%TIME:~0,2%
set min=%TIME:~3,2%

IF %day% LSS 10 SET day=0%day:~1,1%
IF %mnt% LSS 10 SET mnt=0%mnt:~1,1%
IF %hr% LSS 10 SET hr=0%hr:~1,1%
IF %min% LSS 10 SET min=0%min:~1,1%

set backuptime=%mnt%-%day%-%year%-%hr%-%min%

:: User name for DB - NOTE that root credentials are needed for this script.
set dbuser=root

:: User password - NOTE that the root credentials are needed for this script.
set dbpass=password

:: Path to location where you would like to save the errors log file. For simplicity, I keep mine in the same location as the backups.
set errorLogPath="\\REMOTE\KODI_Database\backups\dumperrors.txt"

:: We need to switch to the data directory to enumerate the folders
pushd "C:\ProgramData\MySQL\MySQL Server 5.5\data"

:: We will dump each database to it's own .sql so you can easily restore ONLY what is needed in the future. We're also going to skip the performance_schema db as it is not necessary.

FOR /D %%F IN (*) DO (

IF NOT [%%F]==[performance_schema] (
SET %%F=!%%F:@002d=-!
"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump.exe" --user=%dbuser% --password=%dbpass% --databases --routines --log-error=%errorLogPath% %%F > "\\REMOTE\KODI_Database\backups\%%F.%backuptime%.sql"
) ELSE (
echo Skipping DB backup for performance_schema
)
)

::Now to zip all of the .sql files in this folder and move the resulting .zip files to our network location.

"c:\KODISQLBACKUP\zip\7za.exe" a -tzip "\\REMOTE\KODI_Database\backups\FullBackup.%backuptime%.zip" "\\REMOTE\KODI_Database\backups\*.sql"

::Now we'll delete the unzipped .sql files

del "\\REMOTE\KODI_Database\backups\*.sql"

::Now we'll delete all zip files older than 30 days. You can adjust the number of days to suit your needs, simply change the -30 to whatever number of days you prefer. Be sure you enter the path to your backup location.
Forfiles -p \\REMOTE\KODI_Database\backups\ -s -m *.* -d -30 -c "cmd /c del /q @path"

popd
</syntaxhighlight>

Save this as Kodibackup.bat at C:\KODISQLBACKUP
Make ''sure'' you include the .bat at the end.

After you have edited the above batch file to reflect your paths and saved it as a batch file, all that is left is scheduling it to run. Daily backups are best, but you can use whatever frequency you are comfortable with. To do this, open up the Windows Task Scheduler.

In the Task Scheduler click on "Create Task...", NOT "Create Basic Task...". In the new task window, in the Name box put Kodi MySQL backup (or whatever name you want).

Then click on the Triggers tab, followed by the New button. Select Daily (or whatever you want) and adjust the time you would like it to run. Click OK.

Click on the Actions tab and click New. In the Program/Script box enter C:\KODISQLBACKUP\Kodibackup.bat (or whatever you named your batch file) and in the start in box enter C:\KODISQLBACKUP

Click ok, then click ok in the task window. In the main task scheduler window, right click on the task you just created and select run. If everything works as it should, you should now have a zipped backup of your database(s) in your backup location. It will now do this for you automatically.

Enjoy!

=== Linux ===
[http://sourceforge.net/projects/automysqlbackup/ AutoMySQLBackup] is a script that is designed to keep daily, weekly and monthly backups of your databases. It is very customizable and reliable. There is useful information on installing and configuring the script here: http://www.linux.com/learn/tutorials/659107-how-to-do-painless-mysql-server-backups-with-automysqlbackup.
{{note|Detailed instructions on configuring AutoMySQLBackup should probably be added to this section as the linked page above could be deleted at any time and there is little beginner friendly information available on the web.}}

==Name tag==
{{#lst:MySQL/Setting up Kodi|name tag}}

==Multiple profiles with one MySQL database==
The idea is to share information on files in the library (only scrape once) but have individual watch status for every profile. For information see the forum thread [http://forum.kodi.tv/showthread.php?tid=196821 [MYSQL<nowiki>]</nowiki> HOW-TO: 5 User XBMC] and for a setup for Kodi v16 see [http://forum.kodi.tv/showthread.php?tid=196821&pid=2280431#pid2280431 this post]. An older setup can be found at: http://forum.kodi.tv/showthread.php?tid=81095&pid=840499#pid840499

{{Isengard updated}}

Archive:HEVC

2016-06-06T11:13:43Z

Imsodin: minor typo correction

'''[[w:High Efficiency Video Coding|HEVC]]''' (High Efficiency Video Coding, sometimes called ''H.265'') is a new video compression format and is the successor of H.264. It was formalized on the 25th of November 2013 and published as [http://www.iso.org/iso/catalogue_detail.htm?csnumber=35424 ISO/IEC 23008-2:2013]. An open source HEVC decoder and encoder ([http://x265.org/ x265]) has been developed and is widely adopted.

== Support in {{kodi}} ==
Kodi v14 ([[Kodi v14 (Helix) changelog|changelog]]) now has software decoding support for HEVC. Kodi v15 ([[Kodi v15 (Isengard) changelog|changelog]]) introduced limited hardware decoding support for some devices, such as a few Android-based video decoders, for Linux on [[Amlogic]] SoCs and for Windows via DXVA. Kodi v16 ([[Kodi v16 (Jarvis) changelog|changelog]]) further improved hardware decoding on Android and Windows and introduced it via [[wikipedia:VAAPI|VAAPI]] and [[wikipedia:VDPAU|VDPAU]] API on linux. Most HTPCs do not have hardware decoding support for HEVC, so they will need a fairly powerful desktop class CPU in order to playback HEVC videos.

[[Category:Video library]]
{{Updated|16}}

Archive:HEVC

2016-06-06T11:10:44Z

Imsodin: update x265 project status

'''[[w:High Efficiency Video Coding|HEVC]]''' (High Efficiency Video Coding, sometimes called ''H.265'') is a new video compression format and is the successor of H.264. It was formalized on the 25th of November 2013 and published as [http://www.iso.org/iso/catalogue_detail.htm?csnumber=35424 ISO/IEC 23008-2:2013]. An open source HEVC decoder and encoder ([http://x265.org/ x265]) has been developed and is widely adapted.

== Support in {{kodi}} ==
Kodi v14 ([[Kodi v14 (Helix) changelog|changelog]]) now has software decoding support for HEVC. Kodi v15 ([[Kodi v15 (Isengard) changelog|changelog]]) introduced limited hardware decoding support for some devices, such as a few Android-based video decoders, for Linux on [[Amlogic]] SoCs and for Windows via DXVA. Kodi v16 ([[Kodi v16 (Jarvis) changelog|changelog]]) further improved hardware decoding on Android and Windows and introduced it via [[wikipedia:VAAPI|VAAPI]] and [[wikipedia:VDPAU|VDPAU]] API on linux. Most HTPCs do not have hardware decoding support for HEVC, so they will need a fairly powerful desktop class CPU in order to playback HEVC videos.

[[Category:Video library]]
{{Updated|16}}

Archive:HEVC

2016-06-06T11:07:58Z

Imsodin: Update information to Jarvis

'''[[w:High Efficiency Video Coding|HEVC]]''' (High Efficiency Video Coding, sometimes called ''H.265'') is a new video compression format and is the successor of H.264. It was formalized on the 25th of November 2013 and published as [http://www.iso.org/iso/catalogue_detail.htm?csnumber=35424 ISO/IEC 23008-2:2013]. Work on the open source HEVC decoder and encoder ([http://x265.org/ x265]) is still being done, but a proposed implementation of the codec has been made available.

== Support in {{kodi}} ==
Kodi v14 ([[Kodi v14 (Helix) changelog|changelog]]) now has software decoding support for HEVC. Kodi v15 ([[Kodi v15 (Isengard) changelog|changelog]]) introduced limited hardware decoding support for some devices, such as a few Android-based video decoders, for Linux on [[Amlogic]] SoCs and for Windows via DXVA. Kodi v16 ([[Kodi v16 (Jarvis) changelog|changelog]]) further improved hardware decoding on Android and Windows and introduced it via [[wikipedia:VAAPI|VAAPI]] and [[wikipedia:VDPAU|VDPAU]] API on linux. Most HTPCs do not have hardware decoding support for HEVC, so they will need a fairly powerful desktop class CPU in order to playback HEVC videos.

[[Category:Video library]]
{{Updated|16}}

Smartphone/tablet remotes

2016-06-04T23:56:50Z

Imsodin: Add information regarding ports/firewall

{{mininav|[[Remote controls]]}}
<section begin="intro" />{{Kodi}} can be controlled in several different ways, including both a physical remote control as well as using your smartphone or tablet. This page will link to both the official Team Kodi remote control apps and additional remote apps made by the community, as well as tell you how to enable smartphone/tablet app control in Kodi.<section end="intro" />

__TOC__
== Remote apps ==
<section begin="nav" />
{|
|-
| [[File:Kore now playing nexus6.png|64px|link=Category:Smartphone and tablet remotes]] || <big>'''Smartphone and tablet remote controls'''</big>
* [[Official Kodi Remote]]
* [[Android remotes]]
* [[iOS remotes]]
* [[Windows Phone remotes]]
|}<section end="nav" />

== Quick set up guide ==
{{Main|Settings/Services}}
Turn on the following settings in {{kodi}} to enable using a smartphone or tablet remote:

{{highlight|bordered=yes|[[Settings/Services#Remote control|Settings → Services → Remote control → '''Allow programs on other systems to control Kodi''' → {{color|green|'''ON'''}} ]] }}
:This setting enables the basic ability to remotely control Kodi.

{{highlight|bordered=yes|[[Settings/Services#Webserver|Settings → Services → Webserver → '''Allow control of Kodi via HTTP''' → {{color|green|'''ON'''}} ]] }}
:Many smartphone remotes also display additional library data, such as images and summaries. This setting allows that extra data to be transmitted to your remote app.
:Take note of the Port number, the Username and the Password (if any). You'll probably need to enter these in your remote app.

{{highlight|bordered=yes|[[Settings/Services#Zeroconf|Settings → Services → Zeroconf → '''Announce these services to other systems via Zeroconf''' → {{color|green|'''ON'''}} ]] }}
:This should be enabled by default already. Zeroconf makes it easier to find your Kodi install on your local network without having to know the exact IP address.

== Manually enabling remote control ==
{{See also|Web interface#Manually enabling remote control}}
{{#lst:Web interface|manual}}

== Firewall ==
If there is a firewall between the smartphone or tablet and the device running Kodi or on this device itself, you need to open two ports to enable remote control. The first one is the port of the [[Settings/Services/Webserver|http server]] which is 8080/tcp unless otherwise configured. The second port is the Kodi event port 9777/udp. Many remotes work without the second port, but have limited functionality (e.g. keyboard does not pop up automatically when required). Others like [[Yatse]] do not work at all without it.

{{updated|16}}

[[Category:Smartphone and tablet remotes|*]]
[[Category:Manual]]
[[Category:Remotes]]
[[Category:Index]]