Frequency Modulation produces different sounds when played all over the keyboard. To compensate for this the Level Scaler with the below setting (a tip from the manual) gives best results.  FMLinExamp.pch2Ah, I've made another example because I forgot I already made this one. Anyway, here you go: The use of the LevelScaler can best be explained with a FM-patch. The Anschlagsgeräusch-Patch suffers very much from the fact, that the Anschlag is quite audible if played on the upper part of the keyboard but the effect vanishes as you go down the keyboard. The level scaler is the remedy for this.  LevelScaler.pch2 |
|
Last Updated ( Monday, 19 June 2006 )
|
|
The glide module can be used to shape wave forms.
|
|
Last Updated ( Monday, 30 January 2006 )
|
|
Some information on the zero counter: 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. 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. Rob Hordijk on the mailing list |
|
Last Updated ( Sunday, 29 January 2006 )
|
|
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.
|
|
Last Updated ( Monday, 30 January 2006 )
|
|
Smooth transitions between variations |
|
The G2 doesn't have a true morph capability like Reaktor. However it's possible to program smooth transitions from one variation to another with this trick directly from the manual: "Still, if a Parameter on a module is controlled through a Constant module connected to a modulation input, and a Glide module is inserted between the Constant module output and the modulation input, it is very well possible to make a smooth glide for that one parameter when switching to another Variation."
In this example the pitchmodulation of the filter smoothly glides from Variation 1 to 2.
Smoothvariation.pch2 |
|
Last Updated ( Monday, 30 January 2006 )
|
|
