|
Tap Tempo-patches are patches, where you tap e.g. on a button and the speed of you tapping sets the tempo. Below the basic TapTempo-patch from the manual (I added an OSC and and Envelope to make it audible), and below that an explanation why it works by Rob Hordijk on the newslist.
The ZeroCounter actually has different 'code' for a red input or a blue input. If the input is red, like from an osc output, the control value output will make another osc 'set to its default values' (+/-330 Hz) track exactly if connected to the direct pitch input. And if the input is a blue signal from an LFO, it will make another LFO 'set to its default values' (0,64Hz) track exactly, again when connected to the LFO direct rate input. So, if you connect a pushbutton to the ZeroCounter (which has a blue output) the tapping will act like it came from another LFO. The ZeroCounter holds the last measured output value steady until a new measured value becomes available. So, the output value is always the 'time' in between the last two taps. Which is the reason that the output value in between the first two taps is basically 'undefined' and is only correct after the second tap. Set the LFO to 1.28 or 2.56 Hz to have it run at twice or four times the tapping rate. The reason why there is different 'code' for a red and a blue input signal is because the blue sample rate is 'two octaves down' compared to the red sample rate, but the range of an LFO is 'nine octaves down' compared to the range for an oscillator (330 Hz versus 0,64 Hz). But of course a ZeroCounter should work correctly for both oscillators and LFOs, and the difference between the 'red input code' and 'blue input code' make sure it does.
|
