For some devices, the parameter moves even when the tool tip value doesn't (when using Shift). This can happen because many knobs only have 63 frames in the visual 'animation', but at LEAST 127 values at the parameter.
This also happens for controls that have 1000 values, such as many of the SSL mixer controls (faders and EQ frequencies for example).
There are also floating point controls, I recently gave an example of how Selig Gain can have levels set down to 0.000001dB resolution by automating the fader and typing in the value. Many other REs do the same, but you have to figure it out for yourself by trying the "edit trick".
So while the edit parameter is equal steps (127 or 1000 total) the parameters they control are not always going to move in equal amount (boo). For example, for the SSL faders every step is a different decibel amount. This is why you can't scale automation in Reason accurately, as it changes the relationship between values. For example, a 3dB automation change won't be 3dB if you drag all the automation points up/down, a major deal breaker for mix automation IMO.
Basically each decibel is around 1 more "1-000" step apart the higher you go. At the top (+8dB) you have around 36 steps per decibel (it's not exact), and even just down at -10dB you have only 20 steps.
While the resolution is still nice and high, way more than you need regularly (1/20th of a dB), it's not consistent. So if you scale an automation move down by a few dB, you have changed the decibel relationship between the points - literally no other DAW I've ever seen does this.

For reverence, here's a chart I made years ago for converting values from 0-127 (14:2 mixer, etc) to the SSL 0-1000.
![Image]()
You do not have the required permissions to view the files attached to this post.