Hello > I'm reading up on all discussions and realize that i shouldn't put more > time into this before we have moved to qt4.
Now that I recall, I came to the same conclusion that I should wait for the qt4 version, before modifying the control rulers thingy. > Another thought of CC is this, a CC is an controlchange at a specified > time and will affect the controller constantly thru time to next CC > appear so another approach of working with CC is: > > Work with controllervalues as with the tempo ruler, a line representing > the actual controlvalue > thru the whole segement, and let the user create controlpoints @ free or > snapped to grid forming a line of the control changes. ++votes for that, kind of what was on my mind at some point, but the lack of devotion drove to the quick and easy diamond solution > Also a define "sample" rate for getting value of the line @ time for > sending it to midi channel, if value at sampletime equals the previous > value, dont send a midi CC... --votes for this, why complicate things, internally events are sent at a certain specific time and the visuals can be a continuous line with dots/diamonds at the event position, or whatever we come up with. I don't see any reason for this. Tommi ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
