Smart playlists: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 795: | Line 795: | ||
| videoaspect | | videoaspect | ||
| The value is the [http://en.wikipedia.org/wiki/Aspect_ratio_(image) aspect ratio] in the dot format without the :1, e.g. 1.85<br /> Even though "videoaspect is X" is possible to create, it '''won't''' work and will return an empty list. You ''have to'' use "less than" and/or "greater than".<br /> | | The value is the [http://en.wikipedia.org/wiki/Aspect_ratio_(image) aspect ratio] in the dot format without the :1, e.g. 1.85<br /> Even though "videoaspect is X" is possible to create, it '''won't''' work and will return an empty list. You ''have to'' use "less than" and/or "greater than".<br /> | ||
{{note| This is useless if you have a lot of video files with the black bars in its video (e.g. DVD/BD and remuxes). That'll lead to e.g. 4:3 and 2.35:1 videos also being recognized as 16:9. Even if you set the correct aspect ratio in the movie's [[ | {{note| This is useless if you have a lot of video files with the black bars in its video (e.g. DVD/BD and remuxes). That'll lead to e.g. 4:3 and 2.35:1 videos also being recognized as 16:9. Even if you set the correct aspect ratio in the movie's [[NFO_files/Movies|NFO file]] (<streamdetails><aspect>) it won't help because the software will always overwrite this data when it plays back the video file (see [https://github.com/xbmc/xbmc/pull/3701 GitHub] about this issue). For now the only solution is to do it manually using [[Video_library_tags|tags]].'' }} | ||
|- | |- | ||
|} | |} |
Revision as of 22:58, 20 July 2020
![]() |
![]() |
![]() |
![]() |
THIS PAGE IS OUTDATED:
This page or section has not been updated in a long time and may not be reliable. |
Kodi supports smart playlists for all types of media (excluding pictures), which essentially use a set of rules to limit the results from the databases. This means that to be able to create a smart playlist in the GUI, music/video must first be added to the libraries using a scraper addon or by creating NFO files. Smart playlist can be created either by using the built-in GUI smart playlist editor accessible from the Playlists section, or by creating an XML file with the extension XSP (XBMC Smart Playlist).
Creating a smart playlist in the GUI
Smart playlist for music
Music -> Playlists -> New smart playlist
Smart playlist for video
Video -> Playlists -> New smart playlist
Party Mode playlists
- See: Party Mode
Format of a smart playlist file
Smart playlists are plain text files that can be parsed by an XML reader (e.g. Visual Studio and Notepad++). Any text editor can be used to create them. They should be saved with the extension XSP and placed in your userdata directory, as there is only limited support for smart playlists saved outside of the userdata folder.
The format is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="songs"> <name>All U2 from after 1990</name> <match>all</match> <rule field="artist" operator="is"> <value>U2</value> </rule> <rule field="year" operator="greaterthan"> <value>1990</value> </rule> <limit>50</limit> <order direction="descending">playcount</order> </smartplaylist>
Types
Smart playlists can be of one of the following types:
- songs (default)
- albums
- movies
- tvshows
- episodes
- musicvideos
- mixed (audio and music videos)
<smartplaylist type="songs">
Name and Match
Basically there are two header tags, <name>
and <match>
and then a set of <rule>
tags that define the rules to use, along with an <order>
tag to allow sorting and a <limit>
tag to limit the returned results.
Note: that the tags and attributes are all case-sensitive.
The <name>
tag is the name of the playlist and the <match>
tag indicates how the <rule>
tags should be matched. If <match>all</match>
like in the above example, then only songs which satisfy all the <rule>
's will be included. If <match>one</match>
is specified, then songs that satisfy any one (or more) of the <rule>
's will be included.
<name>All U2 from after 1990</name> <match>all</match>
Rules
The <rule>
tags, of which there can be as many as you wish, have two attributes (field
and operator
) and a <value>
tag.
<rule field="artist" operator="is"> <value>U2</value> </rule>
Fields
Depending on the type of the smart playlist different field
s are available:
field
|
music | video | type | ||||||
---|---|---|---|---|---|---|---|---|---|
Name | Data type | songs | albums | artists | movies | tvshows | episodes | musicvideos | mixed |
genre | string | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
album | string | Yes | Yes | No | No | No | No | Yes | Yes |
artist | string | Yes | Yes | Yes | No | No | No | Yes | Yes |
albumartist | string | Yes | Yes | No | No | No | No | Yes | Yes |
title | string | Yes | No | No | Yes | No | No | Yes | Yes |
year | number | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
time | number | Yes | No | No | Yes | No | Yes | Yes | Yes |
tracknumber | number | Yes | No | No | No | No | No | No | Yes |
filename | string | Yes | No | No | Yes | No | Yes | Yes | Yes |
path | string | Yes | No | No | Yes | Yes | Yes | Yes | Yes |
playcount | number | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
lastplayed | date | Yes | No | No | Yes | No | Yes | Yes | Yes |
inprogress | boolean | No | No | No | Yes | Yes | Yes | No | Yes |
rating | number | Yes | Yes | No | Yes | Yes | Yes | No | Yes |
userrating | number | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
comment | string | Yes | No | No | No | No | No | No | Yes |
dateadded | date | No | No | No | Yes | No | No | No | No |
plot | string | No | No | No | Yes | Yes | Yes | Yes | Yes |
plotoutline | string | No | No | No | Yes | No | No | No | Yes |
tagline | string | No | No | No | Yes | No | No | No | Yes |
mpaarating | string | No | No | No | Yes | Yes | Yes | No | Yes |
top250 | number | No | No | No | Yes | No | No | No | Yes |
status | string | No | No | No | No | Yes | No | No | Yes |
votes | number | No | No | No | Yes | Yes | Yes | No | Yes |
director | string | No | No | No | Yes | Yes | Yes | Yes | Yes |
actor | string | No | No | No | Yes | Yes | Yes | No | Yes |
studio | string | No | No | No | Yes | Yes | Yes | Yes | Yes |
country | string | No | No | No | Yes | No | No | No | Yes |
numepisodes | number | No | No | No | No | Yes | No | No | Yes |
numwatched | number | No | No | No | No | Yes | No | No | Yes |
writers | string | No | No | No | Yes | No | Yes | No | Yes |
airdate | date | No | No | No | No | No | Yes | No | Yes |
episode | number | No | No | No | No | No | Yes | No | Yes |
season | number | No | No | No | No | No | Yes | No | Yes |
tvshow | string | No | No | No | No | Yes | Yes | No | Yes |
episodetitle | string | No | No | No | No | No | Yes | No | Yes |
review | string | No | Yes | No | No | No | No | No | Yes |
themes | string | No | Yes | No | No | No | No | No | Yes |
moods | string | No | Yes | Yes | No | No | No | No | Yes |
styles | string | No | Yes | Yes | No | No | No | No | Yes |
type | string | No | Yes | No | No | No | No | No | Yes |
label | string | No | Yes | No | No | No | No | No | Yes |
hastrailer | boolean | No | No | No | Yes | No | No | No | Yes |
videoresolution | number | No | No | No | Yes | No | Yes | Yes | Yes |
audiochannels | number | No | No | No | Yes | No | Yes | Yes | Yes |
videocodec | string | No | No | No | Yes | No | Yes | Yes | Yes |
audiocodec | string | No | No | No | Yes | No | Yes | Yes | Yes |
audiolanguage | string | No | No | No | Yes | No | Yes | Yes | Yes |
audiotrackcount[1] | number | No | No | No | Yes | No | Yes | Yes | Yes |
subtitlelanguage | string | No | No | No | Yes | No | Yes | Yes | Yes |
subtitletrackcount[2] | number | No | No | No | Yes | No | Yes | Yes | Yes |
videoaspect | number | No | No | No | Yes | No | Yes | Yes | Yes |
set | string | No | No | No | Yes | No | No | No | Yes |
tag | string | No | No | No | Yes | Yes | Yes[3] | Yes | Yes |
instruments | string | No | No | Yes | No | No | No | No | No |
biography | string | No | No | Yes | No | No | No | No | No |
born | string | No | No | Yes | No | No | No | No | No |
band formed | string | No | No | Yes | No | No | No | No | No |
disbanded | string | No | No | Yes | No | No | No | No | No |
died | string | No | No | Yes | No | No | No | No | No |
playlist | string | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Field values
field
|
value description |
---|---|
audiolanguage | A three letter ISO 639-2/B value in lowercase (usually the first three letters of the language name in English). An uppercase value will be ignored and produce an empty playlist. |
lastplayed | operator: inthelast/notinthelast value: X days/weeks/months (X being a number) |
mpaarating | Uses the MPAA ratings in the format: Rated G, Rated PG, Rated PG-13, Rated, Rated R |
subtitlelanguage | A three letter ISO 639-2/B value in lowercase (usually the first three letters of the language name in English). An uppercase value will be ignored and produce an empty playlist. |
videoaspect | The value is the aspect ratio in the dot format without the :1, e.g. 1.85 Even though "videoaspect is X" is possible to create, it won't work and will return an empty list. You have to use "less than" and/or "greater than". Note: This is useless if you have a lot of video files with the black bars in its video (e.g. DVD/BD and remuxes). That'll lead to e.g. 4:3 and 2.35:1 videos also being recognized as 16:9. Even if you set the correct aspect ratio in the movie's NFO file (<streamdetails><aspect>) it won't help because the software will always overwrite this data when it plays back the video file (see GitHub about this issue). For now the only solution is to do it manually using tags. |
Operators
The operator
attribute specifies the rule that should be used to match the parameter to the field
. All matching is done case-insensitive. The allowed operator
s are:
operator
|
Definition |
---|---|
contains | True if the field contains the parameter as a substring |
doesnotcontain | True if the field does not contain the parameter as a substring |
is | True if the field matches the parameter exactly |
isnot | True if the field does not match the parameter exactly |
startswith | True if the start of the field matches the parameter |
endswith | True if the end of the field matches the parameter |
lessthan | True if the content of the field is less than the parameter |
greaterthan | True if the content of the field is greater than the parameter |
after | True if the content of the field comes after the parameter |
before | True if the content of the field comes before the parameter |
inthelast | True if the field falls in the last range specified by the parameter. Only applicable for a date field. |
notinthelast | True if the field does not fall in the last range specified by the parameter. Only applicable for a date field. |
Limit and Order
The <limit>
tag simply takes a number of songs as it's limit. A missing limit tag, or <limit>0</limit>
will retrieve all matching songs. The <order>
tag has a direction
attribute, the values of which can be ascending
or descending
, and it's value is a field as above, or can be <order>random</order>
if you want a random ordering returned. Note that random should be used with care - it is quite slow if the returned results from the <rule>
sets is large (more than 500 items).
The above example, therefore selects all songs whose artist field is U2 and whose year field is greater than 1990, orders them by the number of times they've been played (most played first) then limits it to just 50. Thus, the top 50 songs you've played from all U2 songs published after 1990.
<limit>50</limit> <order direction="descending">playcount</order>
Grouping
Grouping was added in v13. The <group>
tag allows to group the resulting list of media items by a specific category. The final list will consist of folder nodes containing matching media items. Depending on the type of the Smart Playlist the following grouping categories exist:
field
|
music | video | |||||||
---|---|---|---|---|---|---|---|---|---|
Name | Data type | songs | albums | artists | movies | tvshows | episodes | musicvideos | mixed |
none | string | No | No | No | Yes | No | No | No | No |
genres | string | No | No | Yes | Yes | Yes | No | Yes | Yes |
years | string | No | Yes | No | Yes | Yes | No | Yes | Yes |
actors | string | No | No | No | Yes | Yes | Yes | No | No |
artists | string | No | No | No | No | No | No | Yes | Yes |
directors | string | No | No | No | Yes | Yes | Yes | Yes | Yes |
writers | string | No | No | No | Yes | No | Yes | No | No |
studios | string | No | No | No | Yes | Yes | No | Yes | Yes |
countries | string | No | No | No | Yes | No | No | No | No |
sets | string | No | No | No | Yes | No | No | No | No |
tags | string | No | No | No | Yes | Yes | No | Yes | Yes |
![]() |
NOTICE: There's an important difference between not providing a <group> tag (or providing an empty <group> tag) and setting the value of the <group> tag to none: The latter will overrule any mixed grouping that would be applied by default to a list of media items (specifically for a mixed list of movies and movie sets if the setting Group movies into sets is enabled).
|
Mixed grouping
For the sets grouping category there is support for additional so called mixed grouping. The difference to normal grouping is that the resulting list will not just be a list of grouped folders but a mix of media items and grouped folders. Mixed grouping can be controlled using the mixed attribute in the <group>
tag with a boolean value (true or false).
Combining playlists
The playlist
field
can be used to combine several playlists together. When playlists are combined, the <limit>
and <order>
tags of the included playlists are ignored; only the <order>
and <limit>
of the final playlist are used.
As a simple example, lets create a new playlist combining the "Rock Music from the 1970s" and "Recently Played Songs" playlists above, to produce a playlist with the recently played rock songs from the 1970s.
Recently played rock tracks from the 1970s
<?xml version="1.0"?> <smartplaylist type="songs"> <name>Recently played Rock Tracks from the 1970s</name> <match>all</match> <rule field="playlist" operator="is">Rock Music from the 1970s</rule> <rule field="playlist" operator="is">Recently Played Songs</rule> </smartplaylist>
Using this system allows very complex queries to be built. Note that in a single playlist, you can only match ALL of the rules, or ONE (or more) of the rules. This is basically either ANDing the conditions together, or ORing them together. You cannot mix AND with OR in a single playlist. To build up a playlist with both AND and OR operations on the rules, you use multiple playlists to group the AND operations and the OR operations, then combine them as above.
Examples
Movie examples
In progress movies
Moives that are still in progress ordered by last played.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="movies"> <name>In progress movies</name> <match>all</match> <rule field="inprogress" operator="true" /> <order direction="descending">lastplayed</order> </smartplaylist>
Last played movies (history)
Not in progress movies with a play count bigger than 0 ordered by last played.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="movies"> <name>Last played movies (history)</name> <match>all</match> <rule field="inprogress" operator="false" /> <rule field="playcount" operator="greaterthan"> <value>0</value> </rule> <order direction="descending">lastplayed</order> </smartplaylist>
One random movie
Only one movie is added to the playlist. This isn't possible to create in the GUI because the lower limit is 10 (or at least the limit needs to be edited afterward).
Even though the limit is only one you still need to set random order.
Though the difference between a playlist containing the GUI minimum 10 or edited to contain only 1 isn't significant. Pressing play on both of them will play a random movie. The "benefit" with a playlist only containing one movie is that you'll only be presented with one if you open the playlist.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="movies"> <name>Random movie</name> <match>all</match> <rule field="playcount" operator="is"> <value>0</value> </rule> <limit>1</limit> <order direction="ascending">random</order> </smartplaylist>
Movies with a specific subtitle language
Movies that contain Swedish (swe) internal subtitles.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="movies"> <name>Movies with Swedish subs</name> <match>all</match> <rule field="subtitlelanguage" operator="is"> <value>swe</value> </rule> <group>none</group> </smartplaylist>
Music examples
Recently played songs
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="songs"> <name>Recently Played Songs</name> <match>all</match> <rule field="lastplayed" operator="inthelast"> <value>2 weeks</value> </rule> <order direction="descending">lastplayed</order> </smartplaylist>
Top 100 songs
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="songs"> <name>Top 100 Songs</name> <match>all</match> <rule field="playcount" operator="greaterthan"> <value>0</value> </rule> <order direction="descending">playcount</order> <limit>100</limit> </smartplaylist>
Rock music from the 1970s
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="songs"> <name>Rock Music from the 1970s</name> <match>all</match> <rule field="genre" operator="is"> <value>Rock</value> </rule> <rule field="year" operator="greaterthan"> <value>1969</value> </rule> <rule field="year" operator="lessthan"> <value>1980</value> </rule> </smartplaylist>
TV show examples
Last played episodes (history)
Not in progress episodes and with a play count bigger than 0 from the last 6 months ordered by last played.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="episodes"> <name>Last played episodes (history)</name> <match>all</match> <rule field="lastplayed" operator="inthelast"> <value>6 months</value> </rule> <rule field="inprogress" operator="false" /> <rule field="playcount" operator="greaterthan"> <value>0</value> </rule> <order direction="descending">lastplayed</order> </smartplaylist>
In progress episodes
Episodes that are still in progress from the last 2 weeks ordered by last played.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="episodes"> <name>In progress episodes</name> <match>all</match> <rule field="lastplayed" operator="inthelast"> <value>2 weeks</value> </rule> <rule field="inprogress" operator="true" /> <order direction="descending">lastplayed</order> </smartplaylist>
Last played TV shows
TV shows that've been played in the last 3 months ordered by last played with play count 0.
The play count setting makes it so if all episodes have been watched it doesn't show up, but as soon new unplayed episodes or seasons are scraped the TV Show will show up again in the playlist.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="tvshows"> <name>Last played TV shows</name> <match>all</match> <rule field="lastplayed" operator="inthelast"> <value>3 months</value> </rule> <rule field="playcount" operator="is"> <value>0</value> </rule> <order direction="descending">lastplayed</order> </smartplaylist>
TV show with specific episode names
A playlist with The Simpsons' Treehouse of Terror episodes.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="episodes"> <name>The Simpsons - Treehouse of Horror</name> <match>all</match> <rule field="title" operator="contains"> <value>Treehouse</value> </rule> <rule field="tvshow" operator="is"> <value>The Simpsons</value> </rule> </smartplaylist>
Random unplayed episodes from a TV show
10 random episodes with a play count of 0 from The Simpsons.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="episodes"> <name>Random episodes - The Simpsons</name> <match>all</match> <rule field="tvshow" operator="is"> <value>The Simpsons</value> </rule> <rule field="playcount" operator="is"> <value>0</value> </rule> <limit>10</limit> <order direction="ascending">random</order> </smartplaylist>
Random unplayed episodes from several TV shows
10 random episodes with a play count of 0 (i.e. unplayed) from six different shows. Though as it's random this can create a list with two to ten episodes of the same show in a row.
If you specifically want to watch 6 random episodes from 6 different shows you could create playlists that are limited to 1 episode and 1 show (see One random movie example). Then you queue the 6 playlists.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <smartplaylist type="episodes"> <name>Random episodes - AAFFSS</name> <match>all</match> <rule field="tvshow" operator="is"> <value>American Dad</value> <value>Archer</value> <value>Family Guy</value> <value>Futurama</value> <value>South Park</value> <value>The Simpsons</value> </rule> <rule field="playcount" operator="is"> <value>0</value> </rule> <limit>10</limit> <order direction="ascending">random</order> </smartplaylist>