svictor
Registered
Good points, it actually only needs a few numbers changed to get smooth jump between each impulse.
Here is a new completely nonlinear example tested on Skip barber, with smoothed/pseudo-randomized needle movement between each impulse:
Since GIF has low frame rate/file size limitation, here is link to original 60fps video which the smoothed/randomized impulse effect is more noticeable:
https://we.tl/t-rzFjE2eaeg
Each "fake" impulse is now set at a roughly(randomized) 500 to 1000 RPM range step, with upper bound override value set 100 RPM below next lower bound override value, this which smoothed out needle jumping effect (as the extra 100 RPM range) and made the impulse effect more natural looking now.
Further randomization is also possible with smaller or bigger RPM step (impulse gap). Mixing smaller steps with bigger steps can also create some sort of fluctuation effect as shown from above GIF.
Here is the new code with comments indicating each step range:
No worries about auto-tools. I'll probably find some time to write a script to allow auto-generating above code with a few parameters that can be adjustable by other users, such as "step range", "randomized range", "smooth range", etc.
Here is a new completely nonlinear example tested on Skip barber, with smoothed/pseudo-randomized needle movement between each impulse:
Since GIF has low frame rate/file size limitation, here is link to original 60fps video which the smoothed/randomized impulse effect is more noticeable:
https://we.tl/t-rzFjE2eaeg
Each "fake" impulse is now set at a roughly(randomized) 500 to 1000 RPM range step, with upper bound override value set 100 RPM below next lower bound override value, this which smoothed out needle jumping effect (as the extra 100 RPM range) and made the impulse effect more natural looking now.
Further randomization is also possible with smaller or bigger RPM step (impulse gap). Mixing smaller steps with bigger steps can also create some sort of fluctuation effect as shown from above GIF.
Here is the new code with comments indicating each step range:
Code:
//------------ Fully nonlinear RPM Step Example: roughly 500-1000 RPM for each impulse
//------------ Target RPM: 0, Override: 0 - 659, Step: 759, Smooth RPM range: 100 (659 - 760)
TachometerNonlinear=(0,0)
TachometerNonlinear=(659,0)
//------------ Target RPM: 760, Override: 760 - 1519, Step: 859, Smooth RPM range: 100 (1519 - 1620)
TachometerNonlinear=(760,760)
TachometerNonlinear=(1519,760)
//------------ Target RPM: 1620, Override: 1620 - 2474, Step: 954, Smooth RPM range: 100 (2474 - 2575)
TachometerNonlinear=(1620,1620)
TachometerNonlinear=(2474,1620)
//------------ Target RPM: 2575, Override: 2575 - 3236, Step: 761
TachometerNonlinear=(2575,2575)
TachometerNonlinear=(3236,2575)
//------------ Target RPM: 3337, Override: 3337 - 4409, Step: 1172
TachometerNonlinear=(3337,3337)
TachometerNonlinear=(4409,3337)
//------------ Target RPM: 4510, Override: 4510 - 4888, Step: 478
TachometerNonlinear=(4510,4510)
TachometerNonlinear=(4888,4510)
//------------ Target RPM: 4989, Override: 4989 - 5664, Step: 775
TachometerNonlinear=(4989,4989)
TachometerNonlinear=(5664,4989)
//------------ Target RPM: 5765, Override: 5765 - 6073, Step: 408
TachometerNonlinear=(5765,5765)
TachometerNonlinear=(6073,5765)
//------------ Target RPM: 6174, Override: 6174 - 7304, Step: 1130
TachometerNonlinear=(6174,6174)
TachometerNonlinear=(7304,6174)
No worries about auto-tools. I'll probably find some time to write a script to allow auto-generating above code with a few parameters that can be adjustable by other users, such as "step range", "randomized range", "smooth range", etc.
Attachments
Last edited: