Speed Dial Release Time Jul 30, 2008 10:51:15 GMT -5
Post by timur on Jul 30, 2008 10:51:15 GMT -5
You can try it with the B bold button on this forum when posting messages for example. Place the mouse-pointer right beside the B button so that the pointer is just some pixels left to the button and does not turn into a "hand" pointer yet. Then rotate the speed dial clockwise and see how a ]b]]/b] is created by that. That means that the push-button event happened at the end of the movement after the pointer has turned into a hand. Now try the other way around, start at the leftmost inner border of the B button where the pointer turned into a hand and rotate the encoder counterclowise. There is no ]b]]/b] inserted into the message, because the click happens before the movement where the pointer turns into an arrow again.
I guess that’s a matter of perception, but I did say “pretty fine” and that was in relation to the fact that it doesn’t move far enough to change a value on one-click of the encoder.
Well, at least for Live's level and pan controls its even so coarse that several values are jumped by one-click of the encoder (see 0.9 dB vs 0.3 dB).
I think the encoder/mouse should only move by 1 or two pixels diagonally for fine control and either make shift move it faster or if fast movement is the default then make shift move it slower (like when pressing CTRL on the keyboard). But even when coupled with CTRL the encoder still jumps over regular steps:
CC: 1.0 -> 0.9
CW: 0.9 -> 1.0
CW: 1.0 -> 1.2
CC: 1.2 -> 1.1
CW: 1.1 -> 1.2
CW: 1.2 -> 1.4
CC: 1.4 -> 1.3
If necessary I can post some video of all the mentioned behavior.