1 * Changes up to version 3.1
5 The 'gap' directive will no longer work. It could be restored if there
10 It is now possible to schedule events to occur in the future. Currently
11 the supported actions are playing a specific track, and changing a
12 global preference (thus allowing e.g. random play to be turned on or
13 off). See the schedule-* commands described in disorder(1).
15 *** Random Track Choice
17 This has been completely rewritten to support new features:
18 - tracks in the recently-played list or in the queue are no longer
19 eligible for random choice
20 - there is a new 'weight' track preference allowing for non-uniform
21 track selection. See disorder(1) for details.
22 - there is a new configuration item replay_min defining the minimum
23 time before a played track can be picked at random. The default is
24 8 hours (which matches the earlier behaviour).
25 - recently added tracks are biased up; see new_bias and new_bias_age
26 in disorder_config(5).
30 This has been largely rewritten. The most immediate benefits are:
31 - the search page is integrated into the choose page, and includes
32 links to parent directories
33 - if you try to do something you have insufficient rights for,
34 instead of getting an error page or nothing happening, you are
35 redirected to the login page
37 Customizers should find their lives easier: the syntax is less onerous,
38 it is possible to define macros to avoid repetition, and the
39 documentation is less monolithic.
43 There is now a new user management window. From here you can add and
44 remove users or modify their settings.
46 Relatedly, the server will only allow remote user management if you set
47 remote_userman to 'yes'.
51 scripts/setup now honors command line options, and can set up network
52 play as well as the local default sound device.
56 #2 Search results should link to directories
57 #6 Schedule tracks for a particular time
58 #10 Non-uniform track selection
59 #11 Bias random selection to newly added tracks
60 #13 Default encoding for debian setup scripts
61 #16 Cookie expiry causes user to be silently logged out and not
62 subsequently redirected to login page
63 #20 Broken aliasing rules
65 * Changes up to version 3.0.2
67 Builds --without-server should work again.
69 The web interface is a bit more liberal in the cookie value syntax it
72 Clients fail more gracefully if no password is available.
74 * Changes up to version 3.0.1
76 Debian upgrades from 2.0.x should now work better.
78 * Changes up to version 3.0
80 Important! See README.upgrades when upgrading.
82 ** Platforms And Installation
84 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
85 in scripts/setup which will automate the setup after 'make install'.
89 Users are now stored in the database rather than a configuration file.
91 The server now has a built-in list of stopwords and players, so only
92 additions to these need be mentioned in the configuration file.
94 The default inter-track gap is now 0s.
96 How sound is played is now controlled via the new 'api' configuration
97 command. This also controls how the volume is set, which now works with
100 A bug in the MP3 decoder was fixed (also in 2.0.4).
104 The web interface now uses cookies to remember user identity, and allows
105 online registration of new users. Also it is no longer necessary to
106 manually specify the URL of the web interface (but you can override it
107 if you don't like the value it figures out).
109 It is possible to allow users to register via the web interface.
111 The web interface's browser support has been improved. It has been
112 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
117 A bug which would cause a crash if you attempt to rearrange the queue
118 while no track was playing has been fixed. There is a new 'deselect all
119 tracks' option, mirroring 'select all tracks.
121 * Changes up to version 2.0
125 Tracks can now have tags associated with them. See tags in disorder(1)
126 or the preferences documentation for the web interface or Disobedience.
128 The search facility knows how to limit results by tag (see search
129 documentation for any interface) as well as by word search. It is
130 possible to limit random play by tag (see required-tags and
131 prohibited-tags in disorder_config(5)).
133 Unicode support is improved. Case-folding and word breaking now follows
134 the rules given in the Unicode standard (with a bit of tailoring in the
139 There is a new client, 'Disobedience', that depends on the GTK+ library.
140 Feedback on the interface would be very welcome.
144 The "New" screen display tracks recently added to the database. From
145 here they can be played or their preferences changed.
147 Long track names are truncated so they fit better on the screen. Hover
152 DisOrder can broadcast audio over a network, allowing it to be played on
153 multiple client machines. See README.streams for details.
157 Slow file lookups are cached in the server. This should help
158 installations with large collections and/or slow platforms.
160 The 'enabled' and 'random_enabled' configuration options are now gone.
161 Instead the state survives from one run of the server to the next.
162 'disable now' is gone as well - if you want to emulate it disable
163 playing and then scratch the current track.
165 The 'pick' plugin has been abolished. All the logic formerly done there
166 is now built into the server, where it can be done much more
169 'tracklength' plugins must be explicitly specified.
171 A bug where removing a collection (from the configuration) could cause a
172 crash when random play was enabled has been fixed.
174 A new configuration option 'queue_pad' allows the number of random
175 tracks kept on the queue to be controlled.
177 There is a new utility disorder-decode which can decode OGG, MP3, WAV
178 and FLAC. The example config file uses it.
180 Database statistics are computed in a subprocess so that the main server
181 (and all clients) are not blocked for the duration.
185 There is a new command line tool called 'disorderfm' which is designed
186 for filename translation on (for instance) digital audio repositories.
187 It is not yet feature-complete. See its man page for additional
190 ** Build And Configuration
192 You can control which components are built with new --with options. See
195 options.transform and the 'transform' web option have gone, replaced
196 with a 'transform' configuration command. Both this and 'namepart' are
201 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
202 contributed in some way to this release.
204 * Changes up to version 1.5.1
208 Correct regexp for non-alpha tracks.
210 * Changes up to version 1.5
214 Regexp-based filtering of tracks (for instance as used by the initial
215 'Choose' page) now does the regexp matching in the server, limiting the
216 amount of data transferred to the web interface only to be discarded.
220 Regexp-base filtering of tracks is now available to the command line
225 New server_nice, speaker_nice and rescan_nice configuration options
226 allow independent control of process priorities.
228 Scratches are now attributed to the user who requested them.
231 A file descriptor was leaked for each track played.
232 The amount of a track played so far was not reported.
233 The speaker process could crash on underrun.
234 The server would crash if you paused a non-pause capable track.
235 Regexp matching in the file and directory list commands was not
237 Handling of variable-argument commands in the client was broken.
239 * Changes up to version 1.4
243 Raw format players are now supported. See README.upgrades and
244 README.raw for details. This allows pausing and eliminating the
247 Pausing is also supported with suitably modified standalone player
248 plugins, though none of the supplied ones are capable of this.
250 When random play is enabled the randomly picked track now appears in the
251 queue, and can be moved around the queue, removed from it, etc.
255 Switches (random play, pause, ...) are now presented as a
256 fixed-appearance switch with an adjacent state indicator.
258 The 'Manage' screen has new buttons to move tracks to the head or tail
261 You can now edit the preferences for all the tracks in an album in a
262 single screen, rather than having to visit each separately. For the
263 time being the raw preferences editing has gone; it can be reintroduced
264 on some form if there is demand. (You can still edit raw preferences
265 from the command line.)
267 Labels are now documented in options.labels rather than
272 If you tried to start up on any empty database with random play enabled
273 the server would exit with an error.
275 The server no longer risks failing if you strace its player
278 It was possible for the server to hang when a 'reconfigure' command was
279 issued. This should no longer be the case.
281 The default signal to forcibly terminate players is now SIGKILL.
285 Plugins must now declare a type word. This allows them to document
286 whether they are a standalone player or a raw-format player, and whether
287 they support pausing. They can also arrange to get setup and cleanup
288 calls in the main server. See disorder(3) for more details.
290 * Changes up to version 1.3
294 Berkeley DB 4.2 is no longer supported. Use 4.3.
298 There is a new 'authorize' command to simplify the addition of local
299 users. Please report successes as well as failures.
301 There is a new 'resolve' command to return the real track name behind an
304 The 'rescan' command no longer takes an argument.
308 The track database code has been largely rewritten to improve
311 There is a new 'lock' directive. By default the server uses a lockfile
312 to prevent multiple copies of itself running simultaneously; this can be
313 inhibited e.g. if you are using a filesystem that does not support
314 locking and are confident you can prevent concurrent running yourself.
316 Aliases for track names, constructed from trackname_display_
317 preferences, now appear in the virtual filesystem.
319 The server now executes a subprocess for the rescan operation. It also
320 runs a separate deadlock manager.
322 Standard output and standard error from subprocesses are now logged.
323 This is handy if you need to figure out why a player failed unexpectedly
324 but might lead to huge log files if you have needlessly verbose players.
328 Enable/disable buttons are now colored to reflect current state.
330 Entering numeric volume values (rather than clicking on the arrows) now
333 Connection errors are reported more gracefully.
337 Scanner plugins are now always invoked in a subprocess.
339 disorder_track_count() and disorder_track_getn() are no longer
340 available. Instead use disorder_track_random().
342 Plugins are now opened with RTLD_NOW, so link errors are detected
347 disorder-dump now insists on the input/output file being a named regular
348 file, rather than using stdin or stdout.
352 Some missing files have been added, and some notes added regarding
353 getting text encoding right.
355 * Changes up to version 1.2
357 See README.upgrades when upgrading to this version.
361 Avoid accumulating overlarge recently played list.
363 When the server was stopped, the currently playing track would not be
364 added to the recently played list. This has been fixed.
366 Reloading the 'volume' page no longer repeats the last volume-changing
369 The search facility now works properly for multiple hits within a single
374 New namepart directive replaces web interface's trackname-part. There
375 are associated changes to the protocol and clients.
377 The number of database queries per candidate match required when
378 searching has been reduced.
380 The operator can control the signal used to scratch playing tracks. The
381 default has been changed to SIGINT from SIGKILL.
383 The 'log' command now provides a formalised event log, rather than raw
384 access to the server's ordinary log output.
386 ** Web Interface Changes
390 When picking a track the client now stays on the same screen rather than
391 redirecting back to the 'Playing' screen. So that the user gets
392 feedback from their action, playing and queued tracks are now marked as
393 such in the track picking screen.
395 It is possible to revert to the old behaviour by removing the back=
396 argument from the choose.html and search.html templates (and optionally
397 the trackstate lines).
401 Non-ASCII characters are now properly supported in search terms.
405 The template syntax has been changed slightly to ignore whitespace in
410 Some formerly textual buttons are now replaced by images (with ALT text
411 reflecting the old value). The stylesheet is now a .css file (installed
412 in the same place as the images) rather than being embedded into every
415 Artist and album names in the playing and recently-played lists are now
416 links to the corresponding directory.
418 More functions are now available from the 'manage' screen.
420 The menus are now (by default) across the top of the screen instead of
421 down the side. Set the 'menu' label to 'sidebar' to restore the old
422 appearance. 'Volume' is not present in this new menu, use 'Manage'
423 instead (or edit the template).
427 tkdisorder now displays artist, album and title in the queue and
428 recently played widgets, rather than just the title (as formerly).
430 * Changes up to version 1.1
434 Corrected various problems with UTF-8 parsing.
436 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
437 'T' when grouping tracks by initial letter.
441 The list of recently played tracks is now preserved across server
444 Track IDs are more compact.
446 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
447 work now. 4.2 support will be removed in some future release.
449 Prehistoric backwards-compatibility logic removed. Only affects people
450 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
455 Tracks can be moved in the queue from the command line.
457 'disorder queue' now reports track IDs.
459 $pkgdatadir/completion.bash provides tab completion over commands and
464 New 'cooked' preferences interface saves users having to know arcane
465 details of trackname preferences and so on. Non-ASCII characters are
466 now properly supported in this context.
468 CGI arguments to the web interface are now checked for UTF-8 compliance.