Amarok/Manual/Playlist/AutomaticPlaylistGenerator: Difference between revisions

From KDE UserBase Wiki
No edit summary
m (Updated for 2.8)
 
(27 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[Category:Amarok]]
<languages/>
<translate>


== Automated Playlist Generator ==
=== Automatic Playlist Generator === <!--T:1-->


The ''Automated Playlist Generator (APG)'' automatically generates playlists based on constraints you set. These constraints can be set based on song data (Author, Artist, Genre) or access time (Last Time Played). There are also special constraints to determine how '''Amarok''' is going to look for songs. You will find the ''APG'' in your ''Media'' pane, <menuchoice>Playlists -> Automated Playlist Generator</menuchoice>.  
<!--T:2-->
The '''Automated Playlist Generator (APG)''' automatically generates playlists based on constraints you set. These constraints can be set based on song data (artist, genre, year) or access time (last played). There are also special constraints to determine how '''Amarok''' is going to look for songs. You will find the ''APG'' in your '''Media Sources''' pane, <menuchoice>Playlists -> Automated Playlist Generator</menuchoice>.  


=== APG Presets Toolbar ===
==== APG Presets Toolbar ==== <!--T:3-->


[[File:Menuitems.jpg|center]]
<!--T:4-->
[[File:Amarok-apg-presets-toolbar.png|center]]


This is the ''APG Presets'' toolbar. From left to right we have the following buttons:<br />
<!--T:5-->
*Add new preset: Adds a blank preset that can be modified.
This is the '''APG Presets''' toolbar. From left to right we have the following buttons:
*Edit selected preset: Opens up the ''APG Preset Editor'' window to edit the currently selected preset constraints.
*Delete selected preset: Removes the selected preset from the list; can '''NOT''' be undone.
*Import new preset: Import a preset from a .xml file. Has the potential to be malformed if edited outside '''Amarok'''; use the constraint tester.
*Export the selected preset: Export the selected preset to a .xml file that can be imported.
*Run constraint tester: Tests the selected preset for consistency.
*Run ''APG'' with selected preset: Loads ''APG'' with the selected preset and automatically generates a playlist.


=== Working with Presets ===
<!--T:21-->
* {{Plus}} Adds a blank preset that can be modified.


[[File:APGpresetsMatchAllGroup.png‎‎|400 px|center|APG Preset Editor window]]
<!--T:22-->
* {{Icon|document-properties}} Opens up the '''APG Preset Editor''' window to edit the currently selected preset constraints.


Presets are sets of rules that '''Amarok''' ''APG'' will use when generating playlists. These rules are going to be referred to as ''constraints'' from now on; every preset is determined by the constraints which create it. Groups of constraints hierarchically and logically organized are called constraint trees.
<!--T:23-->
* {{Minus}} Removes the selected preset from the list; can ''not'' be undone.


==== Constraints ====
<!--T:24-->
* {{Icon|document-import}} Import a preset from a .xml file. Has the potential to be malformed if edited outside '''Amarok'''; use the constraint tester.


Constraints are the building blocks of constraint trees. They are simple statements that the ''APG'' will use to add songs to the playlist it generates To add a constraint to the currently selected preset constraint tree use the <menuchoice>Edit selected preset</menuchoice> option from the ''APG Preset toolbar'' and click the <menuchoice>Add new</menuchoice> option on the ''APG Preset Editor'' window. Note that this will add the constraint under the selected item (constraint or constraint group).<br /><br />
<!--T:25-->
* {{Icon|document-export}} Export the selected preset to a .xml file that can be imported.
 
<!--T:27-->
* {{Icon|go-next}} Loads '''APG''' with the selected preset and automatically generates a playlist.
 
==== Working with Presets ==== <!--T:6-->
 
<!--T:7-->
[[File:APGpresetsMatchAllGroup.png|400 px|center|thumb|APG Preset Editor window]]
 
