1 * Changes up to version 3.1
5 The 'gap' directive will no longer work. It could be restored if there
10 It is now possible to schedule events to occur in the future. Currently
11 the supported actions are playing a specific track, and changing a
12 global preference (thus allowing e.g. random play to be turned on or
13 off). See the schedule-* commands described in disorder(1).
15 *** Random Track Choice
17 This has been completely rewritten to support new features:
18 - tracks in the recently-played list or in the queue are no longer
19 eligible for random choice
20 - there is a new 'weight' track preference allowing for non-uniform
21 track selection. See disorder(1) for details.
22 - there is a new configuration item replay_min defining the minimum
23 time before a played track can be picked at random. The default is
24 8 hours (which matches the earlier behaviour).
25 - recently added tracks are biased up; see new_bias and new_bias_age
26 in disorder_config(5).
30 This has been largely rewritten. The most immediate benefits are:
31 - the search page is integrated into the choose page, and includes
32 links to parent directories
33 - if you try to do something you have insufficient rights for,
34 instead of getting an error page or nothing happening, you are
35 redirected to the login page
37 Customizers should find their lives easier: the syntax is less onerous,
38 it is possible to define macros to avoid repetition, and the
39 documentation is less monolithic.
43 There is now a new user management window. From here you can add and
44 remove users or modify their settings.
46 Relatedly, the server will only allow remote user management if you set
47 remote_userman to 'yes'.
51 scripts/setup now honors command line options, and can set up network
52 play as well as the local default sound device.
56 #2 Search results should link to directories
57 #6 Schedule tracks for a particular time
58 #10 Non-uniform track selection
59 #11 Bias random selection to newly added tracks
60 #16 Cookie expiry causes user to be silently logged out and not
61 subsequently redirected to login page
62 #20 Broken aliasing rules
64 * Changes up to version 3.0.2
66 Builds --without-server should work again.
68 The web interface is a bit more liberal in the cookie value syntax it
71 Clients fail more gracefully if no password is available.
73 * Changes up to version 3.0.1
75 Debian upgrades from 2.0.x should now work better.
77 * Changes up to version 3.0
79 Important! See README.upgrades when upgrading.
81 ** Platforms And Installation
83 Mac OS X and FreeBSD are somewhat supported. There is now a bash script
84 in scripts/setup which will automate the setup after 'make install'.
88 Users are now stored in the database rather than a configuration file.
90 The server now has a built-in list of stopwords and players, so only
91 additions to these need be mentioned in the configuration file.
93 The default inter-track gap is now 0s.
95 How sound is played is now controlled via the new 'api' configuration
96 command. This also controls how the volume is set, which now works with
99 A bug in the MP3 decoder was fixed (also in 2.0.4).
103 The web interface now uses cookies to remember user identity, and allows
104 online registration of new users. Also it is no longer necessary to
105 manually specify the URL of the web interface (but you can override it
106 if you don't like the value it figures out).
108 It is possible to allow users to register via the web interface.
110 The web interface's browser support has been improved. It has been
111 tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
116 A bug which would cause a crash if you attempt to rearrange the queue
117 while no track was playing has been fixed. There is a new 'deselect all
118 tracks' option, mirroring 'select all tracks.
120 * Changes up to version 2.0
124 Tracks can now have tags associated with them. See tags in disorder(1)
125 or the preferences documentation for the web interface or Disobedience.
127 The search facility knows how to limit results by tag (see search
128 documentation for any interface) as well as by word search. It is
129 possible to limit random play by tag (see required-tags and
130 prohibited-tags in disorder_config(5)).
132 Unicode support is improved. Case-folding and word breaking now follows
133 the rules given in the Unicode standard (with a bit of tailoring in the
138 There is a new client, 'Disobedience', that depends on the GTK+ library.
139 Feedback on the interface would be very welcome.
143 The "New" screen display tracks recently added to the database. From
144 here they can be played or their preferences changed.
146 Long track names are truncated so they fit better on the screen. Hover
151 DisOrder can broadcast audio over a network, allowing it to be played on
152 multiple client machines. See README.streams for details.
156 Slow file lookups are cached in the server. This should help
157 installations with large collections and/or slow platforms.
159 The 'enabled' and 'random_enabled' configuration options are now gone.
160 Instead the state survives from one run of the server to the next.
161 'disable now' is gone as well - if you want to emulate it disable
162 playing and then scratch the current track.
164 The 'pick' plugin has been abolished. All the logic formerly done there
165 is now built into the server, where it can be done much more
168 'tracklength' plugins must be explicitly specified.
170 A bug where removing a collection (from the configuration) could cause a
171 crash when random play was enabled has been fixed.
173 A new configuration option 'queue_pad' allows the number of random
174 tracks kept on the queue to be controlled.
176 There is a new utility disorder-decode which can decode OGG, MP3, WAV
177 and FLAC. The example config file uses it.
179 Database statistics are computed in a subprocess so that the main server
180 (and all clients) are not blocked for the duration.
184 There is a new command line tool called 'disorderfm' which is designed
185 for filename translation on (for instance) digital audio repositories.
186 It is not yet feature-complete. See its man page for additional
189 ** Build And Configuration
191 You can control which components are built with new --with options. See
194 options.transform and the 'transform' web option have gone, replaced
195 with a 'transform' configuration command. Both this and 'namepart' are
200 Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
201 contributed in some way to this release.
203 * Changes up to version 1.5.1
207 Correct regexp for non-alpha tracks.
209 * Changes up to version 1.5
213 Regexp-based filtering of tracks (for instance as used by the initial
214 'Choose' page) now does the regexp matching in the server, limiting the
215 amount of data transferred to the web interface only to be discarded.
219 Regexp-base filtering of tracks is now available to the command line
224 New server_nice, speaker_nice and rescan_nice configuration options
225 allow independent control of process priorities.
227 Scratches are now attributed to the user who requested them.
230 A file descriptor was leaked for each track played.
231 The amount of a track played so far was not reported.
232 The speaker process could crash on underrun.
233 The server would crash if you paused a non-pause capable track.
234 Regexp matching in the file and directory list commands was not
236 Handling of variable-argument commands in the client was broken.
238 * Changes up to version 1.4
242 Raw format players are now supported. See README.upgrades and
243 README.raw for details. This allows pausing and eliminating the
246 Pausing is also supported with suitably modified standalone player
247 plugins, though none of the supplied ones are capable of this.
249 When random play is enabled the randomly picked track now appears in the
250 queue, and can be moved around the queue, removed from it, etc.
254 Switches (random play, pause, ...) are now presented as a
255 fixed-appearance switch with an adjacent state indicator.
257 The 'Manage' screen has new buttons to move tracks to the head or tail
260 You can now edit the preferences for all the tracks in an album in a
261 single screen, rather than having to visit each separately. For the
262 time being the raw preferences editing has gone; it can be reintroduced
263 on some form if there is demand. (You can still edit raw preferences
264 from the command line.)
266 Labels are now documented in options.labels rather than
271 If you tried to start up on any empty database with random play enabled
272 the server would exit with an error.
274 The server no longer risks failing if you strace its player
277 It was possible for the server to hang when a 'reconfigure' command was
278 issued. This should no longer be the case.
280 The default signal to forcibly terminate players is now SIGKILL.
284 Plugins must now declare a type word. This allows them to document
285 whether they are a standalone player or a raw-format player, and whether
286 they support pausing. They can also arrange to get setup and cleanup
287 calls in the main server. See disorder(3) for more details.
289 * Changes up to version 1.3
293 Berkeley DB 4.2 is no longer supported. Use 4.3.
297 There is a new 'authorize' command to simplify the addition of local
298 users. Please report successes as well as failures.
300 There is a new 'resolve' command to return the real track name behind an
303 The 'rescan' command no longer takes an argument.
307 The track database code has been largely rewritten to improve
310 There is a new 'lock' directive. By default the server uses a lockfile
311 to prevent multiple copies of itself running simultaneously; this can be
312 inhibited e.g. if you are using a filesystem that does not support
313 locking and are confident you can prevent concurrent running yourself.
315 Aliases for track names, constructed from trackname_display_
316 preferences, now appear in the virtual filesystem.
318 The server now executes a subprocess for the rescan operation. It also
319 runs a separate deadlock manager.
321 Standard output and standard error from subprocesses are now logged.
322 This is handy if you need to figure out why a player failed unexpectedly
323 but might lead to huge log files if you have needlessly verbose players.
327 Enable/disable buttons are now colored to reflect current state.
329 Entering numeric volume values (rather than clicking on the arrows) now
332 Connection errors are reported more gracefully.
336 Scanner plugins are now always invoked in a subprocess.
338 disorder_track_count() and disorder_track_getn() are no longer
339 available. Instead use disorder_track_random().
341 Plugins are now opened with RTLD_NOW, so link errors are detected
346 disorder-dump now insists on the input/output file being a named regular
347 file, rather than using stdin or stdout.
351 Some missing files have been added, and some notes added regarding
352 getting text encoding right.
354 * Changes up to version 1.2
356 See README.upgrades when upgrading to this version.
360 Avoid accumulating overlarge recently played list.
362 When the server was stopped, the currently playing track would not be
363 added to the recently played list. This has been fixed.
365 Reloading the 'volume' page no longer repeats the last volume-changing
368 The search facility now works properly for multiple hits within a single
373 New namepart directive replaces web interface's trackname-part. There
374 are associated changes to the protocol and clients.
376 The number of database queries per candidate match required when
377 searching has been reduced.
379 The operator can control the signal used to scratch playing tracks. The
380 default has been changed to SIGINT from SIGKILL.
382 The 'log' command now provides a formalised event log, rather than raw
383 access to the server's ordinary log output.
385 ** Web Interface Changes
389 When picking a track the client now stays on the same screen rather than
390 redirecting back to the 'Playing' screen. So that the user gets
391 feedback from their action, playing and queued tracks are now marked as
392 such in the track picking screen.
394 It is possible to revert to the old behaviour by removing the back=
395 argument from the choose.html and search.html templates (and optionally
396 the trackstate lines).
400 Non-ASCII characters are now properly supported in search terms.
404 The template syntax has been changed slightly to ignore whitespace in
409 Some formerly textual buttons are now replaced by images (with ALT text
410 reflecting the old value). The stylesheet is now a .css file (installed
411 in the same place as the images) rather than being embedded into every
414 Artist and album names in the playing and recently-played lists are now
415 links to the corresponding directory.
417 More functions are now available from the 'manage' screen.
419 The menus are now (by default) across the top of the screen instead of
420 down the side. Set the 'menu' label to 'sidebar' to restore the old
421 appearance. 'Volume' is not present in this new menu, use 'Manage'
422 instead (or edit the template).
426 tkdisorder now displays artist, album and title in the queue and
427 recently played widgets, rather than just the title (as formerly).
429 * Changes up to version 1.1
433 Corrected various problems with UTF-8 parsing.
435 In the web interface, "The Beatles" (etc) are now grouped under 'B' not
436 'T' when grouping tracks by initial letter.
440 The list of recently played tracks is now preserved across server
443 Track IDs are more compact.
445 Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
446 work now. 4.2 support will be removed in some future release.
448 Prehistoric backwards-compatibility logic removed. Only affects people
449 upgrading from long before 1.0 (who should upgrade to 1.0 and then to
454 Tracks can be moved in the queue from the command line.
456 'disorder queue' now reports track IDs.
458 $pkgdatadir/completion.bash provides tab completion over commands and
463 New 'cooked' preferences interface saves users having to know arcane
464 details of trackname preferences and so on. Non-ASCII characters are
465 now properly supported in this context.
467 CGI arguments to the web interface are now checked for UTF-8 compliance.