chiark / gitweb /
docs note that sox is required for speaker_command
[disorder] / CHANGES
CommitLineData
460b9539 1See ChangeLog.d/* for detailed revision history.
2
3* Changes up to version 1.6
4
5** General
6
7There is a new client, 'Disobedience', that depends on the GTK+ library.
8Feedback on the interface would be very welcome.
9
10Tracks can now have tags associated with them. See tags in disorder(1)
11or the preferences documentation for the web interface or Disobedience.
12
13The search facility knows how to limit results by tag (see search
14documentation for any interface) as well as by word search. It is
15possible to limit random play by tag (see required-tags and
16prohibited-tags in disorder_config(5)).
17
18** Server
19
20Cache slow file lookups in the server. Should help installations with
21large collections and/or slow platforms.
22
23The communications protocol has changed, for the benefit of
24Disobedience.
25
26The 'enabled' and 'random_enabled' configuration options are now gone.
27Instead 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
29playing and then scratch the current track.
30
31The 'pick' plugin has been abolished. All the logic formerly done there
32is now built into the server, where it can be done much more
33efficiently.
34
6aba3f6c
RK
35A bug where removing a collection (from the configuration) could cause a
36crash when random play was enabled has been fixed.
37
460b9539 38** disorderfm
39
40There is a new command line tool called 'disorderfm' which is designed
41for filename translation on (for instance) digital audio repositories.
42It is not yet feature-complete. See its man page for additional
43details.
44
45** Build And Configuration
46
47You can control which components are built with new --with options. See
48README.
49
50options.transform and the 'transform' web option have gone, replaced
51with a 'transform' configuration command. Both this and 'namepart' are
52now optional.
53
54* Changes up to version 1.5.1
55
56** Web Interface
57
58Correct regexp for non-alpha tracks.
59
60* Changes up to version 1.5
61
62** Web Interface
63
64Regexp-based filtering of tracks (for instance as used by the initial
65'Choose' page) now does the regexp matching in the server, limiting the
66amount of data transferred to the web interface only to be discarded.
67
68** Client
69
70Regexp-base filtering of tracks is now available to the command line
71client.
72
73** Server
74
75New server_nice, speaker_nice and rescan_nice configuration options
76allow independent control of process priorities.
77
78Scratches are now attributed to the user who requested them.
79
80Bugs fixed:
81 A file descriptor was leaked for each track played.
82 The amount of a track played so far was not reported.
83 The speaker process could crash on underrun.
84 The server would crash if you paused a non-pause capable track.
85 Regexp matching in the file and directory list commands was not
86 reliable.
87 Handling of variable-argument commands in the client was broken.
88
89* Changes up to version 1.4
90
91** General
92
93Raw format players are now supported. See README.upgrades and
94README.raw for details. This allows pausing and eliminating the
95inter-track gap.
96
97Pausing is also supported with suitably modified standalone player
98plugins, though none of the supplied ones are capable of this.
99
100When random play is enabled the randomly picked track now appears in the
101queue, and can be moved around the queue, removed from it, etc.
102
103** Web Interface
104
105Switches (random play, pause, ...) are now presented as a
106fixed-appearance switch with an adjacent state indicator.
107
108The 'Manage' screen has new buttons to move tracks to the head or tail
109of the queue.
110
111You can now edit the preferences for all the tracks in an album in a
112single screen, rather than having to visit each separately. For the
113time being the raw preferences editing has gone; it can be reintroduced
114on some form if there is demand. (You can still edit raw preferences
115from the command line.)
116
117Labels are now documented in options.labels rather than
118disorder_config(5).
119
120** Server
121
122If you tried to start up on any empty database with random play enabled
123the server would exit with an error.
124
125The server no longer risks failing if you strace its player
126subprocesses.
127
128It was possible for the server to hang when a 'reconfigure' command was
129issued. This should no longer be the case.
130
131The default signal to forcibly terminate players is now SIGKILL.
132
133** Plugins
134
135Plugins must now declare a type word. This allows them to document
136whether they are a standalone player or a raw-format player, and whether
137they support pausing. They can also arrange to get setup and cleanup
138calls in the main server. See disorder(3) for more details.
139
140* Changes up to version 1.3
141
142** Dependencies
143
144Berkeley DB 4.2 is no longer supported. Use 4.3.
145
146** Client
147
148There is a new 'authorize' command to simplify the addition of local
149users. Please report successes as well as failures.
150
151There is a new 'resolve' command to return the real track name behind an
152alias.
153
154The 'rescan' command no longer takes an argument.
155
156** Server
157
158The track database code has been largely rewritten to improve
159maintainability.
160
161There is a new 'lock' directive. By default the server uses a lockfile
162to prevent multiple copies of itself running simultaneously; this can be
163inhibited e.g. if you are using a filesystem that does not support
164locking and are confident you can prevent concurrent running yourself.
165
166Aliases for track names, constructed from trackname_display_
167preferences, now appear in the virtual filesystem.
168
169The server now executes a subprocess for the rescan operation. It also
170runs a separate deadlock manager.
171
172Standard output and standard error from subprocesses are now logged.
173This is handy if you need to figure out why a player failed unexpectedly
174but might lead to huge log files if you have needlessly verbose players.
175
176** Web Interface
177
178Enable/disable buttons are now colored to reflect current state.
179
180Entering numeric volume values (rather than clicking on the arrows) now
181works.
182
183Connection errors are reported more gracefuly.
184
185** Plugins
186
187Scanner plugins are now always invoked in a subprocess.
188
189disorder_track_count() and disorder_track_getn() are no longer
190available. Instead use disorder_track_random().
191
192Plugins are now opened with RTLD_NOW, so link errors are detected
193immediately.
194
195** Tools
196
197disorder-dump now insists on the input/output file being a named regular
198file, rather than using stdin or stdout.
199
200** Other
201
202Some missing files have been added, and some notes added regarding
203getting text encoding right.
204
205* Changes up to version 1.2
206
207See README.upgrades when upgrading to this version.
208
209** Bugs Fixed
210
211Avoid accumulating overlarge recently played list.
212
213When the server was stopped, the currently playing track would not be
214added to the recently played list. This has been fixed.
215
216Reloading the 'volume' page no longer repeats the last volume-changing
217action.
218
219The search facility now works properly for multiple hits within a single
220artist or album.
221
222** Server
223
224New namepart directive replaces web interface's trackname-part. There
225are associated changes to the protocol and clients.
226
227The number of database queries per candidate match required when
228searching has been reduced.
229
230The operator can control the signal used to scratch playing tracks. The
231default has been changed to SIGINT from SIGKILL.
232
233The 'log' command now provides a formalised event log, rather than raw
234access to the server's ordinary log output.
235
236** Web Interface Changes
237
238*** Choosing Tracks
239
240When picking a track the client now stays on the same screen rather than
241redirecting back to the 'Playing' screen. So that the user gets
242feedback from their action, playing and queued tracks are now marked as
243such in the track picking screen.
244
245It is possible to revert to the old behaviour by removing the back=
246argument from the choose.html and search.html templates (and optionally
247the trackstate lines).
248
249*** Search
250
251Non-ASCII characters are now properly supported in search terms.
252
253*** Syntax
254
255The template syntax has been changed slightly to ignore whitespace in
256certain places.
257
258*** Miscellaneous
259
260Some formerly textual buttons are now replaced by images (with ALT text
261reflecting the old value). The stylesheet is now a .css file (installed
262in the same place as the images) rather than being embedded into every
263template.
264
265Artist and album names in the playing and recently-played lists are now
266links to the corresponding directory.
267
268More functions are now available from the 'manage' screen.
269
270The menus are now (by default) across the top of the screen instead of
271down the side. Set the 'menu' label to 'sidebar' to restore the old
272appearance. 'Volume' is not present in this new menu, use 'Manage'
273instead (or edit the template).
274
275** tkdisorder
276
277tkdisorder now displays artist, album and title in the queue and
278recently played widgets, rather than just the title (as formerly).
279
280* Changes up to version 1.1
281
282** Bugs Fixed
283
284Corrected various problems with UTF-8 parsing.
285
286In the web interface, "The Beatles" (etc) are now grouped under 'B' not
287'T' when grouping tracks by initial letter.
288
289** Server
290
291The list of recently played tracks is now preserved across server
292restarts.
293
294Track IDs are more compact.
295
296Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
297work now. 4.2 support will be removed in some future release.
298
299Prehistoric backwards-compatibility logic removed. Only affects people
300upgrading from long before 1.0 (who should upgrade to 1.0 and then to
3011.1.)
302
303** Command Line
304
305Tracks can be moved in the queue from the command line.
306
307'disorder queue' now reports track IDs.
308
309$pkgdatadir/completion.bash provides tab completion over commands and
310options.
311
312** Web Interface
313
314New 'cooked' preferences interface saves users having to know arcane
315details of trackname preferences and so on. Non-ASCII characters are
316now properly supported in this context.
317
318CGI arguments to the web interface are now checked for UTF-8 compliance.
319
320Local Variables:
321mode:outline
322fill-column:72
323End: