</refsect2>
<refsect2 id="tags">
<title>Tags section</title>
- <para>Tags plugin's configuration. There is no default configuration for this plugin, it does not work out of the box.</para>
- <para>
- This plugin permits offline autoqueuing based on files tags only. Supported tags are
- <option>'comment'</option>, <option>'date'</option>, <option>'genre'</option>, <option>'label'</option> and
- <option>'originaldate'</option>. It currently supports single track queuing only, no album mode for this plugin.
- </para>
- <para>
- In addition to supported tags above you can use an MPD filter. Please refer to MPD protocol documentation for more.
- </para>
- <para>
- All entries in this section are ANDed as a single MPD filter to look for titles
- in the library. Moreover, with tags, comma separated values are also ANDed.<sbr />
+ <para>Tags plugin's configuration. There is no default configuration for this plugin,
+ it does not work out of the box.</para>
+ <para> This plugin permits offline autoqueuing based on files tags only. Supported tags are
+ <option>'comment'</option>, <option>'date'</option>, <option>'genre'</option>,
+ <option>'label'</option> and <option>'originaldate'</option>. It currently
+ supports single track queuing only, no album mode for this plugin.</para>
+ <para>In addition to supported tags above you can use an MPD filter. Please refer to
+ MPD protocol documentation for more.</para>
+ <para>All entries in this section are ANDed as a single MPD filter to look for titles
+ in the library. Moreover, with tags, comma separated values are also ORed.<sbr />
For instance setting "<option>genre=rock</option>" and
"<option>date=1982,1983,1984,1985,1986,1987,1988,1989</option>"
will end up looking for track tagged with genre <option>rock</option>
and date within 1985 through 1990.<sbr />
Using an MPD filter to replace <option>date</option> you can achieve
the same with the following setting: "<option>genre=rock</option>" and
- "<option>filter=(date =~ '198[2-9]')</option>" (provided your MPD server
+ "<option>filter=(date =~ '198[2-9]+')</option>" (provided your MPD server
was compiled with libpcre).
</para>
<varlistentry> <!-- tags -->
<para>&dhpackage; tries preferably to chose among unplayed artists or
at least not recently played artist.</para>
<variablelist>
- <varlistentry>
- <term><option>track</option></term>
- <listitem>
-
<para>Queue a similar track chosen at random from a similar artist.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>top</option></term>
- <listitem>
-
<para>Queue a track from a similar artist, chosen among
- "top tracks" according to last.fm data mining.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>album</option></term>
- <listitem>
-
<para>Queue a whole album chosen at random from a similar artist.</para>
-
<para><emphasis>Nota Bene:</emphasis><sbr /> Due to the
- track point of view of database build upon tracks tags
- an album lookup for a specific artist will return
- albums as soon as this artist appears in a single track
- of the album.<sbr />
- For instance looking for album from "The Velvet
- Underground" will fetch "Last Days" and "Juno" OSTs
- because the band appears on the soundtrack of these two
- movies.<sbr />
- A solution is for you to set AlbumArtists tag to
- something different than the actual artist of the
- track. For compilations, OSTs etc. a strong convention
- is to use "Various Artists" for this tag.</para>
-
<para>&dhpackage; is currently looking for AlbumArtists tags
- and avoid album where this tag is set with "Various
- Artists". If a single track within an album is found
- with AlbumArtists:"Various Artists" the complete album
- is skipped and won't be queued.</para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term><option>track</option></term>
+ <listitem>
+ <para>Queue a similar track chosen at random from a similar artist.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>top</option></term>
+ <listitem>
+ <para>Queue a track from a similar artist, chosen among
+ "top tracks" according to last.fm data mining.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>album</option></term>
+ <listitem>
+ <para>Queue a whole album chosen at random from a similar artist.</para>
+ <para><emphasis>Nota Bene:</emphasis><sbr /> Due to the
+ track point of view of database build upon tracks tags
+ an album lookup for a specific artist will return
+ albums as soon as this artist appears in a single track
+ of the album.<sbr />
+ For instance looking for album from "The Velvet
+ Underground" will fetch "Last Days" and "Juno" OSTs
+ because the band appears on the soundtrack of these two
+ movies.<sbr />
+ A solution is for you to set AlbumArtists tag to
+ something different than the actual artist of the
+ track. For compilations, OSTs etc. a strong convention
+ is to use "Various Artists" for this tag.</para>
+ <para>&dhpackage; is currently looking for AlbumArtists tags
+ and avoid album where this tag is set with "Various
+ Artists". If a single track within an album is found
+ with AlbumArtists:"Various Artists" the complete album
+ is skipped and won't be queued.</para>
+ </listitem>
+ </varlistentry>
</variablelist>
</refsect1>
<xi:include href="files.xml" />
home / dev / repositories / mpd-sima.git / blobdiff