Concerning the demo with the LFOs at the end of the video: to me it seems that the LFO waveforms are also implemented as wavetables. However, the LFO wavetable oscillators are implemented in a simpler fashion than the audio wavetable oscillators.sadowickproduction wrote: Fri Jun 28, 2019 7:49 pm Hey guys! So I did the follow up video and I thought before I made it live to my subscribers the experts could watch it and explain to me whats happening. Ive found that the filter compounds the aliasing and the LFOs in Oscillator modes are not band-limited at all! Square waves really break this thing.
Because "LFO" stands for "low frequency oscillator" I would assume that one entry (a.k.a position) in the LFO table only consists of one single waveform as opposed to a set of progressively bandlimited waveforms (that are selected depending on the target frequency). If such a single waveform is read at the low frequencies that LFOs are usually operated on then this does not cause any bad problems (except that technically the higher frequencies will drop more and more the lower the frequency goes). However, if you switch such an implementation to be used as an audio rate ocscillator then the table is read at audio frequencies and in that case you indeed get severe aliasing as heard in the demo.
My assumption is that using the LFOs as audio rate oscillator is only meant as a fallback or compromise if you already use all the regular oscillators. So I would not even assume that NI "fixes" anything like is assumed in the video because the fix would be turning them into full blown audio rate oscillators which are more costly to implement.
Considering the target audience of the first version of "Massive" (wub wub) I would not be surprised if these artifacts will be used as an effect in the future.
