log src/TuningDifference.h @ 69:c0b78dcc08e6 feature-alternatives tip

age author description
Thu, 11 Jul 2019 09:58:56 +0100 Chris Cannam Revert to having only a single plugin - I think this should be sufficiently backward compatible after all base src/BulkTuningDifference.h@53bec40aeffe
Tue, 09 Jul 2019 16:14:19 +0100 Chris Cannam Add BulkTuningDifference plugin
Tue, 09 Jul 2019 15:09:33 +0100 Chris Cannam Switch from 60bpo to 120 - seems to work better (?) with little performance downside. Also avoid recalculating second feature if not needed for fine tuning, and extend regression test
Thu, 13 Jun 2019 11:32:01 +0100 Chris Cannam Make fine tuning optional; wire up forgotten max range option!
Thu, 16 May 2019 15:56:07 +0100 Chris Cannam Couple more parameters
Fri, 27 Mar 2015 17:20:40 +0000 Chris Cannam Add max-duration parameter. The results are often going to be quite wrong if you use this, simply because the two performances may be at different speeds and so the same duration of each may represent a different (sub-)performance. But it's sometimes necessary just to avoid blowing the thing up.
Thu, 05 Feb 2015 10:13:31 +0000 Chris Cannam Rearrange code, include subrepo etc base chroma-compare-plugin/TuningDifference.h@7d5fc5391491