|
Chris@23
|
1
|
|
Chris@23
|
2 Changes in Sonic Annotator 1.3 since the previous release 1.2:
|
|
Chris@23
|
3
|
|
Chris@23
|
4 Front-end changes:
|
|
Chris@23
|
5
|
|
Chris@23
|
6 - A new --force front-end option (distinct from the --csv-force and
|
|
Chris@23
|
7 --rdf-force back-end options) has been added, which makes Sonic
|
|
Chris@23
|
8 Annotator continue to process subsequent audio files instead of
|
|
Chris@23
|
9 exiting after an error, if multiple audio files have been specified.
|
|
Chris@23
|
10
|
|
Chris@23
|
11 RDF back-end (feature writer) changes:
|
|
Chris@23
|
12
|
|
Chris@23
|
13 - The RDF writer now conforms more correctly with the Music Ontology
|
|
Chris@23
|
14 in the way it relates signal, track, and track metadata. Signals
|
|
Chris@23
|
15 that have available metadata now gain a Track resource to associate
|
|
Chris@23
|
16 that metadata with, instead of hanging it directly from the Signal
|
|
Chris@23
|
17 resource; also the audio file now encodes the signal rather than the
|
|
Chris@23
|
18 signal being available as the audio file (matching the domain
|
|
Chris@23
|
19 specification of the Music Ontology). Note that this new resource
|
|
Chris@23
|
20 structure will not be properly read by versions of Sonic Visualiser
|
|
Chris@23
|
21 prior to 1.6 (should importing the data into Sonic Visualiser be of
|
|
Chris@23
|
22 interest to you).
|
|
Chris@23
|
23
|
|
Chris@23
|
24 - The --rdf-signal-uri option has been removed and replaced with the
|
|
Chris@23
|
25 more meaningful set of options --rdf-audiofile-uri, --rdf-track-uri,
|
|
Chris@23
|
26 and --rdf-maker-uri.
|
|
Chris@23
|
27
|
|
Chris@23
|
28 - A new --rdf-network option is available, to cause Sonic Annotator
|
|
Chris@23
|
29 to try to retrieve RDF descriptions for plugins from the network
|
|
Chris@23
|
30 where those descriptions are not available locally. Use of this
|
|
Chris@23
|
31 option is recommended, but it is not the default because of the
|
|
Chris@23
|
32 possible performance implication (even though the results are mostly
|
|
Chris@23
|
33 cached, there may be some network access involved).
|
|
Chris@23
|
34
|
|
Chris@23
|
35 - The RDF writer now writes the computed_by property for signal
|
|
Chris@23
|
36 features.
|
|
Chris@23
|
37
|
|
Chris@23
|
38 - Plugin and output URIs in the resulting RDF are now percent-encoded.
|
|
Chris@23
|
39
|
