Le mardi 29 novembre 2011 à 21:23:00, Tom Breton (Tehom) a écrit : > >At first I also thought that it'd require radical changes. But then it >occurred to me that there's a 90% solution that doesn't require radical >changes. It just uses segments instead of creating new structures, >commands, and functionality. I'll outline it:
I don't exactly know when a change become a radical one so maybe I'm totally wrong, but here is an other way which could solve the problem and is, I think, more user friendly. What we need is a way to multiplex the controllers over the midi channel. Each time the sequencer reads an event, it should be able to read the Id of the related segment. Then the sequencer may maintain a table of the current controllers for each segment, a table of last controllers on each midi channel and memorize the segment of the last event written on each midi channel. Each time the sequencer gets a new event it compares its segment to the segment of the last controller sent of the midi channel and, if necessary, sends again a controller from the table related to the segment just before the event. The advantage of this method is to authorize an easy use of controllers on a segment even if the same controllers are used on other segments connected to the same instrument. The drawback is the need to do most of the work, if not all the work, in real time inside the sequencer. Nevertheless a midi sequencer is slow compared to an audio processor. So maybe this is not totally unworkable. That's just a thought I had while reading your mail and I don't take the time to study it extensively. Yves ------------------------------------------------------------------------------ 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
