annotate CHANGELOG @ 181:c5619f2a63b1

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