1 * Changes up to version 3.1
5 The 'gap' directive will no longer work. It could be restored if there
8 *** Random Track Choice
10 This has been completely rewritten to support new features:
11 - tracks in the recently-played list or in the queue are no longer
12 eligible for random choice
13 - there is a new 'weight' track preference allowing for non-uniform
14 track selection. See disorder(1) for details.
15 - there is a new configuration item replay_min defining the minimum
16 time before a played track can be picked at random. The default is
17 8 hours (which matches the earlier behaviour).
21 This has been largely rewritten. The most immediate benefits are:
22 - the search page is integrated into the choose page, and includes
23 links to parent directories
24 - if you try to do something you have insufficient rights for,
25 instead of getting an error page or nothing happening, you are
26 redirected to the login page
28 Customizers should find their lives easier: the syntax is less onerous,
29 it is possible to define macros to avoid repetition, and the
30 documentation is less monolithic.
34 There is now a new user management window. From here you can add and
35 remove users or modify their settings.
37 Relatedly, the server will only allow remote user management if you set
38 remote_userman to 'yes'.
42 scripts/setup now honors command line options, and can set up network
43 play as well as the local default sound device.
47 #2 Search results should link to directories
48 #10 Non-uniform track selection
49 #16 Cookie expiry causes user to be silently logged out and not
50 subsequently redirected to login page
51 #20 Broken aliasing rules
53 * Changes up to version 3.0.2
55 Builds --without-server should work again.
57 The web interface is a bit more liberal in the cookie value syntax it
60 Clients fail more gracefully if no password is available.
62 * Changes up to version 3.0.1
64 Debian upgrades from 2.0.x should now work better.
66 * Changes up to version 3.0
68 Important! See README.upgrades when upgrading.
70 ** Platforms And Installation
72 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
73 in scripts/setup which will automate the setup after 'make install'.
77 Users are now stored in the database rather than a configuration file.
79 The server now has a built-in list of stopwords and players, so only
80 additions to these need be mentioned in the configuration file.
82 The default inter-track gap is now 0s.
84 How sound is played is now controlled via the new 'api' configuration
85 command. This also controls how the volume is set, which now works with
88 A bug in the MP3 decoder was fixed (also in 2.0.4).
92 The web interface now uses cookies to remember user identity, and allows
93 online registration of new users. Also it is no longer necessary to
94 manually specify the URL of the web interface (but you can override it
95 if you don't like the value it figures out).
97 It is possible to allow users to register via the web interface.
99 The web interface's browser support has been improved. It has been
100 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
105 A bug which would cause a crash if you attempt to rearrange the queue
106 while no track was playing has been fixed. There is a new 'deselect all
107 tracks' option, mirroring 'select all tracks.
109 * Changes up to version 2.0
113 Tracks can now have tags associated with them. See tags in disorder(1)
114 or the preferences documentation for the web interface or Disobedience.
116 The search facility knows how to limit results by tag (see search
117 documentation for any interface) as well as by word search. It is
118 possible to limit random play by tag (see required-tags and
119 prohibited-tags in disorder_config(5)).
121 Unicode support is improved. Case-folding and word breaking now follows
122 the rules given in the Unicode standard (with a bit of tailoring in the
127 There is a new client, 'Disobedience', that depends on the GTK+ library.
128 Feedback on the interface would be very welcome.
132 The "New" screen display tracks recently added to the database. From
133 here they can be played or their preferences changed.
135 Long track names are truncated so they fit better on the screen. Hover
140 DisOrder can broadcast audio over a network, allowing it to be played on
141 multiple client machines. See README.streams for details.
145 Slow file lookups are cached in the server. This should help
146 installations with large collections and/or slow platforms.
148 The 'enabled' and 'random_enabled' configuration options are now gone.
149 Instead the state survives from one run of the server to the next.
150 'disable now' is gone as well - if you want to emulate it disable
151 playing and then scratch the current track.
153 The 'pick' plugin has been abolished. All the logic formerly done there
154 is now built into the server, where it can be done much more
157 'tracklength' plugins must be explicitly specified.
159 A bug where removing a collection (from the configuration) could cause a
160 crash when random play was enabled has been fixed.
162 A new configuration option 'queue_pad' allows the number of random
163 tracks kept on the queue to be controlled.
165 There is a new utility disorder-decode which can decode OGG, MP3, WAV
166 and FLAC. The example config file uses it.
168 Database statistics are computed in a subprocess so that the main server
169 (and all clients) are not blocked for the duration.
173 There is a new command line tool called 'disorderfm' which is designed
174 for filename translation on (for instance) digital audio repositories.
175 It is not yet feature-complete. See its man page for additional
178 ** Build And Configuration
180 You can control which components are built with new --with options. See
183 options.transform and the 'transform' web option have gone, replaced
184 with a 'transform' configuration command. Both this and 'namepart' are
189 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
190 contributed in some way to this release.
192 * Changes up to version 1.5.1
196 Correct regexp for non-alpha tracks.
198 * Changes up to version 1.5
202 Regexp-based filtering of tracks (for instance as used by the initial
203 'Choose' page) now does the regexp matching in the server, limiting the
204 amount of data transferred to the web interface only to be discarded.
208 Regexp-base filtering of tracks is now available to the command line
213 New server_nice, speaker_nice and rescan_nice configuration options
214 allow independent control of process priorities.
216 Scratches are now attributed to the user who requested them.
219 A file descriptor was leaked for each track played.
220 The amount of a track played so far was not reported.
221 The speaker process could crash on underrun.
222 The server would crash if you paused a non-pause capable track.
223 Regexp matching in the file and directory list commands was not
225 Handling of variable-argument commands in the client was broken.
227 * Changes up to version 1.4
231 Raw format players are now supported. See README.upgrades and
232 README.raw for details. This allows pausing and eliminating the
235 Pausing is also supported with suitably modified standalone player
236 plugins, though none of the supplied ones are capable of this.
238 When random play is enabled the randomly picked track now appears in the
239 queue, and can be moved around the queue, removed from it, etc.
243 Switches (random play, pause, ...) are now presented as a
244 fixed-appearance switch with an adjacent state indicator.
246 The 'Manage' screen has new buttons to move tracks to the head or tail
249 You can now edit the preferences for all the tracks in an album in a
250 single screen, rather than having to visit each separately. For the
251 time being the raw preferences editing has gone; it can be reintroduced
252 on some form if there is demand. (You can still edit raw preferences
253 from the command line.)
255 Labels are now documented in options.labels rather than
260 If you tried to start up on any empty database with random play enabled
261 the server would exit with an error.
263 The server no longer risks failing if you strace its player
266 It was possible for the server to hang when a 'reconfigure' command was
267 issued. This should no longer be the case.
269 The default signal to forcibly terminate players is now SIGKILL.
273 Plugins must now declare a type word. This allows them to document
274 whether they are a standalone player or a raw-format player, and whether
275 they support pausing. They can also arrange to get setup and cleanup
276 calls in the main server. See disorder(3) for more details.
278 * Changes up to version 1.3
282 Berkeley DB 4.2 is no longer supported. Use 4.3.
286 There is a new 'authorize' command to simplify the addition of local
287 users. Please report successes as well as failures.
289 There is a new 'resolve' command to return the real track name behind an
292 The 'rescan' command no longer takes an argument.
296 The track database code has been largely rewritten to improve
299 There is a new 'lock' directive. By default the server uses a lockfile
300 to prevent multiple copies of itself running simultaneously; this can be
301 inhibited e.g. if you are using a filesystem that does not support
302 locking and are confident you can prevent concurrent running yourself.
304 Aliases for track names, constructed from trackname_display_
305 preferences, now appear in the virtual filesystem.
307 The server now executes a subprocess for the rescan operation. It also
308 runs a separate deadlock manager.
310 Standard output and standard error from subprocesses are now logged.
311 This is handy if you need to figure out why a player failed unexpectedly
312 but might lead to huge log files if you have needlessly verbose players.
316 Enable/disable buttons are now colored to reflect current state.
318 Entering numeric volume values (rather than clicking on the arrows) now
321 Connection errors are reported more gracefully.
325 Scanner plugins are now always invoked in a subprocess.
327 disorder_track_count() and disorder_track_getn() are no longer
328 available. Instead use disorder_track_random().
330 Plugins are now opened with RTLD_NOW, so link errors are detected
335 disorder-dump now insists on the input/output file being a named regular
336 file, rather than using stdin or stdout.
340 Some missing files have been added, and some notes added regarding
341 getting text encoding right.
343 * Changes up to version 1.2
345 See README.upgrades when upgrading to this version.
349 Avoid accumulating overlarge recently played list.
351 When the server was stopped, the currently playing track would not be
352 added to the recently played list. This has been fixed.
354 Reloading the 'volume' page no longer repeats the last volume-changing
357 The search facility now works properly for multiple hits within a single
362 New namepart directive replaces web interface's trackname-part. There
363 are associated changes to the protocol and clients.
365 The number of database queries per candidate match required when
366 searching has been reduced.
368 The operator can control the signal used to scratch playing tracks. The
369 default has been changed to SIGINT from SIGKILL.
371 The 'log' command now provides a formalised event log, rather than raw
372 access to the server's ordinary log output.
374 ** Web Interface Changes
378 When picking a track the client now stays on the same screen rather than
379 redirecting back to the 'Playing' screen. So that the user gets
380 feedback from their action, playing and queued tracks are now marked as
381 such in the track picking screen.
383 It is possible to revert to the old behaviour by removing the back=
384 argument from the choose.html and search.html templates (and optionally
385 the trackstate lines).
389 Non-ASCII characters are now properly supported in search terms.
393 The template syntax has been changed slightly to ignore whitespace in
398 Some formerly textual buttons are now replaced by images (with ALT text
399 reflecting the old value). The stylesheet is now a .css file (installed
400 in the same place as the images) rather than being embedded into every
403 Artist and album names in the playing and recently-played lists are now
404 links to the corresponding directory.
406 More functions are now available from the 'manage' screen.
408 The menus are now (by default) across the top of the screen instead of
409 down the side. Set the 'menu' label to 'sidebar' to restore the old
410 appearance. 'Volume' is not present in this new menu, use 'Manage'
411 instead (or edit the template).
415 tkdisorder now displays artist, album and title in the queue and
416 recently played widgets, rather than just the title (as formerly).
418 * Changes up to version 1.1
422 Corrected various problems with UTF-8 parsing.
424 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
425 'T' when grouping tracks by initial letter.
429 The list of recently played tracks is now preserved across server
432 Track IDs are more compact.
434 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
435 work now. 4.2 support will be removed in some future release.
437 Prehistoric backwards-compatibility logic removed. Only affects people
438 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
443 Tracks can be moved in the queue from the command line.
445 'disorder queue' now reports track IDs.
447 $pkgdatadir/completion.bash provides tab completion over commands and
452 New 'cooked' preferences interface saves users having to know arcane
453 details of trackname preferences and so on. Non-ASCII characters are
454 now properly supported in this context.
456 CGI arguments to the web interface are now checked for UTF-8 compliance.