annotate CHANGELOG @ 172:64a7faf9a122

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