I had misspoken when I called the automation track a controller, sorry.
Yes, limiting the tempo changes to only one automation track is what I was
attempting to describe and I understand after your explanation why that may
not be as easy as suggested.
Conceptually, its still difficult because automation events are often a
line in the sand that must be crossed to have an effect, so weird things
will happen when the event is missed (as does now if an event is missed),
but the act of "looking ahead at automation" is quite confusing when
combined with elements that don't naturally look ahead, i.e. sample tracks
playing at the right tempo while the rest of the track plays at the wrong
tempo.
This really does open up Pandora's box so to speak.
------------------------------------------------------------------------------
"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
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
