Hello > See it like this, if we want a smooth CC change there would be ALOT of > dots visually represented that somehow would get hard to work with, as > if we check on the TempoRuler > there as keypoints but a tempochange is sent between 2 keypoints when a > "ramp" is used... > That is what i mean, think of handling CC as the temporuler with > keypoints.
Ok, now I got it. Much like Ardours automation. That would visually be the best approach that I can currently think of, that could be doable. Technically maybe not so easy. But let's wait for the qt4 first.. >> 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
