I've committed the recent refactoring etc. Ted, I can guarantee that
TempoSkew won't fail to compile because it no longer exists.
To put it thru its paces, try adding a timesignature with a swing
(checkbox in time sig dialog). Also range cutting and
tempo×ig-pasting are more airtight, just to support this stuff
reasonably.
New in this commit:
* A ton of refactoring. I figured I should make the new stuff nice
while it's young and manageable.
* Add or improved (I hope) comments for most of the new stuff.
* The tempo curves it makes are fixed to be monotonic. Technical,
but I'll try to explain: In my previous commit, it sometimes built
a ramp from (say) 110 qpm to 130 that passed thru 140. Now when
it's all done, it fixes the overall tempo curve so that there is no
overshoot, if possible.
* Technical, but we're doing the cubics in a different way and ISTM
simpler way: Storing the true average tempo and doing
realtime-at-time and tempo-at-time calculations with a Hermite
Spline. It's simpler than you might think. About half the
calculation code went away by doing that.
Now I can finally get to writing the commands Tim suggested.
Tom Breton (Tehom)
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
