This screen displays the currently playing track (if there is one) and lists all the tracks in the queue (the track that will be played soonest being listed first.) Where possible, estimated start times are given.
Each track has a button next to it. For the currently playing track this can be used to stop playing the track before it has finished. For a track in the queue it removes the track from the queue.
Depending on the server configuration, you may be able to do this for any track, or only for tracks you submitted or that were randomly picked. See the "restrict" option in disorder_config(5) for more details.
Artist and album names are hyperlinks to the relevant locations in the Choose screen (see below).
This screen is almost identical to Playing except that it includes extra management features.
At the top of the screen are the following controls:
Below this is the same table of current and queued tracks as for the main playing screen, but with extra buttons for managing the queue. The and buttons on each track move that track around in the queue. Similarly the and buttons move each track to the head or tail of the queue. Depending on server configuration, it may be that only trusted users can move tracks around the queue.
This screen displays recently played tracks, most recent first. The button can be used to edit the details for a track; see Editing Preferences below.
The number of tracks remembered is controlled by the server configuration. See the "history" option in disorder_config(5) for more details.
This screen allows you to choose a track to be played, by navigating through the directory structure of the tracks filesystem. The following buttons appear:
|This button can be used to edit the details for a track; see Editing Preferences below.|
|This button plays all the tracks in a directory, in order. This is used to efficiently play a whole album.|
At the top appear "cooked" preferences. These can be used to edit artist, album and title fields for the track as displayed, or to set the tags for a track, or to enable or disable random play for the track.
Tags are separated by commas and can contain any other printing characters (including spaces). Leading and trailing spaces are not significant.
Random play for any given track is enabled by default, but you can use this screen to disable it for undesirable tracks.
Below this are "raw" preferences, which allow individual database fields to be modified.
To change an existing preference, edit its value and press itsbutton.
To delete an existing preference, press itsbutton.
To add a new preference, enter its name and value in the box at the bottom and press thebutton. If the preference exists already it will be overwritten.
Preferences can have any name or value but certain names have special significance:
|pick_at_random||If this preference is present and set to "0" then the track will not be picked for random play. Otherwise it may be.|
|trackname_context_part||These preferences can be used to override the filename parsing rules to find a track name part. trackname_part will be used if the full version is not present.|
context can be anything but standard values are:
|display||Displayed in a web page|
|sort||Used when sorting track names|
part can be anything too but standard values are "artist", "album" and "title", with the obvious meanings.
This screen allows you to search for keywords in track names. If you specify more than one keyword then only tracks containing all of them are listed. Results are grouped by artist, album and title.
It is possible to limit results to tracks with a particular tag, by using tag:TAG among the search terms.
Some keywords, known as "stopwords", are excluded from the search, and will never match. See the "stopword" option in disorder_config(5) for further details about this.
This screen allows you to set the playback volume, if this is enabled in the server configuration. See the "channel" and "mixer" options in disorder_config(5) for further details about this.
If you cannot play a track, or it does not appear in the database even after a rescan, check the following things:
The user the server runs as is determined by the user directive in the configuration file. The README recommends using jukebox for this purpose but it could be different locally.