chiark / gitweb /
New 'replay_min' directive defines lower bound on interval between a
[disorder] / CHANGES
... / ...
CommitLineData
1* Changes up to version 3.1
2
3** Server
4
5The 'gap' directive will no longer work. It could be restored if there
6is real demand.
7
8*** Random Track Choice
9
10This has been completely rewritten to support new features:
11 - tracks in the recently-played list or in the queue are no longer
12 eligible for random choice
13 - there is a new configuration item replay_min defining the minimum
14 time before a played track can be picked at random. The default is
15 8 hours (which matches the earlier behaviour).
16
17* Changes up to version 3.0
18
19Important! See README.upgrades when upgrading.
20
21** Platforms And Installation
22
23Mac OS X and FreeBSD are somewhat supported. There is now a bash script
24in scripts/setup which will automate the setup after 'make install'.
25
26** Server
27
28Users are now stored in the database rather than a configuration file.
29
30The server now has a built-in list of stopwords and players, so only
31additions to these need be mentioned in the configuration file.
32
33The default inter-track gap is now 0s.
34
35How sound is played is now controlled via the new 'api' configuration
36command. This also controls how the volume is set, which now works with
37ALSA as well as OSS.
38
39A bug in the MP3 decoder was fixed (also in 2.0.4).
40
41** Web Interface
42
43The web interface now uses cookies to remember user identity, and allows
44online registration of new users. Also it is no longer necessary to
45manually specify the URL of the web interface (but you can override it
46if you don't like the value it figures out).
47
48It is possible to allow users to register via the web interface.
49
50The web interface's browser support has been improved. It has been
51tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer 7 and
52Opera 9.
53
54** Disobedience
55
56A bug which would cause a crash if you attempt to rearrange the queue
57while no track was playing has been fixed. There is a new 'deselect all
58tracks' option, mirroring 'select all tracks.
59
60* Changes up to version 2.0
61
62** General
63
64Tracks can now have tags associated with them. See tags in disorder(1)
65or the preferences documentation for the web interface or Disobedience.
66
67The search facility knows how to limit results by tag (see search
68documentation for any interface) as well as by word search. It is
69possible to limit random play by tag (see required-tags and
70prohibited-tags in disorder_config(5)).
71
72Unicode support is improved. Case-folding and word breaking now follows
73the rules given in the Unicode standard (with a bit of tailoring in the
74latter case).
75
76** Disobedience
77
78There is a new client, 'Disobedience', that depends on the GTK+ library.
79Feedback on the interface would be very welcome.
80
81** Web Interface
82
83The "New" screen display tracks recently added to the database. From
84here they can be played or their preferences changed.
85
86Long track names are truncated so they fit better on the screen. Hover
87for the full name.
88
89** Network Play
90
91DisOrder can broadcast audio over a network, allowing it to be played on
92multiple client machines. See README.streams for details.
93
94** Server
95
96Slow file lookups are cached in the server. This should help
97installations with large collections and/or slow platforms.
98
99The 'enabled' and 'random_enabled' configuration options are now gone.
100Instead the state survives from one run of the server to the next.
101'disable now' is gone as well - if you want to emulate it disable
102playing and then scratch the current track.
103
104The 'pick' plugin has been abolished. All the logic formerly done there
105is now built into the server, where it can be done much more
106efficiently.
107
108'tracklength' plugins must be explicitly specified.
109
110A bug where removing a collection (from the configuration) could cause a
111crash when random play was enabled has been fixed.
112
113A new configuration option 'queue_pad' allows the number of random
114tracks kept on the queue to be controlled.
115
116There is a new utility disorder-decode which can decode OGG, MP3, WAV
117and FLAC. The example config file uses it.
118
119Database statistics are computed in a subprocess so that the main server
120(and all clients) are not blocked for the duration.
121
122** disorderfm
123
124There is a new command line tool called 'disorderfm' which is designed
125for filename translation on (for instance) digital audio repositories.
126It is not yet feature-complete. See its man page for additional
127details.
128
129** Build And Configuration
130
131You can control which components are built with new --with options. See
132README.
133
134options.transform and the 'transform' web option have gone, replaced
135with a 'transform' configuration command. Both this and 'namepart' are
136now optional.
137
138** Thanks
139
140Ross Younger, Colin Watson, Michael Stevens and Mark Wooding all
141contributed in some way to this release.
142
143* Changes up to version 1.5.1
144
145** Web Interface
146
147Correct regexp for non-alpha tracks.
148
149* Changes up to version 1.5
150
151** Web Interface
152
153Regexp-based filtering of tracks (for instance as used by the initial
154'Choose' page) now does the regexp matching in the server, limiting the
155amount of data transferred to the web interface only to be discarded.
156
157** Client
158
159Regexp-base filtering of tracks is now available to the command line
160client.
161
162** Server
163
164New server_nice, speaker_nice and rescan_nice configuration options
165allow independent control of process priorities.
166
167Scratches are now attributed to the user who requested them.
168
169Bugs fixed:
170 A file descriptor was leaked for each track played.
171 The amount of a track played so far was not reported.
172 The speaker process could crash on underrun.
173 The server would crash if you paused a non-pause capable track.
174 Regexp matching in the file and directory list commands was not
175 reliable.
176 Handling of variable-argument commands in the client was broken.
177
178* Changes up to version 1.4
179
180** General
181
182Raw format players are now supported. See README.upgrades and
183README.raw for details. This allows pausing and eliminating the
184inter-track gap.
185
186Pausing is also supported with suitably modified standalone player
187plugins, though none of the supplied ones are capable of this.
188
189When random play is enabled the randomly picked track now appears in the
190queue, and can be moved around the queue, removed from it, etc.
191
192** Web Interface
193
194Switches (random play, pause, ...) are now presented as a
195fixed-appearance switch with an adjacent state indicator.
196
197The 'Manage' screen has new buttons to move tracks to the head or tail
198of the queue.
199
200You can now edit the preferences for all the tracks in an album in a
201single screen, rather than having to visit each separately. For the
202time being the raw preferences editing has gone; it can be reintroduced
203on some form if there is demand. (You can still edit raw preferences
204from the command line.)
205
206Labels are now documented in options.labels rather than
207disorder_config(5).
208
209** Server
210
211If you tried to start up on any empty database with random play enabled
212the server would exit with an error.
213
214The server no longer risks failing if you strace its player
215subprocesses.
216
217It was possible for the server to hang when a 'reconfigure' command was
218issued. This should no longer be the case.
219
220The default signal to forcibly terminate players is now SIGKILL.
221
222** Plugins
223
224Plugins must now declare a type word. This allows them to document
225whether they are a standalone player or a raw-format player, and whether
226they support pausing. They can also arrange to get setup and cleanup
227calls in the main server. See disorder(3) for more details.
228
229* Changes up to version 1.3
230
231** Dependencies
232
233Berkeley DB 4.2 is no longer supported. Use 4.3.
234
235** Client
236
237There is a new 'authorize' command to simplify the addition of local
238users. Please report successes as well as failures.
239
240There is a new 'resolve' command to return the real track name behind an
241alias.
242
243The 'rescan' command no longer takes an argument.
244
245** Server
246
247The track database code has been largely rewritten to improve
248maintainability.
249
250There is a new 'lock' directive. By default the server uses a lockfile
251to prevent multiple copies of itself running simultaneously; this can be
252inhibited e.g. if you are using a filesystem that does not support
253locking and are confident you can prevent concurrent running yourself.
254
255Aliases for track names, constructed from trackname_display_
256preferences, now appear in the virtual filesystem.
257
258The server now executes a subprocess for the rescan operation. It also
259runs a separate deadlock manager.
260
261Standard output and standard error from subprocesses are now logged.
262This is handy if you need to figure out why a player failed unexpectedly
263but might lead to huge log files if you have needlessly verbose players.
264
265** Web Interface
266
267Enable/disable buttons are now colored to reflect current state.
268
269Entering numeric volume values (rather than clicking on the arrows) now
270works.
271
272Connection errors are reported more gracefully.
273
274** Plugins
275
276Scanner plugins are now always invoked in a subprocess.
277
278disorder_track_count() and disorder_track_getn() are no longer
279available. Instead use disorder_track_random().
280
281Plugins are now opened with RTLD_NOW, so link errors are detected
282immediately.
283
284** Tools
285
286disorder-dump now insists on the input/output file being a named regular
287file, rather than using stdin or stdout.
288
289** Other
290
291Some missing files have been added, and some notes added regarding
292getting text encoding right.
293
294* Changes up to version 1.2
295
296See README.upgrades when upgrading to this version.
297
298** Bugs Fixed
299
300Avoid accumulating overlarge recently played list.
301
302When the server was stopped, the currently playing track would not be
303added to the recently played list. This has been fixed.
304
305Reloading the 'volume' page no longer repeats the last volume-changing
306action.
307
308The search facility now works properly for multiple hits within a single
309artist or album.
310
311** Server
312
313New namepart directive replaces web interface's trackname-part. There
314are associated changes to the protocol and clients.
315
316The number of database queries per candidate match required when
317searching has been reduced.
318
319The operator can control the signal used to scratch playing tracks. The
320default has been changed to SIGINT from SIGKILL.
321
322The 'log' command now provides a formalised event log, rather than raw
323access to the server's ordinary log output.
324
325** Web Interface Changes
326
327*** Choosing Tracks
328
329When picking a track the client now stays on the same screen rather than
330redirecting back to the 'Playing' screen. So that the user gets
331feedback from their action, playing and queued tracks are now marked as
332such in the track picking screen.
333
334It is possible to revert to the old behaviour by removing the back=
335argument from the choose.html and search.html templates (and optionally
336the trackstate lines).
337
338*** Search
339
340Non-ASCII characters are now properly supported in search terms.
341
342*** Syntax
343
344The template syntax has been changed slightly to ignore whitespace in
345certain places.
346
347*** Miscellaneous
348
349Some formerly textual buttons are now replaced by images (with ALT text
350reflecting the old value). The stylesheet is now a .css file (installed
351in the same place as the images) rather than being embedded into every
352template.
353
354Artist and album names in the playing and recently-played lists are now
355links to the corresponding directory.
356
357More functions are now available from the 'manage' screen.
358
359The menus are now (by default) across the top of the screen instead of
360down the side. Set the 'menu' label to 'sidebar' to restore the old
361appearance. 'Volume' is not present in this new menu, use 'Manage'
362instead (or edit the template).
363
364** tkdisorder
365
366tkdisorder now displays artist, album and title in the queue and
367recently played widgets, rather than just the title (as formerly).
368
369* Changes up to version 1.1
370
371** Bugs Fixed
372
373Corrected various problems with UTF-8 parsing.
374
375In the web interface, "The Beatles" (etc) are now grouped under 'B' not
376'T' when grouping tracks by initial letter.
377
378** Server
379
380The list of recently played tracks is now preserved across server
381restarts.
382
383Track IDs are more compact.
384
385Versions of libdb before 4.2 are no longer supported. 4.2 and 4.3 both
386work now. 4.2 support will be removed in some future release.
387
388Prehistoric backwards-compatibility logic removed. Only affects people
389upgrading from long before 1.0 (who should upgrade to 1.0 and then to
3901.1.)
391
392** Command Line
393
394Tracks can be moved in the queue from the command line.
395
396'disorder queue' now reports track IDs.
397
398$pkgdatadir/completion.bash provides tab completion over commands and
399options.
400
401** Web Interface
402
403New 'cooked' preferences interface saves users having to know arcane
404details of trackname preferences and so on. Non-ASCII characters are
405now properly supported in this context.
406
407CGI arguments to the web interface are now checked for UTF-8 compliance.
408
409Local Variables:
410mode:outline
411fill-column:72
412End: