1 * Changes up to version 2.1
3 ** Platforms And Installation
5 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
6 in scripts/setup which will automate the setup after 'make install'.
10 Users are now stored in the database rather than a configuration file.
12 The server now has a built-in list of stopwords and players, so only
13 additions to these need be mentioned in the configuration file.
15 The default inter-track gap is now 0s.
17 How sound is played is now controlled via the new 'api' configuration
18 command. This also controls how the volume is set, which now works with
23 The web interface now uses cookies to remember user identity, and allows
24 online registration of new users. Also it is no longer necessary to
25 manually specify the URL of the web interface (but you can override it
26 if you don't like the value it figures out).
28 It is possible to allow users to register via the web interface.
30 The web interface's browser support has been improved. It has been
31 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
34 * Changes up to version 2.0
38 Tracks can now have tags associated with them. See tags in disorder(1)
39 or the preferences documentation for the web interface or Disobedience.
41 The search facility knows how to limit results by tag (see search
42 documentation for any interface) as well as by word search. It is
43 possible to limit random play by tag (see required-tags and
44 prohibited-tags in disorder_config(5)).
46 Unicode support is improved. Case-folding and word breaking now follows
47 the rules given in the Unicode standard (with a bit of tailoring in the
52 There is a new client, 'Disobedience', that depends on the GTK+ library.
53 Feedback on the interface would be very welcome.
57 The "New" screen display tracks recently added to the database. From
58 here they can be played or their preferences changed.
60 Long track names are truncated so they fit better on the screen. Hover
65 DisOrder can broadcast audio over a network, allowing it to be played on
66 multiple client machines. See README.streams for details.
70 Slow file lookups are cached in the server. This should help
71 installations with large collections and/or slow platforms.
73 The 'enabled' and 'random_enabled' configuration options are now gone.
74 Instead the state survives from one run of the server to the next.
75 'disable now' is gone as well - if you want to emulate it disable
76 playing and then scratch the current track.
78 The 'pick' plugin has been abolished. All the logic formerly done there
79 is now built into the server, where it can be done much more
82 'tracklength' plugins must be explicitly specified.
84 A bug where removing a collection (from the configuration) could cause a
85 crash when random play was enabled has been fixed.
87 A new configuration option 'queue_pad' allows the number of random
88 tracks kept on the queue to be controlled.
90 There is a new utility disorder-decode which can decode OGG, MP3, WAV
91 and FLAC. The example config file uses it.
93 Database statistics are computed in a subprocess so that the main server
94 (and all clients) are not blocked for the duration.
98 There is a new command line tool called 'disorderfm' which is designed
99 for filename translation on (for instance) digital audio repositories.
100 It is not yet feature-complete. See its man page for additional
103 ** Build And Configuration
105 You can control which components are built with new --with options. See
108 options.transform and the 'transform' web option have gone, replaced
109 with a 'transform' configuration command. Both this and 'namepart' are
114 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
115 contributed in some way to this release.
117 * Changes up to version 1.5.1
121 Correct regexp for non-alpha tracks.
123 * Changes up to version 1.5
127 Regexp-based filtering of tracks (for instance as used by the initial
128 'Choose' page) now does the regexp matching in the server, limiting the
129 amount of data transferred to the web interface only to be discarded.
133 Regexp-base filtering of tracks is now available to the command line
138 New server_nice, speaker_nice and rescan_nice configuration options
139 allow independent control of process priorities.
141 Scratches are now attributed to the user who requested them.
144 A file descriptor was leaked for each track played.
145 The amount of a track played so far was not reported.
146 The speaker process could crash on underrun.
147 The server would crash if you paused a non-pause capable track.
148 Regexp matching in the file and directory list commands was not
150 Handling of variable-argument commands in the client was broken.
152 * Changes up to version 1.4
156 Raw format players are now supported. See README.upgrades and
157 README.raw for details. This allows pausing and eliminating the
160 Pausing is also supported with suitably modified standalone player
161 plugins, though none of the supplied ones are capable of this.
163 When random play is enabled the randomly picked track now appears in the
164 queue, and can be moved around the queue, removed from it, etc.
168 Switches (random play, pause, ...) are now presented as a
169 fixed-appearance switch with an adjacent state indicator.
171 The 'Manage' screen has new buttons to move tracks to the head or tail
174 You can now edit the preferences for all the tracks in an album in a
175 single screen, rather than having to visit each separately. For the
176 time being the raw preferences editing has gone; it can be reintroduced
177 on some form if there is demand. (You can still edit raw preferences
178 from the command line.)
180 Labels are now documented in options.labels rather than
185 If you tried to start up on any empty database with random play enabled
186 the server would exit with an error.
188 The server no longer risks failing if you strace its player
191 It was possible for the server to hang when a 'reconfigure' command was
192 issued. This should no longer be the case.
194 The default signal to forcibly terminate players is now SIGKILL.
198 Plugins must now declare a type word. This allows them to document
199 whether they are a standalone player or a raw-format player, and whether
200 they support pausing. They can also arrange to get setup and cleanup
201 calls in the main server. See disorder(3) for more details.
203 * Changes up to version 1.3
207 Berkeley DB 4.2 is no longer supported. Use 4.3.
211 There is a new 'authorize' command to simplify the addition of local
212 users. Please report successes as well as failures.
214 There is a new 'resolve' command to return the real track name behind an
217 The 'rescan' command no longer takes an argument.
221 The track database code has been largely rewritten to improve
224 There is a new 'lock' directive. By default the server uses a lockfile
225 to prevent multiple copies of itself running simultaneously; this can be
226 inhibited e.g. if you are using a filesystem that does not support
227 locking and are confident you can prevent concurrent running yourself.
229 Aliases for track names, constructed from trackname_display_
230 preferences, now appear in the virtual filesystem.
232 The server now executes a subprocess for the rescan operation. It also
233 runs a separate deadlock manager.
235 Standard output and standard error from subprocesses are now logged.
236 This is handy if you need to figure out why a player failed unexpectedly
237 but might lead to huge log files if you have needlessly verbose players.
241 Enable/disable buttons are now colored to reflect current state.
243 Entering numeric volume values (rather than clicking on the arrows) now
246 Connection errors are reported more gracefuly.
250 Scanner plugins are now always invoked in a subprocess.
252 disorder_track_count() and disorder_track_getn() are no longer
253 available. Instead use disorder_track_random().
255 Plugins are now opened with RTLD_NOW, so link errors are detected
260 disorder-dump now insists on the input/output file being a named regular
261 file, rather than using stdin or stdout.
265 Some missing files have been added, and some notes added regarding
266 getting text encoding right.
268 * Changes up to version 1.2
270 See README.upgrades when upgrading to this version.
274 Avoid accumulating overlarge recently played list.
276 When the server was stopped, the currently playing track would not be
277 added to the recently played list. This has been fixed.
279 Reloading the 'volume' page no longer repeats the last volume-changing
282 The search facility now works properly for multiple hits within a single
287 New namepart directive replaces web interface's trackname-part. There
288 are associated changes to the protocol and clients.
290 The number of database queries per candidate match required when
291 searching has been reduced.
293 The operator can control the signal used to scratch playing tracks. The
294 default has been changed to SIGINT from SIGKILL.
296 The 'log' command now provides a formalised event log, rather than raw
297 access to the server's ordinary log output.
299 ** Web Interface Changes
303 When picking a track the client now stays on the same screen rather than
304 redirecting back to the 'Playing' screen. So that the user gets
305 feedback from their action, playing and queued tracks are now marked as
306 such in the track picking screen.
308 It is possible to revert to the old behaviour by removing the back=
309 argument from the choose.html and search.html templates (and optionally
310 the trackstate lines).
314 Non-ASCII characters are now properly supported in search terms.
318 The template syntax has been changed slightly to ignore whitespace in
323 Some formerly textual buttons are now replaced by images (with ALT text
324 reflecting the old value). The stylesheet is now a .css file (installed
325 in the same place as the images) rather than being embedded into every
328 Artist and album names in the playing and recently-played lists are now
329 links to the corresponding directory.
331 More functions are now available from the 'manage' screen.
333 The menus are now (by default) across the top of the screen instead of
334 down the side. Set the 'menu' label to 'sidebar' to restore the old
335 appearance. 'Volume' is not present in this new menu, use 'Manage'
336 instead (or edit the template).
340 tkdisorder now displays artist, album and title in the queue and
341 recently played widgets, rather than just the title (as formerly).
343 * Changes up to version 1.1
347 Corrected various problems with UTF-8 parsing.
349 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
350 'T' when grouping tracks by initial letter.
354 The list of recently played tracks is now preserved across server
357 Track IDs are more compact.
359 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
360 work now. 4.2 support will be removed in some future release.
362 Prehistoric backwards-compatibility logic removed. Only affects people
363 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
368 Tracks can be moved in the queue from the command line.
370 'disorder queue' now reports track IDs.
372 $pkgdatadir/completion.bash provides tab completion over commands and
377 New 'cooked' preferences interface saves users having to know arcane
378 details of trackname preferences and so on. Non-ASCII characters are
379 now properly supported in this context.
381 CGI arguments to the web interface are now checked for UTF-8 compliance.