Chris@211
|
1 Changes in Sonic Annotator 1.3 since the previous release 1.2:
|
Chris@211
|
2
|
Chris@211
|
3 Back-end (feature writer) changes:
|
Chris@211
|
4
|
Chris@211
|
5 - Add the --csv-digits, --lab-digits, and --jams-digits options to
|
Chris@211
|
6 control the number of significant figures printed for feature values
|
Chris@211
|
7
|
Chris@211
|
8 - Update the JAMS writer to JAMS 0.2.0 format
|
Chris@211
|
9
|
Chris@211
|
10 - Show a more useful error message when user provides a filename
|
Chris@211
|
11 instead of a transform id to the -d option (happened to me when
|
Chris@211
|
12 cut-and-pasting command lines and I was quite baffled at first)
|
Chris@211
|
13
|
Chris@200
|
14
|
Chris@200
|
15 Changes in Sonic Annotator 1.2 since the previous release 1.1:
|
Chris@200
|
16
|
Chris@200
|
17 Front-end changes:
|
Chris@200
|
18
|
Chris@200
|
19 - Add the --segments-from option, providing the ability to read
|
Chris@200
|
20 segment boundaries from a file
|
Chris@200
|
21
|
Chris@200
|
22 Back-end (feature writer) changes:
|
Chris@200
|
23
|
Chris@200
|
24 - Rename the JSON feature writer to JAMS. There may be other JSON
|
Chris@200
|
25 formats supported in future
|
Chris@200
|
26
|
Chris@200
|
27 Bug fixes:
|
Chris@200
|
28
|
Chris@200
|
29 - Fix invalid JSON written by JAMS feature writer for dense
|
Chris@200
|
30 features.
|
Chris@200
|
31 - Fix invalid UTF-8 output from RDF feature writer when processing
|
Chris@200
|
32 MP3 files having ID3 tags in non-ASCII, non-UTF8 encodings
|
Chris@200
|
33
|
Chris@127
|
34
|
Chris@127
|
35 Changes in Sonic Annotator 1.1 since the previous release 1.0:
|
Chris@127
|
36
|
Chris@127
|
37 Front-end changes:
|
Chris@127
|
38
|
Chris@127
|
39 - Add support for the start time and duration properties of a
|
Chris@127
|
40 transform, applying a plugin to only a range of the input audio
|
Chris@179
|
41 - Reduce the internal processing blocksize from 16384 to 1024 samples
|
Chris@179
|
42 to reduce extent of time rounding at end of file or range
|
Chris@128
|
43 - Add --multiplex option to compose multiple audio files into a
|
Chris@128
|
44 single multi-channel stream with one input file per channel
|
Chris@172
|
45 - Add --normalise to request each audio file be normalised to 1.0 max
|
Chris@172
|
46 - Add support for the plugin_version property of a transform, causing
|
Chris@172
|
47 Sonic Annotator to refuse to run with the wrong version of a plugin
|
Chris@128
|
48 - Add --minversion option to permit scripts to check that the
|
Chris@128
|
49 version of Sonic Annotator is as they expect
|
Chris@172
|
50 - Add new housekeeping options to list the available feature writers
|
Chris@172
|
51 and supported audio file formats
|
Chris@172
|
52 - Pull out the feature-writer-specific help text into separate help
|
Chris@172
|
53 options (-h <writertype>) as the help was getting too long
|
Chris@172
|
54
|
Chris@172
|
55 Back-end (feature writer) changes:
|
Chris@172
|
56
|
Chris@172
|
57 - Add --csv-omit-filename, --csv-end-times, and --csv-fill-ends
|
Chris@172
|
58 options to the CSV feature writer to adjust various aspects of its
|
Chris@172
|
59 output
|
Chris@172
|
60 - Add "json" feature writer, exporting to JAMS (JSON Annotated Music
|
Chris@181
|
61 Specification) format. This writer is provisional and is expected
|
Chris@172
|
62 to change in future releases to comply more effectively with the
|
Chris@172
|
63 specification
|
Chris@172
|
64 - Add "midi" feature writer, exporting to MIDI files
|
Chris@172
|
65 - Add "lab" feature writer, exporting to tab-separated label files.
|
Chris@172
|
66 (This is equivalent to using the CSV writer with a tab separator and
|
Chris@172
|
67 the new --csv-omit-filename and --csv-end-times options, but it's
|
Chris@172
|
68 simpler to use if .lab is what you want)
|
Chris@128
|
69
|
Chris@128
|
70 Bug fixes:
|
Chris@128
|
71
|
Chris@128
|
72 - Fix the former habit of forging ahead even if not all transform
|
Chris@128
|
73 files could be found or parsed (this may have been intentional
|
Chris@128
|
74 behaviour but it is confusing more than it is useful)
|
Chris@128
|
75 - Fix failure to support --summary-only flag when reading transforms
|
Chris@128
|
76 with summaries from a transform file
|
Chris@71
|
77
|
Chris@172
|
78
|
Chris@86
|
79 Changes in Sonic Annotator 1.0 since the previous release 0.7:
|
Chris@71
|
80
|
Chris@87
|
81 Bug fixes:
|
Chris@87
|
82
|
Chris@71
|
83 - Fix incorrect samplerate in reading m4a files on OS/X
|
Chris@73
|
84 - Fix incorrect handling of FixedSampleRate outputs (Vamp SDK fix)
|
Chris@86
|
85 - Add tests that use the Vamp test plugin
|
Chris@65
|
86
|
Chris@172
|
87
|
Chris@65
|
88 Changes in Sonic Annotator 0.7 since the previous release 0.6:
|
Chris@65
|
89
|
Chris@65
|
90 Build changes:
|
Chris@65
|
91
|
Chris@65
|
92 - Support 64-bit builds on OS/X (using CoreAudio instead of
|
Chris@65
|
93 obsolete QuickTime audio file reader)
|
Chris@65
|
94
|
Chris@65
|
95 - Simplify RDF reading and fix some bugs. Now requires Dataquay
|
Chris@65
|
96 (http://breakfastquay.com/dataquay/) rather than using Redland
|
Chris@65
|
97 directly. Release builds use Sord/Serd rather than Redland
|
Chris@49
|
98
|
Chris@172
|
99
|
Chris@49
|
100 Changes in Sonic Annotator 0.6 since the previous release 0.5:
|
Chris@49
|
101
|
Chris@49
|
102 Build changes:
|
Chris@49
|
103
|
Chris@49
|
104 - Switch to modular SV-libraries build using svcore library
|
Chris@53
|
105 - We now require Vamp plugin SDK v2.3
|
Chris@49
|
106 - Add autoconf configure script
|
Chris@49
|
107
|
Chris@49
|
108 Front-end changes:
|
Chris@49
|
109
|
Chris@49
|
110 - Pick up default sample rate and channel count from the first
|
Chris@49
|
111 audio file, where not specified in the transform, instead of using
|
Chris@49
|
112 hard coded defaults
|
Chris@53
|
113 - Make it possible to specify the window shape in transform
|
Chris@49
|
114 - Fix the --csv-one-file option which did not work in 0.5
|
Chris@49
|
115 - Fix --force option when using playlists
|
Chris@49
|
116 - Add -v option to print version number and exit
|
Chris@36
|
117
|
Chris@172
|
118
|
Chris@36
|
119 Changes in Sonic Annotator 0.5 since the previous release 0.4:
|
Chris@36
|
120
|
Chris@36
|
121 Build changes:
|
Chris@36
|
122
|
Chris@36
|
123 - Remove unused audioio library and avoid its dependencies
|
Chris@36
|
124
|
Chris@36
|
125 Front-end changes:
|
Chris@36
|
126
|
Chris@36
|
127 - Avoid leaking file descriptors on exceptions
|
Chris@36
|
128 - Fix embarrassing bug that caused failure to mix down to mono
|
Chris@36
|
129 properly for single-channel plugins with multi-channel input files
|
Chris@36
|
130 - Fail sooner if the output file is not writable (i.e. don't wait
|
Chris@36
|
131 until the first data is available for writing)
|
Chris@23
|
132
|
Chris@172
|
133
|
Chris@27
|
134 Changes in Sonic Annotator 0.4 since the previous release 0.3:
|
Chris@27
|
135
|
Chris@27
|
136 Build changes:
|
Chris@27
|
137
|
Chris@27
|
138 - Sonic Annotator now requires the Vamp plugin SDK v2.1 or newer.
|
Chris@27
|
139
|
Chris@27
|
140 Front-end changes:
|
Chris@27
|
141
|
Chris@28
|
142 - Frequency-domain plugins now use the PluginInputDomainAdapter's new
|
Chris@28
|
143 ShiftData processing method, ensuring that the first block received
|
Chris@28
|
144 by the plugin is the one centred on 0 rather than starting at 0.
|
Chris@28
|
145 Unfortunately, the old behaviour omitted a timing compensation step,
|
Chris@28
|
146 and this fix actually changes the results from some plugin processes:
|
Chris@28
|
147 the previous behaviour was not always in line with the Vamp plugin
|
Chris@28
|
148 specification.
|
Chris@28
|
149
|
Chris@27
|
150 - More useful diagnostics are now available when a plugin fails to
|
Chris@28
|
151 load or run.
|
Chris@27
|
152
|
Chris@27
|
153 CSV back-end (feature writer) changes:
|
Chris@27
|
154
|
Chris@27
|
155 - The CSV writer now closes its output files properly when it
|
Chris@27
|
156 finishes writing to each one, rather than leaving them all open
|
Chris@27
|
157 until the end and risk running out of file descriptors. This was
|
Chris@27
|
158 already the behaviour of the RDF writer, the CSV one has just been
|
Chris@27
|
159 updated to match it.
|
Chris@27
|
160 - The behaviour of the CSV writer has also been changed to match
|
Chris@27
|
161 that of the RDF writer in handling file write failures (it now
|
Chris@27
|
162 continues processing only if --force is given).
|
Chris@27
|
163
|
Chris@27
|
164
|
Chris@27
|
165 Changes in Sonic Annotator 0.3 since the previous release 0.2:
|
Chris@23
|
166
|
Chris@23
|
167 Front-end changes:
|
Chris@23
|
168
|
Chris@23
|
169 - A new --force front-end option (distinct from the --csv-force and
|
Chris@23
|
170 --rdf-force back-end options) has been added, which makes Sonic
|
Chris@23
|
171 Annotator continue to process subsequent audio files instead of
|
Chris@23
|
172 exiting after an error, if multiple audio files have been specified.
|
Chris@23
|
173
|
Chris@23
|
174 RDF back-end (feature writer) changes:
|
Chris@23
|
175
|
Chris@23
|
176 - The RDF writer now conforms more correctly with the Music Ontology
|
Chris@23
|
177 in the way it relates signal, track, and track metadata. Signals
|
Chris@23
|
178 that have available metadata now gain a Track resource to associate
|
Chris@23
|
179 that metadata with, instead of hanging it directly from the Signal
|
Chris@23
|
180 resource; also the audio file now encodes the signal rather than the
|
Chris@23
|
181 signal being available as the audio file (matching the domain
|
Chris@23
|
182 specification of the Music Ontology). Note that this new resource
|
Chris@23
|
183 structure will not be properly read by versions of Sonic Visualiser
|
Chris@23
|
184 prior to 1.6 (should importing the data into Sonic Visualiser be of
|
Chris@23
|
185 interest to you).
|
Chris@23
|
186
|
Chris@23
|
187 - The --rdf-signal-uri option has been removed and replaced with the
|
Chris@23
|
188 more meaningful set of options --rdf-audiofile-uri, --rdf-track-uri,
|
Chris@23
|
189 and --rdf-maker-uri.
|
Chris@23
|
190
|
Chris@23
|
191 - A new --rdf-network option is available, to cause Sonic Annotator
|
Chris@23
|
192 to try to retrieve RDF descriptions for plugins from the network
|
Chris@23
|
193 where those descriptions are not available locally. Use of this
|
Chris@23
|
194 option is recommended, but it is not the default because of the
|
Chris@23
|
195 possible performance implication (even though the results are mostly
|
Chris@23
|
196 cached, there may be some network access involved).
|
Chris@23
|
197
|
Chris@23
|
198 - The RDF writer now writes the computed_by property for signal
|
Chris@23
|
199 features.
|
Chris@23
|
200
|
Chris@23
|
201 - Plugin and output URIs in the resulting RDF are now percent-encoded.
|
Chris@23
|
202
|