Its not so much about playing straight through as it is about clicking
ahead in a track. In order for the sample track to play at the proper
moment requires iterating through the automation controllers to find out
where the actual play time should start from.
See, when you play a sample track from the beginning it just naturally
plays through until finished, however jumping onto it from some other
position begs the question "where would this sample have been playing
from?". It also causes other problems, such as the waveform being inn
inaccurate unless it is redrawn at a "stretch" representing the tempo at
that given time.
Vesa is asking if we can strip out all standard automation on tempo so that
this can all be calculated properly with a dedicated tempo automation track.
I don't disagree fundamentally although I'd vote we instead have a
max-automation events property for it and just lock it from being dragged
to more than one controller.
But I'm not capable of coding this feature so my opinion is moot.
------------------------------------------------------------------------------
"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
