annotate CHANGELOG @ 127:f0df07da6f46

Update version, add --minversion flag
author Chris Cannam
date Thu, 09 Oct 2014 12:56:55 +0100
parents 52e5e2c03792
children c24270fc6635
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@127 8 - Add --normalise to request each audio file be normalised to 1.0 max
Chris@127 9 - Add --multiplex
Chris@71 10
Chris@86 11 Changes in Sonic Annotator 1.0 since the previous release 0.7:
Chris@71 12
Chris@87 13 Bug fixes:
Chris@87 14
Chris@71 15 - Fix incorrect samplerate in reading m4a files on OS/X
Chris@73 16 - Fix incorrect handling of FixedSampleRate outputs (Vamp SDK fix)
Chris@86 17 - Add tests that use the Vamp test plugin
Chris@65 18
Chris@65 19 Changes in Sonic Annotator 0.7 since the previous release 0.6:
Chris@65 20
Chris@65 21 Build changes:
Chris@65 22
Chris@65 23 - Support 64-bit builds on OS/X (using CoreAudio instead of
Chris@65 24 obsolete QuickTime audio file reader)
Chris@65 25
Chris@65 26 - Simplify RDF reading and fix some bugs. Now requires Dataquay
Chris@65 27 (http://breakfastquay.com/dataquay/) rather than using Redland
Chris@65 28 directly. Release builds use Sord/Serd rather than Redland
Chris@49 29
Chris@49 30 Changes in Sonic Annotator 0.6 since the previous release 0.5:
Chris@49 31
Chris@49 32 Build changes:
Chris@49 33
Chris@49 34 - Switch to modular SV-libraries build using svcore library
Chris@53 35 - We now require Vamp plugin SDK v2.3
Chris@49 36 - Add autoconf configure script
Chris@49 37
Chris@49 38 Front-end changes:
Chris@49 39
Chris@49 40 - Pick up default sample rate and channel count from the first
Chris@49 41 audio file, where not specified in the transform, instead of using
Chris@49 42 hard coded defaults
Chris@53 43 - Make it possible to specify the window shape in transform
Chris@49 44 - Fix the --csv-one-file option which did not work in 0.5
Chris@49 45 - Fix --force option when using playlists
Chris@49 46 - Add -v option to print version number and exit
Chris@36 47
Chris@36 48 Changes in Sonic Annotator 0.5 since the previous release 0.4:
Chris@36 49
Chris@36 50 Build changes:
Chris@36 51
Chris@36 52 - Remove unused audioio library and avoid its dependencies
Chris@36 53
Chris@36 54 Front-end changes:
Chris@36 55
Chris@36 56 - Avoid leaking file descriptors on exceptions
Chris@36 57 - Fix embarrassing bug that caused failure to mix down to mono
Chris@36 58 properly for single-channel plugins with multi-channel input files
Chris@36 59 - Fail sooner if the output file is not writable (i.e. don't wait
Chris@36 60 until the first data is available for writing)
Chris@23 61
Chris@27 62 Changes in Sonic Annotator 0.4 since the previous release 0.3:
Chris@27 63
Chris@27 64 Build changes:
Chris@27 65
Chris@27 66 - Sonic Annotator now requires the Vamp plugin SDK v2.1 or newer.
Chris@27 67
Chris@27 68 Front-end changes:
Chris@27 69
Chris@28 70 - Frequency-domain plugins now use the PluginInputDomainAdapter's new
Chris@28 71 ShiftData processing method, ensuring that the first block received
Chris@28 72 by the plugin is the one centred on 0 rather than starting at 0.
Chris@28 73 Unfortunately, the old behaviour omitted a timing compensation step,
Chris@28 74 and this fix actually changes the results from some plugin processes:
Chris@28 75 the previous behaviour was not always in line with the Vamp plugin
Chris@28 76 specification.
Chris@28 77
Chris@27 78 - More useful diagnostics are now available when a plugin fails to
Chris@28 79 load or run.
Chris@27 80
Chris@27 81 CSV back-end (feature writer) changes:
Chris@27 82
Chris@27 83 - The CSV writer now closes its output files properly when it
Chris@27 84 finishes writing to each one, rather than leaving them all open
Chris@27 85 until the end and risk running out of file descriptors. This was
Chris@27 86 already the behaviour of the RDF writer, the CSV one has just been
Chris@27 87 updated to match it.
Chris@27 88 - The behaviour of the CSV writer has also been changed to match
Chris@27 89 that of the RDF writer in handling file write failures (it now
Chris@27 90 continues processing only if --force is given).
Chris@27 91
Chris@27 92
Chris@27 93 Changes in Sonic Annotator 0.3 since the previous release 0.2:
Chris@23 94
Chris@23 95 Front-end changes:
Chris@23 96
Chris@23 97 - A new --force front-end option (distinct from the --csv-force and
Chris@23 98 --rdf-force back-end options) has been added, which makes Sonic
Chris@23 99 Annotator continue to process subsequent audio files instead of
Chris@23 100 exiting after an error, if multiple audio files have been specified.
Chris@23 101
Chris@23 102 RDF back-end (feature writer) changes:
Chris@23 103
Chris@23 104 - The RDF writer now conforms more correctly with the Music Ontology
Chris@23 105 in the way it relates signal, track, and track metadata. Signals
Chris@23 106 that have available metadata now gain a Track resource to associate
Chris@23 107 that metadata with, instead of hanging it directly from the Signal
Chris@23 108 resource; also the audio file now encodes the signal rather than the
Chris@23 109 signal being available as the audio file (matching the domain
Chris@23 110 specification of the Music Ontology). Note that this new resource
Chris@23 111 structure will not be properly read by versions of Sonic Visualiser
Chris@23 112 prior to 1.6 (should importing the data into Sonic Visualiser be of
Chris@23 113 interest to you).
Chris@23 114
Chris@23 115 - The --rdf-signal-uri option has been removed and replaced with the
Chris@23 116 more meaningful set of options --rdf-audiofile-uri, --rdf-track-uri,
Chris@23 117 and --rdf-maker-uri.
Chris@23 118
Chris@23 119 - A new --rdf-network option is available, to cause Sonic Annotator
Chris@23 120 to try to retrieve RDF descriptions for plugins from the network
Chris@23 121 where those descriptions are not available locally. Use of this
Chris@23 122 option is recommended, but it is not the default because of the
Chris@23 123 possible performance implication (even though the results are mostly
Chris@23 124 cached, there may be some network access involved).
Chris@23 125
Chris@23 126 - The RDF writer now writes the computed_by property for signal
Chris@23 127 features.
Chris@23 128
Chris@23 129 - Plugin and output URIs in the resulting RDF are now percent-encoded.
Chris@23 130