On 03/30/2014 08:33 PM, Tobias Doerffel wrote: > Hi, > > sounds like an innovative concept - and maybe ambitious at the same > time when it comes to achieving 100% backward compatibility. > Nevertheless this should be nothing we could not manage. > > More thoughts: > - the note effects should show all controls and UI elements inline > i.e. no "control" button which opens another window -> same usability > but eventually with greater flexibility
Yes - that is exactly what I thought also :) Furthermore... If you add in regular effects in the note fx chain, they would show with the regular panel with the "control" button, but the note effects themselves would have inline GUIs. I'm not sure yet how to implement the "move up/down" for the inline GUIs... maybe they'd have a "toolbar" of sorts that you can right click for context menu, or maybe a toolbutton in the corner? (Unrelated: the move up/down by context menu is actually kind of clunky, I'm thinking we could change that to some kind of move grip so you could move effects the same way you move tracks in song editor) > - the existing env/lfo feature could be part of a "legacy > envelope/LFO" plugin which gets loaded for old projects. for new > projects we could provide a new and revised envelope/LFO plugin. Yep. I'm thinking, divide the existing ENV/LFO into two parts: - Volume envelope + LFO - Filter + envelope + LFO Then these two would always be loaded to legacy projects (but could also be used in new projects if the user wants to). The user could then choose which ENV/LFO to use. We could call the old one "Classic ENV/LFO"... For new projects, I'm thinking the ENV/LFO tab would be empty by default, with just a button that reads "add note effect", the user could then choose which of them to add. Game plan: I'm thinking, we could start development of this in a separate branch, at some point. I don't know if I'm capable of doing the architecural changes in core code, but I could help by coding some of the new plugins (I do code lots of plugins these days...) once we have some codebase to code them against. Then when we have something functional in that branch, we could merge that to master, where it would eventually be merged to a stable branch - whatever that may be at that point. ------------------------------------------------------------------------------ _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
