Maybe the automated tempo time calculation could be aided with maintaining
a time table.
LMMS would store lenght in msec. of each bar in the song in a list.
Updating the list by finding regions affected by added/changed tempo
automation would be done and time for each point in the project's timeline
would be calculated by adding all previous bar times together and adding
the sub-bar offset.
On 7 Feb 2014 17:23, "Vesa" <[email protected]> wrote:
> On 02/07/2014 06:15 PM, Alexandre Almeida wrote:
>
> The best solution to get correct time values when the tempo is automated
> is to read the tempo at the cursor position from the automation track. It
> is also interesting to update the tempo value shown in the GUI.
>
> Not that simple I'm afraid. What if the user moves the cursor around?
> You'd have to calculate all the tempo automations since the beginning of
> the track.
>
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> LMMS-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
