Wavetable Oscillator

[celine]

Per default there is no WAV file assigned to your wavetable Oscillator (WT Osc). You can assign a WAV file by scrolling through the list using the first encoder and selecting the waveform by clicking on “load”.

Wavetable Oscillator Parameters

• Sel: scroll through the list of waveforms using the 1st encoder. You can add additional WAV files in the samples directory on the SD-card . Press “Load” to select and load the WAV file.

• Crse: set the coarse frequency of the WT OSC.

• Fine: set the fine frequency of the WT OSC.

• NrWav: cutting the WAV file automatically into smaller pieces or number of waves.

• X: used to navigate the X axis of 3D space of the waves that is automatically generated from the WAV file (cutting it up using the “nr of waves” buttons).

• Y: used to navigate the Y axis of 3D space of the waves that is automatically generated from the WAV file.

• Z: used to navigate the Z axis of 3D space of the waves that is automatically generated from the WAV file.

• NrOsc: up to 4 oscillators per WT Osc

• Sprd: to change the spread between the different oscillators in the cloud.

Wavetable Oscillator Settings

• CalA1/CalA2 after applying a pitch signal to the pitch input, for example from a CV keyboard, press the A key in an octave on your keyboard and press this button. Then press the A one octave up and press CalA2. The wt osc will then know what the voltage difference is and use that to figure out how to correctly track the keyboard. This feature also appears in other modules. The calibration is already done for standard 1v/oct signals so there is no need to use this normally.

• CalRs resets the above calibration data to the default

• Load: to select a new WAV file click “Load”. Each time you click “load” the selected WAV file will be loaded.

Wavetable Oscillator Inputs/Outputs

A wavetable oscillator can be modulated in pitch, spread, x, y, z, frequency, amplitude, and sync.

• WT Osc: Pitch
• WT Osc: Spread
• WT Osc: X
• WT Osc: Y
• WT Osc: Z
• WT Osc: Freq
• WT Osc: Amp
• WT Osc: Sync

The wavetable oscillator has one output.

Example

Modulate the frequency of the WT Osc using the frequency of an LFO (sine), after which the resulting signal is sent to the output.

LFO-> WT Osc -> Output

                               Inputs                           Outputs
  LFO                          /                                sine: WT Osc: Freq                       
  WT Osc                       WT Osc: Freq                     out: out: in
  Output                       out:in                           /

[SSPix]

Would be nice to get some hints on some parameters, what’s them good for, e.g. NrOSC

[bert]

Would be nice to get some hints on some parameters, what’s them good for, e.g. NrOSC

NrWaves parameter determines in how many pieces the loaded WAV file is cut, before the pieces are used to create the 3D wavetable space, which you can navigate with the XYZ parameters. By changing the NrWaves parameter you access a different timbre space using the XYZ.

What other parameters are not clear yet?

[jgrind]

is it possible to load multiple wavetables and morph between them? similar to ensoniq transwaves or something like the dove audio wave plane module?

[bert]

is it possible to load multiple wavetables and morph between them? similar to ensoniq transwaves or something like the dove audio wave plane module?

When you load a WAV file, it’s automatically cut up into a wavetable and you can control in how many waves the file is cut using the NrWaves parameter. So if you want to use multiple wavetables (each containing a number of waves) you can just append them first into one big WAV file and then load that WAV file and then adjust the NrWaves parameter until you get what you want.

[jgrind]

Ok great, thank you!

[BENDY]

Is it possible to trigger in a “one-shot” scenario, where a slice is played only once on each trigger? In this way the wavetable could contain different envelopes, or even as a sampler. The mind boggles.

[bert]

Is it possible to trigger in a “one-shot” scenario, where a slice is played only once on each trigger? In this way the wavetable could contain different envelopes, or even as a sampler. The mind boggles.

the wavetable oscillator won’t do that, but you can load your file(s) into the sampler module and do what you want there.