1 * Changes up to version 3.0.2
3 Builds --without-server should work again.
5 The web interface is a bit more liberal in the cookie value syntax it
8 Clients fail more gracefully if no password is available.
10 * Changes up to version 3.0.1
12 Debian upgrades from 2.0.x should now work better.
14 * Changes up to version 3.0
16 Important! See README.upgrades when upgrading.
18 ** Platforms And Installation
20 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
21 in scripts/setup which will automate the setup after 'make install'.
25 Users are now stored in the database rather than a configuration file.
27 The server now has a built-in list of stopwords and players, so only
28 additions to these need be mentioned in the configuration file.
30 The default inter-track gap is now 0s.
32 How sound is played is now controlled via the new 'api' configuration
33 command. This also controls how the volume is set, which now works with
36 A bug in the MP3 decoder was fixed (also in 2.0.4).
40 The web interface now uses cookies to remember user identity, and allows
41 online registration of new users. Also it is no longer necessary to
42 manually specify the URL of the web interface (but you can override it
43 if you don't like the value it figures out).
45 It is possible to allow users to register via the web interface.
47 The web interface's browser support has been improved. It has been
48 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
53 A bug which would cause a crash if you attempt to rearrange the queue
54 while no track was playing has been fixed. There is a new 'deselect all
55 tracks' option, mirroring 'select all tracks.
57 * Changes up to version 2.0
61 Tracks can now have tags associated with them. See tags in disorder(1)
62 or the preferences documentation for the web interface or Disobedience.
64 The search facility knows how to limit results by tag (see search
65 documentation for any interface) as well as by word search. It is
66 possible to limit random play by tag (see required-tags and
67 prohibited-tags in disorder_config(5)).
69 Unicode support is improved. Case-folding and word breaking now follows
70 the rules given in the Unicode standard (with a bit of tailoring in the
75 There is a new client, 'Disobedience', that depends on the GTK+ library.
76 Feedback on the interface would be very welcome.
80 The "New" screen display tracks recently added to the database. From
81 here they can be played or their preferences changed.
83 Long track names are truncated so they fit better on the screen. Hover
88 DisOrder can broadcast audio over a network, allowing it to be played on
89 multiple client machines. See README.streams for details.
93 Slow file lookups are cached in the server. This should help
94 installations with large collections and/or slow platforms.
96 The 'enabled' and 'random_enabled' configuration options are now gone.
97 Instead the state survives from one run of the server to the next.
98 'disable now' is gone as well - if you want to emulate it disable
99 playing and then scratch the current track.
101 The 'pick' plugin has been abolished. All the logic formerly done there
102 is now built into the server, where it can be done much more
105 'tracklength' plugins must be explicitly specified.
107 A bug where removing a collection (from the configuration) could cause a
108 crash when random play was enabled has been fixed.
110 A new configuration option 'queue_pad' allows the number of random
111 tracks kept on the queue to be controlled.
113 There is a new utility disorder-decode which can decode OGG, MP3, WAV
114 and FLAC. The example config file uses it.
116 Database statistics are computed in a subprocess so that the main server
117 (and all clients) are not blocked for the duration.
121 There is a new command line tool called 'disorderfm' which is designed
122 for filename translation on (for instance) digital audio repositories.
123 It is not yet feature-complete. See its man page for additional
126 ** Build And Configuration
128 You can control which components are built with new --with options. See
131 options.transform and the 'transform' web option have gone, replaced
132 with a 'transform' configuration command. Both this and 'namepart' are
137 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
138 contributed in some way to this release.
140 * Changes up to version 1.5.1
144 Correct regexp for non-alpha tracks.
146 * Changes up to version 1.5
150 Regexp-based filtering of tracks (for instance as used by the initial
151 'Choose' page) now does the regexp matching in the server, limiting the
152 amount of data transferred to the web interface only to be discarded.
156 Regexp-base filtering of tracks is now available to the command line
161 New server_nice, speaker_nice and rescan_nice configuration options
162 allow independent control of process priorities.
164 Scratches are now attributed to the user who requested them.
167 A file descriptor was leaked for each track played.
168 The amount of a track played so far was not reported.
169 The speaker process could crash on underrun.
170 The server would crash if you paused a non-pause capable track.
171 Regexp matching in the file and directory list commands was not
173 Handling of variable-argument commands in the client was broken.
175 * Changes up to version 1.4
179 Raw format players are now supported. See README.upgrades and
180 README.raw for details. This allows pausing and eliminating the
183 Pausing is also supported with suitably modified standalone player
184 plugins, though none of the supplied ones are capable of this.
186 When random play is enabled the randomly picked track now appears in the
187 queue, and can be moved around the queue, removed from it, etc.
191 Switches (random play, pause, ...) are now presented as a
192 fixed-appearance switch with an adjacent state indicator.
194 The 'Manage' screen has new buttons to move tracks to the head or tail
197 You can now edit the preferences for all the tracks in an album in a
198 single screen, rather than having to visit each separately. For the
199 time being the raw preferences editing has gone; it can be reintroduced
200 on some form if there is demand. (You can still edit raw preferences
201 from the command line.)
203 Labels are now documented in options.labels rather than
208 If you tried to start up on any empty database with random play enabled
209 the server would exit with an error.
211 The server no longer risks failing if you strace its player
214 It was possible for the server to hang when a 'reconfigure' command was
215 issued. This should no longer be the case.
217 The default signal to forcibly terminate players is now SIGKILL.
221 Plugins must now declare a type word. This allows them to document
222 whether they are a standalone player or a raw-format player, and whether
223 they support pausing. They can also arrange to get setup and cleanup
224 calls in the main server. See disorder(3) for more details.
226 * Changes up to version 1.3
230 Berkeley DB 4.2 is no longer supported. Use 4.3.
234 There is a new 'authorize' command to simplify the addition of local
235 users. Please report successes as well as failures.
237 There is a new 'resolve' command to return the real track name behind an
240 The 'rescan' command no longer takes an argument.
244 The track database code has been largely rewritten to improve
247 There is a new 'lock' directive. By default the server uses a lockfile
248 to prevent multiple copies of itself running simultaneously; this can be
249 inhibited e.g. if you are using a filesystem that does not support
250 locking and are confident you can prevent concurrent running yourself.
252 Aliases for track names, constructed from trackname_display_
253 preferences, now appear in the virtual filesystem.
255 The server now executes a subprocess for the rescan operation. It also
256 runs a separate deadlock manager.
258 Standard output and standard error from subprocesses are now logged.
259 This is handy if you need to figure out why a player failed unexpectedly
260 but might lead to huge log files if you have needlessly verbose players.
264 Enable/disable buttons are now colored to reflect current state.
266 Entering numeric volume values (rather than clicking on the arrows) now
269 Connection errors are reported more gracefully.
273 Scanner plugins are now always invoked in a subprocess.
275 disorder_track_count() and disorder_track_getn() are no longer
276 available. Instead use disorder_track_random().
278 Plugins are now opened with RTLD_NOW, so link errors are detected
283 disorder-dump now insists on the input/output file being a named regular
284 file, rather than using stdin or stdout.
288 Some missing files have been added, and some notes added regarding
289 getting text encoding right.
291 * Changes up to version 1.2
293 See README.upgrades when upgrading to this version.
297 Avoid accumulating overlarge recently played list.
299 When the server was stopped, the currently playing track would not be
300 added to the recently played list. This has been fixed.
302 Reloading the 'volume' page no longer repeats the last volume-changing
305 The search facility now works properly for multiple hits within a single
310 New namepart directive replaces web interface's trackname-part. There
311 are associated changes to the protocol and clients.
313 The number of database queries per candidate match required when
314 searching has been reduced.
316 The operator can control the signal used to scratch playing tracks. The
317 default has been changed to SIGINT from SIGKILL.
319 The 'log' command now provides a formalised event log, rather than raw
320 access to the server's ordinary log output.
322 ** Web Interface Changes
326 When picking a track the client now stays on the same screen rather than
327 redirecting back to the 'Playing' screen. So that the user gets
328 feedback from their action, playing and queued tracks are now marked as
329 such in the track picking screen.
331 It is possible to revert to the old behaviour by removing the back=
332 argument from the choose.html and search.html templates (and optionally
333 the trackstate lines).
337 Non-ASCII characters are now properly supported in search terms.
341 The template syntax has been changed slightly to ignore whitespace in
346 Some formerly textual buttons are now replaced by images (with ALT text
347 reflecting the old value). The stylesheet is now a .css file (installed
348 in the same place as the images) rather than being embedded into every
351 Artist and album names in the playing and recently-played lists are now
352 links to the corresponding directory.
354 More functions are now available from the 'manage' screen.
356 The menus are now (by default) across the top of the screen instead of
357 down the side. Set the 'menu' label to 'sidebar' to restore the old
358 appearance. 'Volume' is not present in this new menu, use 'Manage'
359 instead (or edit the template).
363 tkdisorder now displays artist, album and title in the queue and
364 recently played widgets, rather than just the title (as formerly).
366 * Changes up to version 1.1
370 Corrected various problems with UTF-8 parsing.
372 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
373 'T' when grouping tracks by initial letter.
377 The list of recently played tracks is now preserved across server
380 Track IDs are more compact.
382 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
383 work now. 4.2 support will be removed in some future release.
385 Prehistoric backwards-compatibility logic removed. Only affects people
386 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
391 Tracks can be moved in the queue from the command line.
393 'disorder queue' now reports track IDs.
395 $pkgdatadir/completion.bash provides tab completion over commands and
400 New 'cooked' preferences interface saves users having to know arcane
401 details of trackname preferences and so on. Non-ASCII characters are
402 now properly supported in this context.
404 CGI arguments to the web interface are now checked for UTF-8 compliance.
~mdw / disorder / blob