comparison CHANGELOG @ 23:1a9ad8f3a98f

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