On 05/30/2014 09:46 PM, Tres Finocchiaro wrote:
>
>
> > No, not necessarily. Why would it?
> >
> > Only if we wanted to convert them to work in that way, which could
> be done, but would require more backwards-compat code.
>
> Why would it? It just seems like the natural progression of things.
> Is this not what you had in mind for a dedicated tempo automation track?
>
Well, I mostly addressed this in my earlier post, maybe you missed it:
> Well, my thoughts on this are, that I'm entirely in favor of making the
> global automation tracks more visible. From a UI standpoint, that would
> be a big improvement, as it would improve their usability and
> discoverability a lot. I've actually suggested doing something like this
> earlier...
>
> As far as the tempo automation though... *using global automation track
> for tempo could work, if we made it so that you could only use that
> track for tempo automation. The whole idea of the tempo track was that
> there's only one place where tempo automation can be*, so as to simplify
> the task of determining what the tempo is at any given position...
>
> However, personally I'd still prefer a dedicated tempo track. Global
> auto tracks are a bit tricky because you can't use patterns in them,
> they're just one long stretch of a pattern, which makes it a bit harder
> to add automation at a specific point in the song (you have to look up
> the position in timeline, match it up with the automation editor, etc.).
> Additionally, a track with discrete patterns would make it easier to
> determine whether a given piece of the project has any tempo automation,
> which would help with optimizations (eg. for the drawing code of the new
> sampletracks: we can ignore the tempo-aware stuff and use simpler
> drawing if there's no tempo automation overlapping with the pattern).
So, to recap: we could use a global auto track for tempo, but we'd have
to change them so that they support patterns, and we'd also have to make
it so that you can only automate tempo in the global track. That might
seem inconsistent in that it would then function differently than all
the other global automation tracks.
Also from a UI design standpoint I think that'd be a bit tricky because
the global tracks are only accessible from context menus. A dedicated
tempo track would have better discoverability.
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
