1 See ChangeLog.d/* for detailed revision history.
3 * Changes up to version 1.6
7 There is a new client, 'Disobedience', that depends on the GTK+ library.
8 Feedback on the interface would be very welcome.
10 Tracks can now have tags associated with them. See tags in disorder(1)
11 or the preferences documentation for the web interface or Disobedience.
13 The search facility knows how to limit results by tag (see search
14 documentation for any interface) as well as by word search. It is
15 possible to limit random play by tag (see required-tags and
16 prohibited-tags in disorder_config(5)).
20 Cache slow file lookups in the server. Should help installations with
21 large collections and/or slow platforms.
23 The communications protocol has changed, for the benefit of
26 The 'enabled' and 'random_enabled' configuration options are now gone.
27 Instead the state survives from one run of the server to the next.
28 'disable now' is gone as well - if you want to emulate it disable
29 playing and then scratch the current track.
31 The 'pick' plugin has been abolished. All the logic formerly done there
32 is now built into the server, where it can be done much more
35 A bug where removing a collection (from the configuration) could cause a
36 crash when random play was enabled has been fixed.
38 A new configuration option 'queue_pad' allows the number of random
39 tracks kept on the queue to be controlled.
43 DisOrder can broadcast audio over a network, allowing it to be played on
44 multiple client machines. See README.streams for details.
48 There is a new command line tool called 'disorderfm' which is designed
49 for filename translation on (for instance) digital audio repositories.
50 It is not yet feature-complete. See its man page for additional
53 ** Build And Configuration
55 You can control which components are built with new --with options. See
58 options.transform and the 'transform' web option have gone, replaced
59 with a 'transform' configuration command. Both this and 'namepart' are
64 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
65 contributed in some way to this release.
67 * Changes up to version 1.5.1
71 Correct regexp for non-alpha tracks.
73 * Changes up to version 1.5
77 Regexp-based filtering of tracks (for instance as used by the initial
78 'Choose' page) now does the regexp matching in the server, limiting the
79 amount of data transferred to the web interface only to be discarded.
83 Regexp-base filtering of tracks is now available to the command line
88 New server_nice, speaker_nice and rescan_nice configuration options
89 allow independent control of process priorities.
91 Scratches are now attributed to the user who requested them.
94 A file descriptor was leaked for each track played.
95 The amount of a track played so far was not reported.
96 The speaker process could crash on underrun.
97 The server would crash if you paused a non-pause capable track.
98 Regexp matching in the file and directory list commands was not
100 Handling of variable-argument commands in the client was broken.
102 * Changes up to version 1.4
106 Raw format players are now supported. See README.upgrades and
107 README.raw for details. This allows pausing and eliminating the
110 Pausing is also supported with suitably modified standalone player
111 plugins, though none of the supplied ones are capable of this.
113 When random play is enabled the randomly picked track now appears in the
114 queue, and can be moved around the queue, removed from it, etc.
118 Switches (random play, pause, ...) are now presented as a
119 fixed-appearance switch with an adjacent state indicator.
121 The 'Manage' screen has new buttons to move tracks to the head or tail
124 You can now edit the preferences for all the tracks in an album in a
125 single screen, rather than having to visit each separately. For the
126 time being the raw preferences editing has gone; it can be reintroduced
127 on some form if there is demand. (You can still edit raw preferences
128 from the command line.)
130 Labels are now documented in options.labels rather than
135 If you tried to start up on any empty database with random play enabled
136 the server would exit with an error.
138 The server no longer risks failing if you strace its player
141 It was possible for the server to hang when a 'reconfigure' command was
142 issued. This should no longer be the case.
144 The default signal to forcibly terminate players is now SIGKILL.
148 Plugins must now declare a type word. This allows them to document
149 whether they are a standalone player or a raw-format player, and whether
150 they support pausing. They can also arrange to get setup and cleanup
151 calls in the main server. See disorder(3) for more details.
153 * Changes up to version 1.3
157 Berkeley DB 4.2 is no longer supported. Use 4.3.
161 There is a new 'authorize' command to simplify the addition of local
162 users. Please report successes as well as failures.
164 There is a new 'resolve' command to return the real track name behind an
167 The 'rescan' command no longer takes an argument.
171 The track database code has been largely rewritten to improve
174 There is a new 'lock' directive. By default the server uses a lockfile
175 to prevent multiple copies of itself running simultaneously; this can be
176 inhibited e.g. if you are using a filesystem that does not support
177 locking and are confident you can prevent concurrent running yourself.
179 Aliases for track names, constructed from trackname_display_
180 preferences, now appear in the virtual filesystem.
182 The server now executes a subprocess for the rescan operation. It also
183 runs a separate deadlock manager.
185 Standard output and standard error from subprocesses are now logged.
186 This is handy if you need to figure out why a player failed unexpectedly
187 but might lead to huge log files if you have needlessly verbose players.
191 Enable/disable buttons are now colored to reflect current state.
193 Entering numeric volume values (rather than clicking on the arrows) now
196 Connection errors are reported more gracefuly.
200 Scanner plugins are now always invoked in a subprocess.
202 disorder_track_count() and disorder_track_getn() are no longer
203 available. Instead use disorder_track_random().
205 Plugins are now opened with RTLD_NOW, so link errors are detected
210 disorder-dump now insists on the input/output file being a named regular
211 file, rather than using stdin or stdout.
215 Some missing files have been added, and some notes added regarding
216 getting text encoding right.
218 * Changes up to version 1.2
220 See README.upgrades when upgrading to this version.
224 Avoid accumulating overlarge recently played list.
226 When the server was stopped, the currently playing track would not be
227 added to the recently played list. This has been fixed.
229 Reloading the 'volume' page no longer repeats the last volume-changing
232 The search facility now works properly for multiple hits within a single
237 New namepart directive replaces web interface's trackname-part. There
238 are associated changes to the protocol and clients.
240 The number of database queries per candidate match required when
241 searching has been reduced.
243 The operator can control the signal used to scratch playing tracks. The
244 default has been changed to SIGINT from SIGKILL.
246 The 'log' command now provides a formalised event log, rather than raw
247 access to the server's ordinary log output.
249 ** Web Interface Changes
253 When picking a track the client now stays on the same screen rather than
254 redirecting back to the 'Playing' screen. So that the user gets
255 feedback from their action, playing and queued tracks are now marked as
256 such in the track picking screen.
258 It is possible to revert to the old behaviour by removing the back=
259 argument from the choose.html and search.html templates (and optionally
260 the trackstate lines).
264 Non-ASCII characters are now properly supported in search terms.
268 The template syntax has been changed slightly to ignore whitespace in
273 Some formerly textual buttons are now replaced by images (with ALT text
274 reflecting the old value). The stylesheet is now a .css file (installed
275 in the same place as the images) rather than being embedded into every
278 Artist and album names in the playing and recently-played lists are now
279 links to the corresponding directory.
281 More functions are now available from the 'manage' screen.
283 The menus are now (by default) across the top of the screen instead of
284 down the side. Set the 'menu' label to 'sidebar' to restore the old
285 appearance. 'Volume' is not present in this new menu, use 'Manage'
286 instead (or edit the template).
290 tkdisorder now displays artist, album and title in the queue and
291 recently played widgets, rather than just the title (as formerly).
293 * Changes up to version 1.1
297 Corrected various problems with UTF-8 parsing.
299 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
300 'T' when grouping tracks by initial letter.
304 The list of recently played tracks is now preserved across server
307 Track IDs are more compact.
309 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
310 work now. 4.2 support will be removed in some future release.
312 Prehistoric backwards-compatibility logic removed. Only affects people
313 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
318 Tracks can be moved in the queue from the command line.
320 'disorder queue' now reports track IDs.
322 $pkgdatadir/completion.bash provides tab completion over commands and
327 New 'cooked' preferences interface saves users having to know arcane
328 details of trackname preferences and so on. Non-ASCII characters are
329 now properly supported in this context.
331 CGI arguments to the web interface are now checked for UTF-8 compliance.