Hi all
In addition to my moving fader system (soon released), I write some alternative NGC/NGR for various stand alone calibration process like PID tuning and Touch sensitivities.
For the “touch calibration” NGC/NGR I write a loop section with incremental value activated by a button that automatically move the fader (CV output) up and down, in order to see when the touch calibration pot bypass the motor driver (or not)
here is the section for fader 1 (CV3 due to HW layout):
if ^section == 1 if BUTTON:6 == 127 set CV:3 [CV:3+10] if CV:3 \>= 16200 set BUTTON:6 126 endif delay\_ms 1 exec\_meta RunSection:1 endif if BUTTON:6 == 126 set CV:3 [CV:3-10] if CV:3 \<= 200 set BUTTON:6 127 endif delay\_ms 1 exec\_meta RunSection:1 endif if BUTTON:6 == 0 set CV:3 0 endif exit endif
It work fine, but I have a strange behaviour between various fader (8 in total)
More I go up in fader activation, from 1 to 8, more the fader is slow !!! despite the exact same incremental/decremental math and delay, which is theoretically around 1.6sec full travel here (14 bit / 16383 steps with 10steps each ms –>1600ms), 3.2sec for the full up and down wave.
It’s not a big problem for me in this use case, I just need to see if fader move or not, speed is not so important but I like to understand why
Is there some priority or something with .NGR and section call?
Best
Zam