|
Chris@71
|
1
|
|
Chris@86
|
2 Changes in Sonic Annotator 1.0 since the previous release 0.7:
|
|
Chris@71
|
3
|
|
Chris@71
|
4 - Fix incorrect samplerate in reading m4a files on OS/X
|
|
Chris@73
|
5 - Fix incorrect handling of FixedSampleRate outputs (Vamp SDK fix)
|
|
Chris@86
|
6 - Add tests that use the Vamp test plugin
|
|
Chris@65
|
7
|
|
Chris@65
|
8 Changes in Sonic Annotator 0.7 since the previous release 0.6:
|
|
Chris@65
|
9
|
|
Chris@65
|
10 Build changes:
|
|
Chris@65
|
11
|
|
Chris@65
|
12 - Support 64-bit builds on OS/X (using CoreAudio instead of
|
|
Chris@65
|
13 obsolete QuickTime audio file reader)
|
|
Chris@65
|
14
|
|
Chris@65
|
15 - Simplify RDF reading and fix some bugs. Now requires Dataquay
|
|
Chris@65
|
16 (http://breakfastquay.com/dataquay/) rather than using Redland
|
|
Chris@65
|
17 directly. Release builds use Sord/Serd rather than Redland
|
|
Chris@49
|
18
|
|
Chris@49
|
19 Changes in Sonic Annotator 0.6 since the previous release 0.5:
|
|
Chris@49
|
20
|
|
Chris@49
|
21 Build changes:
|
|
Chris@49
|
22
|
|
Chris@49
|
23 - Switch to modular SV-libraries build using svcore library
|
|
Chris@53
|
24 - We now require Vamp plugin SDK v2.3
|
|
Chris@49
|
25 - Add autoconf configure script
|
|
Chris@49
|
26
|
|
Chris@49
|
27 Front-end changes:
|
|
Chris@49
|
28
|
|
Chris@49
|
29 - Pick up default sample rate and channel count from the first
|
|
Chris@49
|
30 audio file, where not specified in the transform, instead of using
|
|
Chris@49
|
31 hard coded defaults
|
|
Chris@53
|
32 - Make it possible to specify the window shape in transform
|
|
Chris@49
|
33 - Fix the --csv-one-file option which did not work in 0.5
|
|
Chris@49
|
34 - Fix --force option when using playlists
|
|
Chris@49
|
35 - Add -v option to print version number and exit
|
|
Chris@36
|
36
|
|
Chris@36
|
37 Changes in Sonic Annotator 0.5 since the previous release 0.4:
|
|
Chris@36
|
38
|
|
Chris@36
|
39 Build changes:
|
|
Chris@36
|
40
|
|
Chris@36
|
41 - Remove unused audioio library and avoid its dependencies
|
|
Chris@36
|
42
|
|
Chris@36
|
43 Front-end changes:
|
|
Chris@36
|
44
|
|
Chris@36
|
45 - Avoid leaking file descriptors on exceptions
|
|
Chris@36
|
46 - Fix embarrassing bug that caused failure to mix down to mono
|
|
Chris@36
|
47 properly for single-channel plugins with multi-channel input files
|
|
Chris@36
|
48 - Fail sooner if the output file is not writable (i.e. don't wait
|
|
Chris@36
|
49 until the first data is available for writing)
|
|
Chris@23
|
50
|
|
Chris@27
|
51 Changes in Sonic Annotator 0.4 since the previous release 0.3:
|
|
Chris@27
|
52
|
|
Chris@27
|
53 Build changes:
|
|
Chris@27
|
54
|
|
Chris@27
|
55 - Sonic Annotator now requires the Vamp plugin SDK v2.1 or newer.
|
|
Chris@27
|
56
|
|
Chris@27
|
57 Front-end changes:
|
|
Chris@27
|
58
|
|
Chris@28
|
59 - Frequency-domain plugins now use the PluginInputDomainAdapter's new
|
|
Chris@28
|
60 ShiftData processing method, ensuring that the first block received
|
|
Chris@28
|
61 by the plugin is the one centred on 0 rather than starting at 0.
|
|
Chris@28
|
62 Unfortunately, the old behaviour omitted a timing compensation step,
|
|
Chris@28
|
63 and this fix actually changes the results from some plugin processes:
|
|
Chris@28
|
64 the previous behaviour was not always in line with the Vamp plugin
|
|
Chris@28
|
65 specification.
|
|
Chris@28
|
66
|
|
Chris@27
|
67 - More useful diagnostics are now available when a plugin fails to
|
|
Chris@28
|
68 load or run.
|
|
Chris@27
|
69
|
|
Chris@27
|
70 CSV back-end (feature writer) changes:
|
|
Chris@27
|
71
|
|
Chris@27
|
72 - The CSV writer now closes its output files properly when it
|
|
Chris@27
|
73 finishes writing to each one, rather than leaving them all open
|
|
Chris@27
|
74 until the end and risk running out of file descriptors. This was
|
|
Chris@27
|
75 already the behaviour of the RDF writer, the CSV one has just been
|
|
Chris@27
|
76 updated to match it.
|
|
Chris@27
|
77 - The behaviour of the CSV writer has also been changed to match
|
|
Chris@27
|
78 that of the RDF writer in handling file write failures (it now
|
|
Chris@27
|
79 continues processing only if --force is given).
|
|
Chris@27
|
80
|
|
Chris@27
|
81
|
|
Chris@27
|
82 Changes in Sonic Annotator 0.3 since the previous release 0.2:
|
|
Chris@23
|
83
|
|
Chris@23
|
84 Front-end changes:
|
|
Chris@23
|
85
|
|
Chris@23
|
86 - A new --force front-end option (distinct from the --csv-force and
|
|
Chris@23
|
87 --rdf-force back-end options) has been added, which makes Sonic
|
|
Chris@23
|
88 Annotator continue to process subsequent audio files instead of
|
|
Chris@23
|
89 exiting after an error, if multiple audio files have been specified.
|
|
Chris@23
|
90
|
|
Chris@23
|
91 RDF back-end (feature writer) changes:
|
|
Chris@23
|
92
|
|
Chris@23
|
93 - The RDF writer now conforms more correctly with the Music Ontology
|
|
Chris@23
|
94 in the way it relates signal, track, and track metadata. Signals
|
|
Chris@23
|
95 that have available metadata now gain a Track resource to associate
|
|
Chris@23
|
96 that metadata with, instead of hanging it directly from the Signal
|
|
Chris@23
|
97 resource; also the audio file now encodes the signal rather than the
|
|
Chris@23
|
98 signal being available as the audio file (matching the domain
|
|
Chris@23
|
99 specification of the Music Ontology). Note that this new resource
|
|
Chris@23
|
100 structure will not be properly read by versions of Sonic Visualiser
|
|
Chris@23
|
101 prior to 1.6 (should importing the data into Sonic Visualiser be of
|
|
Chris@23
|
102 interest to you).
|
|
Chris@23
|
103
|
|
Chris@23
|
104 - The --rdf-signal-uri option has been removed and replaced with the
|
|
Chris@23
|
105 more meaningful set of options --rdf-audiofile-uri, --rdf-track-uri,
|
|
Chris@23
|
106 and --rdf-maker-uri.
|
|
Chris@23
|
107
|
|
Chris@23
|
108 - A new --rdf-network option is available, to cause Sonic Annotator
|
|
Chris@23
|
109 to try to retrieve RDF descriptions for plugins from the network
|
|
Chris@23
|
110 where those descriptions are not available locally. Use of this
|
|
Chris@23
|
111 option is recommended, but it is not the default because of the
|
|
Chris@23
|
112 possible performance implication (even though the results are mostly
|
|
Chris@23
|
113 cached, there may be some network access involved).
|
|
Chris@23
|
114
|
|
Chris@23
|
115 - The RDF writer now writes the computed_by property for signal
|
|
Chris@23
|
116 features.
|
|
Chris@23
|
117
|
|
Chris@23
|
118 - Plugin and output URIs in the resulting RDF are now percent-encoded.
|
|
Chris@23
|
119
|
