1 See ChangeLog.d/* for detailed revision history.
3 * Changes up to version 1.6
7 Tracks can now have tags associated with them. See tags in disorder(1)
8 or the preferences documentation for the web interface or Disobedience.
10 The search facility knows how to limit results by tag (see search
11 documentation for any interface) as well as by word search. It is
12 possible to limit random play by tag (see required-tags and
13 prohibited-tags in disorder_config(5)).
17 There is a new client, 'Disobedience', that depends on the GTK+ library.
18 Feedback on the interface would be very welcome.
22 The "New" screen display tracks recently added to the database. From
23 here they can be played or their preferences changed.
27 DisOrder can broadcast audio over a network, allowing it to be played on
28 multiple client machines. See README.streams for details.
32 Cache slow file lookups in the server. Should help installations with
33 large collections and/or slow platforms.
35 The communications protocol has changed, for the benefit of
38 The 'enabled' and 'random_enabled' configuration options are now gone.
39 Instead the state survives from one run of the server to the next.
40 'disable now' is gone as well - if you want to emulate it disable
41 playing and then scratch the current track.
43 The 'pick' plugin has been abolished. All the logic formerly done there
44 is now built into the server, where it can be done much more
47 A bug where removing a collection (from the configuration) could cause a
48 crash when random play was enabled has been fixed.
50 A new configuration option 'queue_pad' allows the number of random
51 tracks kept on the queue to be controlled.
53 There is a new utility disorder-decode which can decode OGG, MP3, WAV
54 and FLAC. The example config file uses it.
58 There is a new command line tool called 'disorderfm' which is designed
59 for filename translation on (for instance) digital audio repositories.
60 It is not yet feature-complete. See its man page for additional
63 ** Build And Configuration
65 You can control which components are built with new --with options. See
68 options.transform and the 'transform' web option have gone, replaced
69 with a 'transform' configuration command. Both this and 'namepart' are
74 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
75 contributed in some way to this release.
77 * Changes up to version 1.5.1
81 Correct regexp for non-alpha tracks.
83 * Changes up to version 1.5
87 Regexp-based filtering of tracks (for instance as used by the initial
88 'Choose' page) now does the regexp matching in the server, limiting the
89 amount of data transferred to the web interface only to be discarded.
93 Regexp-base filtering of tracks is now available to the command line
98 New server_nice, speaker_nice and rescan_nice configuration options
99 allow independent control of process priorities.
101 Scratches are now attributed to the user who requested them.
104 A file descriptor was leaked for each track played.
105 The amount of a track played so far was not reported.
106 The speaker process could crash on underrun.
107 The server would crash if you paused a non-pause capable track.
108 Regexp matching in the file and directory list commands was not
110 Handling of variable-argument commands in the client was broken.
112 * Changes up to version 1.4
116 Raw format players are now supported. See README.upgrades and
117 README.raw for details. This allows pausing and eliminating the
120 Pausing is also supported with suitably modified standalone player
121 plugins, though none of the supplied ones are capable of this.
123 When random play is enabled the randomly picked track now appears in the
124 queue, and can be moved around the queue, removed from it, etc.
128 Switches (random play, pause, ...) are now presented as a
129 fixed-appearance switch with an adjacent state indicator.
131 The 'Manage' screen has new buttons to move tracks to the head or tail
134 You can now edit the preferences for all the tracks in an album in a
135 single screen, rather than having to visit each separately. For the
136 time being the raw preferences editing has gone; it can be reintroduced
137 on some form if there is demand. (You can still edit raw preferences
138 from the command line.)
140 Labels are now documented in options.labels rather than
145 If you tried to start up on any empty database with random play enabled
146 the server would exit with an error.
148 The server no longer risks failing if you strace its player
151 It was possible for the server to hang when a 'reconfigure' command was
152 issued. This should no longer be the case.
154 The default signal to forcibly terminate players is now SIGKILL.
158 Plugins must now declare a type word. This allows them to document
159 whether they are a standalone player or a raw-format player, and whether
160 they support pausing. They can also arrange to get setup and cleanup
161 calls in the main server. See disorder(3) for more details.
163 * Changes up to version 1.3
167 Berkeley DB 4.2 is no longer supported. Use 4.3.
171 There is a new 'authorize' command to simplify the addition of local
172 users. Please report successes as well as failures.
174 There is a new 'resolve' command to return the real track name behind an
177 The 'rescan' command no longer takes an argument.
181 The track database code has been largely rewritten to improve
184 There is a new 'lock' directive. By default the server uses a lockfile
185 to prevent multiple copies of itself running simultaneously; this can be
186 inhibited e.g. if you are using a filesystem that does not support
187 locking and are confident you can prevent concurrent running yourself.
189 Aliases for track names, constructed from trackname_display_
190 preferences, now appear in the virtual filesystem.
192 The server now executes a subprocess for the rescan operation. It also
193 runs a separate deadlock manager.
195 Standard output and standard error from subprocesses are now logged.
196 This is handy if you need to figure out why a player failed unexpectedly
197 but might lead to huge log files if you have needlessly verbose players.
201 Enable/disable buttons are now colored to reflect current state.
203 Entering numeric volume values (rather than clicking on the arrows) now
206 Connection errors are reported more gracefuly.
210 Scanner plugins are now always invoked in a subprocess.
212 disorder_track_count() and disorder_track_getn() are no longer
213 available. Instead use disorder_track_random().
215 Plugins are now opened with RTLD_NOW, so link errors are detected
220 disorder-dump now insists on the input/output file being a named regular
221 file, rather than using stdin or stdout.
225 Some missing files have been added, and some notes added regarding
226 getting text encoding right.
228 * Changes up to version 1.2
230 See README.upgrades when upgrading to this version.
234 Avoid accumulating overlarge recently played list.
236 When the server was stopped, the currently playing track would not be
237 added to the recently played list. This has been fixed.
239 Reloading the 'volume' page no longer repeats the last volume-changing
242 The search facility now works properly for multiple hits within a single
247 New namepart directive replaces web interface's trackname-part. There
248 are associated changes to the protocol and clients.
250 The number of database queries per candidate match required when
251 searching has been reduced.
253 The operator can control the signal used to scratch playing tracks. The
254 default has been changed to SIGINT from SIGKILL.
256 The 'log' command now provides a formalised event log, rather than raw
257 access to the server's ordinary log output.
259 ** Web Interface Changes
263 When picking a track the client now stays on the same screen rather than
264 redirecting back to the 'Playing' screen. So that the user gets
265 feedback from their action, playing and queued tracks are now marked as
266 such in the track picking screen.
268 It is possible to revert to the old behaviour by removing the back=
269 argument from the choose.html and search.html templates (and optionally
270 the trackstate lines).
274 Non-ASCII characters are now properly supported in search terms.
278 The template syntax has been changed slightly to ignore whitespace in
283 Some formerly textual buttons are now replaced by images (with ALT text
284 reflecting the old value). The stylesheet is now a .css file (installed
285 in the same place as the images) rather than being embedded into every
288 Artist and album names in the playing and recently-played lists are now
289 links to the corresponding directory.
291 More functions are now available from the 'manage' screen.
293 The menus are now (by default) across the top of the screen instead of
294 down the side. Set the 'menu' label to 'sidebar' to restore the old
295 appearance. 'Volume' is not present in this new menu, use 'Manage'
296 instead (or edit the template).
300 tkdisorder now displays artist, album and title in the queue and
301 recently played widgets, rather than just the title (as formerly).
303 * Changes up to version 1.1
307 Corrected various problems with UTF-8 parsing.
309 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
310 'T' when grouping tracks by initial letter.
314 The list of recently played tracks is now preserved across server
317 Track IDs are more compact.
319 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
320 work now. 4.2 support will be removed in some future release.
322 Prehistoric backwards-compatibility logic removed. Only affects people
323 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
328 Tracks can be moved in the queue from the command line.
330 'disorder queue' now reports track IDs.
332 $pkgdatadir/completion.bash provides tab completion over commands and
337 New 'cooked' preferences interface saves users having to know arcane
338 details of trackname preferences and so on. Non-ASCII characters are
339 now properly supported in this context.
341 CGI arguments to the web interface are now checked for UTF-8 compliance.