On Thursday, December 01, 2011, Tom Breton (Tehom) wrote: > I'd like to hear it. I'm certainly not wedded to doing what I proposed. > If there's a better way I'm all ears.
I'm just starting to see the edges of this idea, but what if segments, rather than tracks, owned the instrument? A segment would take a default instrument from the track in the same way it takes a default "create segments with" color, highest and lowest playable notes, transposition, clef, etc., but once it existed, it would maintain its instrument independently of whatever track it landed on, in the same way it owns its other properties. We talked about doing this once before, for an entirely different reason that I'll skip discussing for the sake of focus. We never felt it was worth the pain to implement, but the concept is basically plausible. In that kind of world, how does this controller problem look different? Could moving the instrument to the segment allow us to deal with the controller issue in a more elegant manner than your proposal, which you admitted was "philosophically" awkward? I'm not sure, and I'm ridiculously ready for bed just now, but I'd like to mull this over with you and see if it leads anywhere interesting. -- D. Michael McIntyre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
