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 There is now a new user management window. From here you can add and
22 remove users or modify their settings.
24 Relatedly, the server will only allow remote user management if you set
25 remote_userman to 'yes'.
29 scripts/setup now honors command line options, and can set up network
30 play as well as the local default sound device.
32 * Changes up to version 3.0.2
34 Builds --without-server should work again.
36 The web interface is a bit more liberal in the cookie value syntax it
39 Clients fail more gracefully if no password is available.
41 * Changes up to version 3.0.1
43 Debian upgrades from 2.0.x should now work better.
45 * Changes up to version 3.0
47 Important! See README.upgrades when upgrading.
49 ** Platforms And Installation
51 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
52 in scripts/setup which will automate the setup after 'make install'.
56 Users are now stored in the database rather than a configuration file.
58 The server now has a built-in list of stopwords and players, so only
59 additions to these need be mentioned in the configuration file.
61 The default inter-track gap is now 0s.
63 How sound is played is now controlled via the new 'api' configuration
64 command. This also controls how the volume is set, which now works with
67 A bug in the MP3 decoder was fixed (also in 2.0.4).
71 The web interface now uses cookies to remember user identity, and allows
72 online registration of new users. Also it is no longer necessary to
73 manually specify the URL of the web interface (but you can override it
74 if you don't like the value it figures out).
76 It is possible to allow users to register via the web interface.
78 The web interface's browser support has been improved. It has been
79 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
84 A bug which would cause a crash if you attempt to rearrange the queue
85 while no track was playing has been fixed. There is a new 'deselect all
86 tracks' option, mirroring 'select all tracks.
88 * Changes up to version 2.0
92 Tracks can now have tags associated with them. See tags in disorder(1)
93 or the preferences documentation for the web interface or Disobedience.
95 The search facility knows how to limit results by tag (see search
96 documentation for any interface) as well as by word search. It is
97 possible to limit random play by tag (see required-tags and
98 prohibited-tags in disorder_config(5)).
100 Unicode support is improved. Case-folding and word breaking now follows
101 the rules given in the Unicode standard (with a bit of tailoring in the
106 There is a new client, 'Disobedience', that depends on the GTK+ library.
107 Feedback on the interface would be very welcome.
111 The "New" screen display tracks recently added to the database. From
112 here they can be played or their preferences changed.
114 Long track names are truncated so they fit better on the screen. Hover
119 DisOrder can broadcast audio over a network, allowing it to be played on
120 multiple client machines. See README.streams for details.
124 Slow file lookups are cached in the server. This should help
125 installations with large collections and/or slow platforms.
127 The 'enabled' and 'random_enabled' configuration options are now gone.
128 Instead the state survives from one run of the server to the next.
129 'disable now' is gone as well - if you want to emulate it disable
130 playing and then scratch the current track.
132 The 'pick' plugin has been abolished. All the logic formerly done there
133 is now built into the server, where it can be done much more
136 'tracklength' plugins must be explicitly specified.
138 A bug where removing a collection (from the configuration) could cause a
139 crash when random play was enabled has been fixed.
141 A new configuration option 'queue_pad' allows the number of random
142 tracks kept on the queue to be controlled.
144 There is a new utility disorder-decode which can decode OGG, MP3, WAV
145 and FLAC. The example config file uses it.
147 Database statistics are computed in a subprocess so that the main server
148 (and all clients) are not blocked for the duration.
152 There is a new command line tool called 'disorderfm' which is designed
153 for filename translation on (for instance) digital audio repositories.
154 It is not yet feature-complete. See its man page for additional
157 ** Build And Configuration
159 You can control which components are built with new --with options. See
162 options.transform and the 'transform' web option have gone, replaced
163 with a 'transform' configuration command. Both this and 'namepart' are
168 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
169 contributed in some way to this release.
171 * Changes up to version 1.5.1
175 Correct regexp for non-alpha tracks.
177 * Changes up to version 1.5
181 Regexp-based filtering of tracks (for instance as used by the initial
182 'Choose' page) now does the regexp matching in the server, limiting the
183 amount of data transferred to the web interface only to be discarded.
187 Regexp-base filtering of tracks is now available to the command line
192 New server_nice, speaker_nice and rescan_nice configuration options
193 allow independent control of process priorities.
195 Scratches are now attributed to the user who requested them.
198 A file descriptor was leaked for each track played.
199 The amount of a track played so far was not reported.
200 The speaker process could crash on underrun.
201 The server would crash if you paused a non-pause capable track.
202 Regexp matching in the file and directory list commands was not
204 Handling of variable-argument commands in the client was broken.
206 * Changes up to version 1.4
210 Raw format players are now supported. See README.upgrades and
211 README.raw for details. This allows pausing and eliminating the
214 Pausing is also supported with suitably modified standalone player
215 plugins, though none of the supplied ones are capable of this.
217 When random play is enabled the randomly picked track now appears in the
218 queue, and can be moved around the queue, removed from it, etc.
222 Switches (random play, pause, ...) are now presented as a
223 fixed-appearance switch with an adjacent state indicator.
225 The 'Manage' screen has new buttons to move tracks to the head or tail
228 You can now edit the preferences for all the tracks in an album in a
229 single screen, rather than having to visit each separately. For the
230 time being the raw preferences editing has gone; it can be reintroduced
231 on some form if there is demand. (You can still edit raw preferences
232 from the command line.)
234 Labels are now documented in options.labels rather than
239 If you tried to start up on any empty database with random play enabled
240 the server would exit with an error.
242 The server no longer risks failing if you strace its player
245 It was possible for the server to hang when a 'reconfigure' command was
246 issued. This should no longer be the case.
248 The default signal to forcibly terminate players is now SIGKILL.
252 Plugins must now declare a type word. This allows them to document
253 whether they are a standalone player or a raw-format player, and whether
254 they support pausing. They can also arrange to get setup and cleanup
255 calls in the main server. See disorder(3) for more details.
257 * Changes up to version 1.3
261 Berkeley DB 4.2 is no longer supported. Use 4.3.
265 There is a new 'authorize' command to simplify the addition of local
266 users. Please report successes as well as failures.
268 There is a new 'resolve' command to return the real track name behind an
271 The 'rescan' command no longer takes an argument.
275 The track database code has been largely rewritten to improve
278 There is a new 'lock' directive. By default the server uses a lockfile
279 to prevent multiple copies of itself running simultaneously; this can be
280 inhibited e.g. if you are using a filesystem that does not support
281 locking and are confident you can prevent concurrent running yourself.
283 Aliases for track names, constructed from trackname_display_
284 preferences, now appear in the virtual filesystem.
286 The server now executes a subprocess for the rescan operation. It also
287 runs a separate deadlock manager.
289 Standard output and standard error from subprocesses are now logged.
290 This is handy if you need to figure out why a player failed unexpectedly
291 but might lead to huge log files if you have needlessly verbose players.
295 Enable/disable buttons are now colored to reflect current state.
297 Entering numeric volume values (rather than clicking on the arrows) now
300 Connection errors are reported more gracefully.
304 Scanner plugins are now always invoked in a subprocess.
306 disorder_track_count() and disorder_track_getn() are no longer
307 available. Instead use disorder_track_random().
309 Plugins are now opened with RTLD_NOW, so link errors are detected
314 disorder-dump now insists on the input/output file being a named regular
315 file, rather than using stdin or stdout.
319 Some missing files have been added, and some notes added regarding
320 getting text encoding right.
322 * Changes up to version 1.2
324 See README.upgrades when upgrading to this version.
328 Avoid accumulating overlarge recently played list.
330 When the server was stopped, the currently playing track would not be
331 added to the recently played list. This has been fixed.
333 Reloading the 'volume' page no longer repeats the last volume-changing
336 The search facility now works properly for multiple hits within a single
341 New namepart directive replaces web interface's trackname-part. There
342 are associated changes to the protocol and clients.
344 The number of database queries per candidate match required when
345 searching has been reduced.
347 The operator can control the signal used to scratch playing tracks. The
348 default has been changed to SIGINT from SIGKILL.
350 The 'log' command now provides a formalised event log, rather than raw
351 access to the server's ordinary log output.
353 ** Web Interface Changes
357 When picking a track the client now stays on the same screen rather than
358 redirecting back to the 'Playing' screen. So that the user gets
359 feedback from their action, playing and queued tracks are now marked as
360 such in the track picking screen.
362 It is possible to revert to the old behaviour by removing the back=
363 argument from the choose.html and search.html templates (and optionally
364 the trackstate lines).
368 Non-ASCII characters are now properly supported in search terms.
372 The template syntax has been changed slightly to ignore whitespace in
377 Some formerly textual buttons are now replaced by images (with ALT text
378 reflecting the old value). The stylesheet is now a .css file (installed
379 in the same place as the images) rather than being embedded into every
382 Artist and album names in the playing and recently-played lists are now
383 links to the corresponding directory.
385 More functions are now available from the 'manage' screen.
387 The menus are now (by default) across the top of the screen instead of
388 down the side. Set the 'menu' label to 'sidebar' to restore the old
389 appearance. 'Volume' is not present in this new menu, use 'Manage'
390 instead (or edit the template).
394 tkdisorder now displays artist, album and title in the queue and
395 recently played widgets, rather than just the title (as formerly).
397 * Changes up to version 1.1
401 Corrected various problems with UTF-8 parsing.
403 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
404 'T' when grouping tracks by initial letter.
408 The list of recently played tracks is now preserved across server
411 Track IDs are more compact.
413 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
414 work now. 4.2 support will be removed in some future release.
416 Prehistoric backwards-compatibility logic removed. Only affects people
417 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
422 Tracks can be moved in the queue from the command line.
424 'disorder queue' now reports track IDs.
426 $pkgdatadir/completion.bash provides tab completion over commands and
431 New 'cooked' preferences interface saves users having to know arcane
432 details of trackname preferences and so on. Non-ASCII characters are
433 now properly supported in this context.
435 CGI arguments to the web interface are now checked for UTF-8 compliance.