<!--T:8-->
Presets are sets of rules that '''Amarok''' '''APG''' will use when generating playlists. These rules are going to be referred to as ''constraints'' from now on; every preset is determined by the constraints which create it. Groups of constraints hierarchically and logically organized are called constraint trees.
 
===== Constraints ===== <!--T:9-->
 
<!--T:10-->
Constraints are the building blocks of constraint trees. They are simple statements that the '''APG''' will use to add songs to the playlist it generates. To add a constraint to the currently selected preset constraint tree click the {{Icon|document-properties}} button in the '''APG Preset toolbar''' and click the <menuchoice>Add new</menuchoice> option on the '''APG Preset Editor''' window. Note that this will add the constraint under the selected item (constraint or constraint group).<br /><br />
Many different kinds of constraints can be added; each works in a different way inside the tree.
Many different kinds of constraints can be added; each works in a different way inside the tree.


==== Constraint Types ====
===== Constraint Types ===== <!--T:11-->


'''Amarok''' ''APG'' supports several types of constraints:
<!--T:12-->
{|
'''Amarok''' '''APG''' supports several types of constraints:
! Constraint !! Description
{| <!--}-->
! Constraint !! Description</translate>
|-
|-
| <menuchoice>Match Tags</menuchoice> || The most important constraints, because they can be set to virtually any information regarding the file, including: artist name, album name, genre, year, last time played, bpm, sample rate and score.
<translate>
<!--T:28-->
| <menuchoice>Match Tags</menuchoice> || The most important constraints, because they can be set to virtually any information regarding the file, including: artist name, album name, genre, year, last played, and score.</translate>
|-
|-
| <menuchoice>Playlist Duration</menuchoice> || Set the running time (in HH:MM:SS format) that the playlist should have
<translate>
<!--T:29-->
| <menuchoice>Playlist Duration</menuchoice> || Set the running time (in HH:MM:SS format) that the playlist should have</translate>
|-
|-
| <menuchoice>Playlist Length</menuchoice> || Determine how many songs should be in the playlist
<translate>
<!--T:30-->
| <menuchoice>Playlist Length</menuchoice> || Determine how many songs should be in the playlist</translate>
|-
|-
| <menuchoice>Checkpoint</menuchoice> || Tell '''Amarok''' where to start and stop looking for tracks
<translate>
<!--T:31-->
| <menuchoice>Checkpoint</menuchoice> || Tell '''Amarok''' where to start and stop looking for tracks</translate>
|-
|-
<translate>
<!--T:32-->
| <menuchoice>Prevent Duplicates</menuchoice> || Prevent '''Amarok''' from selecting the same tracks, songs from the same artist, or the same album
| <menuchoice>Prevent Duplicates</menuchoice> || Prevent '''Amarok''' from selecting the same tracks, songs from the same artist, or the same album
|}
|} <!--{-->


Note that you can change how constraints work in various manners, such as setting the fuzzy-exact slider, which determines how closely the constraint is going to be followed.<br /><br />
<!--T:13-->
Another way to modify constraints that is present mainly on <menuchoice>Match Tags</menuchoice> is the option box at the left of the value to: <menuchoice>contains</menuchoice> (which will consider any songs that have the according text in their tag), <menuchoice>matches</menuchoice> (which will consider songs whose corresponding match exactly the one in the text box), <menuchoice>starts with</menuchoice> and <menuchoice>ends with</menuchoice>.<br /><br />
Note that you can change how constraints work in various manners, such as setting the fuzzy-exact slider, which determines how closely the constraint is going to be followed.
You can also edit the way value-based (such as the Length constraints and the playcount <menuchoice>Match Tag</menuchoice> constraint) behave by changing the option close to the text to settings such as <menuchoice>fewer than</menuchoice>, <menuchoice>equals</menuchoice> and <menuchoice>more than</menuchoice>.<br /><br />
Another way to change constraint behavior is to check the <menuchoice>invert</menuchoice> checkbox on them, this makes them behave the opposite way, a ''Match Tag: artist contains <name>'' becomes ''Match Tag: artist not contains <name>''.


==== Constraint Groups ====
<!--T:33-->
Another way to modify constraints that is present on <menuchoice>Match Tags</menuchoice> with a textbased tag is found in the line below the <menuchoice>Field</menuchoice> option box. In the text field to the right you write the text to be matched and in the option box at the left of the value you can select <menuchoice>contains</menuchoice> (which will consider any songs that have the according text in their tag), <menuchoice>matches</menuchoice> (which will consider songs whose corresponding tag match exactly the one in the text box), <menuchoice>starts with</menuchoice> and <menuchoice>ends with</menuchoice>.


Constraint groups can be added from the <menuchoice>Add new</menuchoice> option from the ''APG Preset Editor'' window, constraints under a group are logically linked, the same applies to groups under groups.
<!--T:34-->
Similarly, you can also edit the way value-based constraints (such as the <menuchoice>Playlist Length</menuchoice> constraints and the playcount <menuchoice>Match Tag</menuchoice> constraint) behave by changing the option close to the text to settings such as <menuchoice>fewer than</menuchoice>, <menuchoice>equals</menuchoice> and <menuchoice>more than</menuchoice>.
 
<!--T:35-->
Another way to change constraint behavior is to check the <menuchoice>invert</menuchoice> checkbox on them, this makes them behave the opposite way, a "Match Tag: artist contains '''''name'''''" becomes "Match Tag: artist not contains '''''name'''''".
 
===== Constraint Groups ===== <!--T:14-->
 
<!--T:15-->
Constraint groups can be added from the <menuchoice>Add new</menuchoice> option from the '''APG Preset Editor''' window, constraints under a group are logically linked, the same applies to groups under groups.
There are currently two kinds of constraint groups: "Match all" groups and "Match any" groups. "Match all" groups require that all the constraints under them are met by the song. "Match any" groups require that at least one of the constraints under them are met by the song. To add a constraint under a specific group highlight it on the preset editor and use the <menuchoice>Add new</menuchoice> option.
There are currently two kinds of constraint groups: "Match all" groups and "Match any" groups. "Match all" groups require that all the constraints under them are met by the song. "Match any" groups require that at least one of the constraints under them are met by the song. To add a constraint under a specific group highlight it on the preset editor and use the <menuchoice>Add new</menuchoice> option.


=== Using your Presets ===
==== Using your Presets ==== <!--T:16-->


Once you set up a preset, you just have to select it on the ''APG Presets'' panel and click the rightmost button on the toolbar, <menuchoice>Run APG with selected preset</menuchoice>. You will then have a playlist matching your criteria, like this:
<!--T:17-->
Once you set up a preset, you just have to select it on the '''APG Presets''' panel in the '''Automated Playlist Generator (APG)''' and click {{Icon|go-next}} the toolbar to run '''APG''' with the selected preset. You will then have a playlist matching your criteria, like this:


<!--T:18-->
[[Image:Generatedlist.jpeg|thumb|300 px|thumb|center|Playlist generated by the constraint tree below.]]
[[Image:Generatedlist.jpeg|thumb|300 px|thumb|center|Playlist generated by the constraint tree below.]]
[[Image:Generatingtree.jpeg|thumb|400 px|center]]
[[Image:Generatingtree.jpeg|thumb|400 px|center]]




<!--T:19-->
{{Prevnext2
{{Prevnext2
| prevpage=Amarok/Manual/Playlist/DynamicPlaylists | nextpage=Amarok/Manual/Organization/Collection/ExternalDatabase
| prevpage=Special:myLanguage/Amarok/Manual/Playlist/DynamicPlaylists | nextpage=Special:myLanguage/Amarok/Manual/Various
| prevtext=Dynamic Playlists | nexttext=External Database
| prevtext=Dynamic Playlists | nexttext=Various
| index= Amarok/Manual | indextext=Back to Menu
| index=Special:myLanguage/Amarok/Manual | indextext=Back to Menu
}}
}}
<!--T:20-->
[[Category:Amarok2.8]]
[[Category:Multimedia]]
[[Category:Tutorials]]
</translate>

Latest revision as of 16:27, 1 July 2013

Other languages:

Automatic Playlist Generator

The Automated Playlist Generator (APG) automatically generates playlists based on constraints you set. These constraints can be set based on song data (artist, genre, year) or access time (last played). There are also special constraints to determine how Amarok is going to look for songs. You will find the APG in your Media Sources pane, Playlists -> Automated Playlist Generator.

APG Presets Toolbar

This is the APG Presets toolbar. From left to right we have the following buttons:

  • Adds a blank preset that can be modified.
  • Opens up the APG Preset Editor window to edit the currently selected preset constraints.
  • Removes the selected preset from the list; can not be undone.
  • Import a preset from a .xml file. Has the potential to be malformed if edited outside Amarok; use the constraint tester.
  • Export the selected preset to a .xml file that can be imported.
  • Loads APG with the selected preset and automatically generates a playlist.

Working with Presets

APG Preset Editor window

Presets are sets of rules that Amarok APG will use when generating playlists. These rules are going to be referred to as constraints from now on; every preset is determined by the constraints which create it. Groups of constraints hierarchically and logically organized are called constraint trees.

Constraints

Constraints are the building blocks of constraint trees. They are simple statements that the APG will use to add songs to the playlist it generates. To add a constraint to the currently selected preset constraint tree click the button in the APG Preset toolbar and click the Add new option on the APG Preset Editor window. Note that this will add the constraint under the selected item (constraint or constraint group).

Many different kinds of constraints can be added; each works in a different way inside the tree.

Constraint Types

Amarok APG supports several types of constraints:

Constraint Description
Match Tags The most important constraints, because they can be set to virtually any information regarding the file, including: artist name, album name, genre, year, last played, and score.
Playlist Duration Set the running time (in HH:MM:SS format) that the playlist should have
Playlist Length Determine how many songs should be in the playlist
Checkpoint Tell Amarok where to start and stop looking for tracks
Prevent Duplicates Prevent Amarok from selecting the same tracks, songs from the same artist, or the same album

Note that you can change how constraints work in various manners, such as setting the fuzzy-exact slider, which determines how closely the constraint is going to be followed.

Another way to modify constraints that is present on Match Tags with a textbased tag is found in the line below the Field option box. In the text field to the right you write the text to be matched and in the option box at the left of the value you can select contains (which will consider any songs that have the according text in their tag), matches (which will consider songs whose corresponding tag match exactly the one in the text box), starts with and ends with.

Similarly, you can also edit the way value-based constraints (such as the Playlist Length constraints and the playcount Match Tag constraint) behave by changing the option close to the text to settings such as fewer than, equals and more than.

Another way to change constraint behavior is to check the invert checkbox on them, this makes them behave the opposite way, a "Match Tag: artist contains name" becomes "Match Tag: artist not contains name".

Constraint Groups

Constraint groups can be added from the Add new option from the APG Preset Editor window, constraints under a group are logically linked, the same applies to groups under groups. There are currently two kinds of constraint groups: "Match all" groups and "Match any" groups. "Match all" groups require that all the constraints under them are met by the song. "Match any" groups require that at least one of the constraints under them are met by the song. To add a constraint under a specific group highlight it on the preset editor and use the Add new option.

Using your Presets

Once you set up a preset, you just have to select it on the APG Presets panel in the Automated Playlist Generator (APG) and click the toolbar to run APG with the selected preset. You will then have a playlist matching your criteria, like this:

Playlist generated by the constraint tree below.