trigger to sample latency

the firmware features adjustable trigger-to-sample latency, which can be useful especially when re-quantizing stepped voltages (like from a sequencer). in such cases, to achieve the desired result (= sampling the target voltage level, rather than some intermediate level), it can make sense to increase the processing latency of the CV2midi module in order to account for variations in slew/delay/settling times in combination with various upstream modules / devices.

to adjust the trigger-to-sample latency, do the following:

• long press the "learn" button (the 'learn'-LED will start to blink).
• push the "learn" button to cycle through the six available latency settings (indicated by the channel-LEDs):
  • all LEDs off = minimum latency (~ 66.6 us)
  • all LEDs on = maximum latency (~ 1.5 ms)
  • or values in between (1 LED = ~ 250us ; 2 LEDs = ~ 500us ; 3 LEDs = ~ 750us ; 4 LEDs = ~ 1ms)
• long press the "learn" button again to select + save settings.

NB

• there's a few sequencers out there that are notoriously slew-y, so if you find that 1.5ms isn't enough, you'll have to increase the max. latency in the code and recompile. to do this, you simply have to adjust the trigger_delay_ticks array in APP_CV2MIDI.ino. the numbers in the array are given in 'ticks' (1 tick = 66.6us), so to, say, double the above latency values, you'd double said tick values, ie:

const uint8_t trigger_delay_ticks[NUM_CHANNELS + 0x1] = { 0, 8, 16, 24, 32, 48 }