| Chris@23 | 1 | 
| Chris@27 | 2 Changes in Sonic Annotator 0.4 since the previous release 0.3: | 
| Chris@27 | 3 | 
| Chris@27 | 4 Build changes: | 
| Chris@27 | 5 | 
| Chris@27 | 6  - Sonic Annotator now requires the Vamp plugin SDK v2.1 or newer. | 
| Chris@27 | 7 | 
| Chris@27 | 8 Front-end changes: | 
| Chris@27 | 9 | 
| Chris@27 | 10  - More useful diagnostics are now available when a plugin fails to | 
| Chris@27 | 11  load or run | 
| Chris@27 | 12  - Frequency-domain plugins now use the PluginInputDomainAdapter's | 
| Chris@27 | 13  new ShiftData processing method, ensuring that the first block | 
| Chris@27 | 14  received by the plugin is the one centred on 0 rather than starting | 
| Chris@27 | 15  at 0: we think this is a better match for normal usage expectations. | 
| Chris@27 | 16 | 
| Chris@27 | 17 CSV back-end (feature writer) changes: | 
| Chris@27 | 18 | 
| Chris@27 | 19  - The CSV writer now closes its output files properly when it | 
| Chris@27 | 20  finishes writing to each one, rather than leaving them all open | 
| Chris@27 | 21  until the end and risk running out of file descriptors.  This was | 
| Chris@27 | 22  already the behaviour of the RDF writer, the CSV one has just been | 
| Chris@27 | 23  updated to match it. | 
| Chris@27 | 24  - The behaviour of the CSV writer has also been changed to match | 
| Chris@27 | 25  that of the RDF writer in handling file write failures (it now | 
| Chris@27 | 26  continues processing only if --force is given). | 
| Chris@27 | 27 | 
| Chris@27 | 28 | 
| Chris@27 | 29 Changes in Sonic Annotator 0.3 since the previous release 0.2: | 
| Chris@23 | 30 | 
| Chris@23 | 31 Front-end changes: | 
| Chris@23 | 32 | 
| Chris@23 | 33  - A new --force front-end option (distinct from the --csv-force and | 
| Chris@23 | 34  --rdf-force back-end options) has been added, which makes Sonic | 
| Chris@23 | 35  Annotator continue to process subsequent audio files instead of | 
| Chris@23 | 36  exiting after an error, if multiple audio files have been specified. | 
| Chris@23 | 37 | 
| Chris@23 | 38 RDF back-end (feature writer) changes: | 
| Chris@23 | 39 | 
| Chris@23 | 40  - The RDF writer now conforms more correctly with the Music Ontology | 
| Chris@23 | 41  in the way it relates signal, track, and track metadata.  Signals | 
| Chris@23 | 42  that have available metadata now gain a Track resource to associate | 
| Chris@23 | 43  that metadata with, instead of hanging it directly from the Signal | 
| Chris@23 | 44  resource; also the audio file now encodes the signal rather than the | 
| Chris@23 | 45  signal being available as the audio file (matching the domain | 
| Chris@23 | 46  specification of the Music Ontology).  Note that this new resource | 
| Chris@23 | 47  structure will not be properly read by versions of Sonic Visualiser | 
| Chris@23 | 48  prior to 1.6 (should importing the data into Sonic Visualiser be of | 
| Chris@23 | 49  interest to you). | 
| Chris@23 | 50 | 
| Chris@23 | 51  - The --rdf-signal-uri option has been removed and replaced with the | 
| Chris@23 | 52  more meaningful set of options --rdf-audiofile-uri, --rdf-track-uri, | 
| Chris@23 | 53  and --rdf-maker-uri. | 
| Chris@23 | 54 | 
| Chris@23 | 55  - A new --rdf-network option is available, to cause Sonic Annotator | 
| Chris@23 | 56  to try to retrieve RDF descriptions for plugins from the network | 
| Chris@23 | 57  where those descriptions are not available locally.  Use of this | 
| Chris@23 | 58  option is recommended, but it is not the default because of the | 
| Chris@23 | 59  possible performance implication (even though the results are mostly | 
| Chris@23 | 60  cached, there may be some network access involved). | 
| Chris@23 | 61 | 
| Chris@23 | 62  - The RDF writer now writes the computed_by property for signal | 
| Chris@23 | 63  features. | 
| Chris@23 | 64 | 
| Chris@23 | 65  - Plugin and output URIs in the resulting RDF are now percent-encoded. | 
| Chris@23 | 66 |