Quote:
Originally Posted by Klangfarben
Two responses to this:
One, they are very different animals. CC information is completely independent of note events. Velocity is always tied to note events. In a CC lane, deleting/editing information never affects note events. In the velocity lane it always affects note events. So the editing processes are always going to be different animals. For example, how often are you going to want to reset CC to an original value in the CC lane? Probably not much. In the velocity lane? That is more critical. Setting all velocities to the same value? Much more critical in the velocity lane than the CC lane. Just because they share some functions does not mean they aren't different animals. They are and they should be treated that way.
Two, if you want to have the same standard actions in the velocity lane vs other CC lanes, you can absolutely do that. Just make the modifiers the same in the CC Lane mouse modifiers and the Velocity lane modifiers. It will function exactly the same. And you only have to set it once and be done. Every other way of trying to solve this is going to get convoluted and overly complicated. This doesn't. It is simply adding another mouse modifier (among many, many other mouse modifier categories) and allowing the user to dictate the behavior. Want it to be the exact same behavior as the CC lanes? Just set it that way. Want it to be different? Set it different.
|
Good points.
2 other differences between Velocities and CCs are that Velocities are polyphonic and CCs aren't -- by this I mean you can't have multiple CC points at the same exact time whereas you can have multiple Velocities... like on a chord. Also, Velocities are never interpolated since they are not continuous (and are not continuous controllers)... whereas CCs can be.
Having an eraser tool to erase (say) a single stacked velocity at a time would be an expected behavior IMHO.