Jump to content

.NGR loop variable speed processing


Zam
 Share

Recommended Posts

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 :confused:

Is there some priority or something with .NGR and section call?

 

Best

Zam

 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...