On 05/31/2014 05:26 PM, Tobias Doerffel wrote: > Hi, > > I like and support this idea! I wonder how we could integrate that > with existing model automation and/or the InlineAutomation class > (which in turn is used by DetuningHelper) so we actually do not have > to rewrite that much functionality. The downside: editing > InlineAutomation objects currently is only possible using > AutomationEditor. Therefore we could maybe refactor the > AutomationEditor core part such that it can be embedded as widget in > the piano roll. What do you think about this? >
Well, part of my original idea was that we'd use the same controls as we use for note volume/panning, this way the values would be easy to set for each note. That would only support static, once-per-note values for notes though, which is a bit of a downside, but it would be simpler from a UI standpoint. Using actual inline automations would be more flexible and allow more control, but we'd need some UI changes - like you said, embedding automation editor in piano roll would be one way of doing that. Maybe even so that you can edit the curves directly in the piano roll, kind of like how the piano roll now displays the pitch curves for the notes, maybe you could select a tool and then you could move the vertexes of the automation directly on the piano roll... ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
