Hi Vesa and others, thank you for your suggestions and discussion! It took me a while to read at least thouroughly over what has been written. I also vote for implementing a dedicated tempo track. The current approach simply "was there" after implementing automation support at all -> basic tempo control (actually a dedicated feature) has been working quite well without any additional work - how cool is that? ;-) Nevertheless we should go the next step here and consolidate and improve things. What we have to take care of is to implement proper compat code which merges existing tempo automations into the global tempo automation track.
It just came to my mind that we could think about re-using the global automation pattern feature. If we change it that way that all global automations (as soon as more than one value is set) appear as individual tracks it improves visibility a lot while at the same time we don't have to care about tempo automation specifically. We could introduce a more generic "GlobalAutomationTrack" which per definition has just one automation pattern (beginning at 0) which would simplify things a lot. Toby ------------------------------------------------------------------------------ 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
