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 * Changes up to version 3.0.2
26 Builds --without-server should work again.
28 The web interface is a bit more liberal in the cookie value syntax it
31 * Changes up to version 3.0.1
33 Debian upgrades from 2.0.x should now work better.
35 * Changes up to version 3.0
37 Important! See README.upgrades when upgrading.
39 ** Platforms And Installation
41 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
42 in scripts/setup which will automate the setup after 'make install'.
46 Users are now stored in the database rather than a configuration file.
48 The server now has a built-in list of stopwords and players, so only
49 additions to these need be mentioned in the configuration file.
51 The default inter-track gap is now 0s.
53 How sound is played is now controlled via the new 'api' configuration
54 command. This also controls how the volume is set, which now works with
57 A bug in the MP3 decoder was fixed (also in 2.0.4).
61 The web interface now uses cookies to remember user identity, and allows
62 online registration of new users. Also it is no longer necessary to
63 manually specify the URL of the web interface (but you can override it
64 if you don't like the value it figures out).
66 It is possible to allow users to register via the web interface.
68 The web interface's browser support has been improved. It has been
69 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
74 A bug which would cause a crash if you attempt to rearrange the queue
75 while no track was playing has been fixed. There is a new 'deselect all
76 tracks' option, mirroring 'select all tracks.
78 * Changes up to version 2.0
82 Tracks can now have tags associated with them. See tags in disorder(1)
83 or the preferences documentation for the web interface or Disobedience.
85 The search facility knows how to limit results by tag (see search
86 documentation for any interface) as well as by word search. It is
87 possible to limit random play by tag (see required-tags and
88 prohibited-tags in disorder_config(5)).
90 Unicode support is improved. Case-folding and word breaking now follows
91 the rules given in the Unicode standard (with a bit of tailoring in the
96 There is a new client, 'Disobedience', that depends on the GTK+ library.
97 Feedback on the interface would be very welcome.
101 The "New" screen display tracks recently added to the database. From
102 here they can be played or their preferences changed.
104 Long track names are truncated so they fit better on the screen. Hover
109 DisOrder can broadcast audio over a network, allowing it to be played on
110 multiple client machines. See README.streams for details.
114 Slow file lookups are cached in the server. This should help
115 installations with large collections and/or slow platforms.
117 The 'enabled' and 'random_enabled' configuration options are now gone.
118 Instead the state survives from one run of the server to the next.
119 'disable now' is gone as well - if you want to emulate it disable
120 playing and then scratch the current track.
122 The 'pick' plugin has been abolished. All the logic formerly done there
123 is now built into the server, where it can be done much more
126 'tracklength' plugins must be explicitly specified.
128 A bug where removing a collection (from the configuration) could cause a
129 crash when random play was enabled has been fixed.
131 A new configuration option 'queue_pad' allows the number of random
132 tracks kept on the queue to be controlled.
134 There is a new utility disorder-decode which can decode OGG, MP3, WAV
135 and FLAC. The example config file uses it.
137 Database statistics are computed in a subprocess so that the main server
138 (and all clients) are not blocked for the duration.
142 There is a new command line tool called 'disorderfm' which is designed
143 for filename translation on (for instance) digital audio repositories.
144 It is not yet feature-complete. See its man page for additional
147 ** Build And Configuration
149 You can control which components are built with new --with options. See
152 options.transform and the 'transform' web option have gone, replaced
153 with a 'transform' configuration command. Both this and 'namepart' are
158 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
159 contributed in some way to this release.
161 * Changes up to version 1.5.1
165 Correct regexp for non-alpha tracks.
167 * Changes up to version 1.5
171 Regexp-based filtering of tracks (for instance as used by the initial
172 'Choose' page) now does the regexp matching in the server, limiting the
173 amount of data transferred to the web interface only to be discarded.
177 Regexp-base filtering of tracks is now available to the command line
182 New server_nice, speaker_nice and rescan_nice configuration options
183 allow independent control of process priorities.
185 Scratches are now attributed to the user who requested them.
188 A file descriptor was leaked for each track played.
189 The amount of a track played so far was not reported.
190 The speaker process could crash on underrun.
191 The server would crash if you paused a non-pause capable track.
192 Regexp matching in the file and directory list commands was not
194 Handling of variable-argument commands in the client was broken.
196 * Changes up to version 1.4
200 Raw format players are now supported. See README.upgrades and
201 README.raw for details. This allows pausing and eliminating the
204 Pausing is also supported with suitably modified standalone player
205 plugins, though none of the supplied ones are capable of this.
207 When random play is enabled the randomly picked track now appears in the
208 queue, and can be moved around the queue, removed from it, etc.
212 Switches (random play, pause, ...) are now presented as a
213 fixed-appearance switch with an adjacent state indicator.
215 The 'Manage' screen has new buttons to move tracks to the head or tail
218 You can now edit the preferences for all the tracks in an album in a
219 single screen, rather than having to visit each separately. For the
220 time being the raw preferences editing has gone; it can be reintroduced
221 on some form if there is demand. (You can still edit raw preferences
222 from the command line.)
224 Labels are now documented in options.labels rather than
229 If you tried to start up on any empty database with random play enabled
230 the server would exit with an error.
232 The server no longer risks failing if you strace its player
235 It was possible for the server to hang when a 'reconfigure' command was
236 issued. This should no longer be the case.
238 The default signal to forcibly terminate players is now SIGKILL.
242 Plugins must now declare a type word. This allows them to document
243 whether they are a standalone player or a raw-format player, and whether
244 they support pausing. They can also arrange to get setup and cleanup
245 calls in the main server. See disorder(3) for more details.
247 * Changes up to version 1.3
251 Berkeley DB 4.2 is no longer supported. Use 4.3.
255 There is a new 'authorize' command to simplify the addition of local
256 users. Please report successes as well as failures.
258 There is a new 'resolve' command to return the real track name behind an
261 The 'rescan' command no longer takes an argument.
265 The track database code has been largely rewritten to improve
268 There is a new 'lock' directive. By default the server uses a lockfile
269 to prevent multiple copies of itself running simultaneously; this can be
270 inhibited e.g. if you are using a filesystem that does not support
271 locking and are confident you can prevent concurrent running yourself.
273 Aliases for track names, constructed from trackname_display_
274 preferences, now appear in the virtual filesystem.
276 The server now executes a subprocess for the rescan operation. It also
277 runs a separate deadlock manager.
279 Standard output and standard error from subprocesses are now logged.
280 This is handy if you need to figure out why a player failed unexpectedly
281 but might lead to huge log files if you have needlessly verbose players.
285 Enable/disable buttons are now colored to reflect current state.
287 Entering numeric volume values (rather than clicking on the arrows) now
290 Connection errors are reported more gracefully.
294 Scanner plugins are now always invoked in a subprocess.
296 disorder_track_count() and disorder_track_getn() are no longer
297 available. Instead use disorder_track_random().
299 Plugins are now opened with RTLD_NOW, so link errors are detected
304 disorder-dump now insists on the input/output file being a named regular
305 file, rather than using stdin or stdout.
309 Some missing files have been added, and some notes added regarding
310 getting text encoding right.
312 * Changes up to version 1.2
314 See README.upgrades when upgrading to this version.
318 Avoid accumulating overlarge recently played list.
320 When the server was stopped, the currently playing track would not be
321 added to the recently played list. This has been fixed.
323 Reloading the 'volume' page no longer repeats the last volume-changing
326 The search facility now works properly for multiple hits within a single
331 New namepart directive replaces web interface's trackname-part. There
332 are associated changes to the protocol and clients.
334 The number of database queries per candidate match required when
335 searching has been reduced.
337 The operator can control the signal used to scratch playing tracks. The
338 default has been changed to SIGINT from SIGKILL.
340 The 'log' command now provides a formalised event log, rather than raw
341 access to the server's ordinary log output.
343 ** Web Interface Changes
347 When picking a track the client now stays on the same screen rather than
348 redirecting back to the 'Playing' screen. So that the user gets
349 feedback from their action, playing and queued tracks are now marked as
350 such in the track picking screen.
352 It is possible to revert to the old behaviour by removing the back=
353 argument from the choose.html and search.html templates (and optionally
354 the trackstate lines).
358 Non-ASCII characters are now properly supported in search terms.
362 The template syntax has been changed slightly to ignore whitespace in
367 Some formerly textual buttons are now replaced by images (with ALT text
368 reflecting the old value). The stylesheet is now a .css file (installed
369 in the same place as the images) rather than being embedded into every
372 Artist and album names in the playing and recently-played lists are now
373 links to the corresponding directory.
375 More functions are now available from the 'manage' screen.
377 The menus are now (by default) across the top of the screen instead of
378 down the side. Set the 'menu' label to 'sidebar' to restore the old
379 appearance. 'Volume' is not present in this new menu, use 'Manage'
380 instead (or edit the template).
384 tkdisorder now displays artist, album and title in the queue and
385 recently played widgets, rather than just the title (as formerly).
387 * Changes up to version 1.1
391 Corrected various problems with UTF-8 parsing.
393 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
394 'T' when grouping tracks by initial letter.
398 The list of recently played tracks is now preserved across server
401 Track IDs are more compact.
403 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
404 work now. 4.2 support will be removed in some future release.
406 Prehistoric backwards-compatibility logic removed. Only affects people
407 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
412 Tracks can be moved in the queue from the command line.
414 'disorder queue' now reports track IDs.
416 $pkgdatadir/completion.bash provides tab completion over commands and
421 New 'cooked' preferences interface saves users having to know arcane
422 details of trackname preferences and so on. Non-ASCII characters are
423 now properly supported in this context.
425 CGI arguments to the web interface are now checked for UTF-8 compliance.