LFOs and CPU...

[Cyforce]

Currently the stock LFO is not so nice on the CPU, as for example the non-bandlimited in the wiki zone, but their is the aliasing a problem.

But is it a real problem? Specially in case where the LFO is just the modulation source?

Wouldn`t be better to use instead of the 4-5 osc inside the LFO modules, just 1 wavetable read which is feeded by 5 tables(+ selector)? Should be also more gentle on cpu as stock lfo with square selected and you would have a higher amount on possibile waveforms as source...

[CoreStyler]

Did you tried it? i never looked about LFO cpu consuption.. is really high?
i can't confirm that using wave read it will be cpu less. Just try and compare the results.

About waves will be cool to have large number of waves like 100. Instead of coding the in code component.

[stw]

Currently the stock LFO is not so nice on the CPU, as for example the non-bandlimited in the wiki zone, but their is the aliasing a problem.

But is it a real problem? Specially in case where the LFO is just the modulation source?

Wouldn`t be better to use instead of the 4-5 osc inside the LFO modules, just 1 wavetable read which is feeded by 5 tables(+ selector)? Should be also more gentle on cpu as stock lfo with square selected and you would have a higher amount on possibile waveforms as source...

It very much depends on what you want to do with the LFO. As you mentioned if you just want to take it as what it stands for (Low Frequency Osc) you will be fine without any non bandlimited osc. But that changes immediatly if you're going into the audio range.
I myself very much prefer the wave read version (not the wavetable) and use it e.g. in my Reflex Pro.
The big advantage is that you can read different waves on packed streams with just one wave read primitive with a simple read offset. But if you do so take care of proper wave lengths.

[Cyforce]

Well the cpu usage of the stock is now not so big...

Stock bandlimited - 140-240 cycles(240 with square because 2 saws )
Stock non-bandlimited - 60-120 cycles
Wavetable - 130 cycles(dry without speed control etc)

Also if the modification or other modul just saving 100 cycles, through the fact, that the lfo runs the hole time, and if you have 2 of them on board, it could save you up to 200 cycles, which is maybe the cycle-amount which the filter would eat.

it`s just "looking for slim and light on cpu as possible"

Also if it`s a LOW frequency osc(concerning the non-bandlimited version), in some cases of sounddesign the lfo`s are used with max. speed amount, and if there the waveforms didn`t running ideal from aliasing, also not so perfect.
The wave-read sounds interesting, tell us more

[trogluddite]

it`s just "looking for slim and light on cpu as possible"

You can go really low CPU using hopped oscillators (or the hopped version of wave-read) - so long as the LFO's are not getting up into audio frequencies.
I often hop 16 or 32, followed by a gentle smoothing filter (a single pole filter uses only a few cycles) - and I have yet to hear any difference that I found objectionable. I do the same thing with envelopes too, if I am using custom ones.