On 05/24/2014 10:16 PM, Tres Finocchiaro wrote: > > > Remember the KISS principle... and as corollary, Murphy's law. The > simpler we keep things, the less potential there is for things to go > horribly wrong... > > Yes, that's why I hinted that not being the one coding makes my UI > requests fairly moot. From a composer's perspective, I never want > discriminatory automation areas, and I certainly don't want more > tracks (the number of average tracks per project is already a problem > in my compositions). Wishful thinking, but I'd vote for a design that > doesn't introduce more tracks. Even if the existing tempo automation > track locks itself from receiving non - automation drags, from my > naive users' world, I would advocate for a solution that keeps what we > already have. >
>From a composer's perspective, I want a solution that works, and gives me accurate timing and automation. I very rarely mix automations of multiple models on the same automation track, because that makes projects harder to read. I get that there's a benefit to it when you only have like a few small simple changes and you want to conserve space. I get the concern about not wanting more clutter in the song editor. However, tempo is a pretty special case... If you're concerned about adding more tracks, we could make it so you can hide/show the tempo track. I think that'd be a better solution, we could keep tempo separate from other automations, and still not have more clutter in projects. Backwards compatibility can be ensured by reading all tempo automations in older projects and copying them onto the tempo track... ------------------------------------------------------------------------------ "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
