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