It's possible to work with frequencies(hz) in a code box?

[trogluddite]

Oversampling is the only truly effective way.
As oddson rightly said in his earlier posts, aliased frequencies get "reflected" to become other, new, frequencies that are below the Nyquist limit.
For example say you make a wave that has a fundamental of 18kHz.
Unless it is a pure sine, the second harmonic (octave) will be at 36kHz - well above Nyquist.
Lets assume that the sample frequency is 44kHz - so the Nyquist limit is 22kHz. That octave harmonic is 14kHz above the limit.
What happens is that instead of being 14kHz above the limit, it will be transformed to 14kHz below the limit - 22kHz - 14kHz = 8kHz. But 8kHz is below our original fundamental frequency, so low pass filtering is not able to get rid of the "alias".
This also demonstrates something else - the alias at 8kHz, is no longer a harmonic (or sub-harmonic) of the original 18kHz tone - which is why aliasing distortion sounds so much worse than "analogue" distortion.

SM's stock oscillators get around this by using wavetables - they do not alias because they play back short waveform samples that already have the >Nyquist frequencies removed. There are many of these short samples for each waveshape - chosen according to pitch, so that exactly the right harmonics are removed.
If your synth only mixes together (adds/subtracts) multiple oscillators, then all is well, you still have no aliasing - but if you FM or RM (multiplying oscillator outputs), then new frequencies are made that can once again be above the limit.

[distante]

So I suppose that multiple filter pre and post edit are in order.

Is there a table or list of the amount of CPU resources use for each pre made module in SM?

[Dell]

The amount of CPU consumed by your plug-in is based on your Computer.

If you are looking to offer plug-ins publicly, use the lowest computer system you own. This will train you to be more concerned on the amount of drainage taking place than using the strongest computer available, which may be larger than the average person using your plug-in in his/her DAW.

If you are not planning to offer your plug-ins publicly, merely look at the “CPU=” listing on the bottom right hand corner of Synthmaker’s window. That is the true CPU consumption and reflects what to expect if you are planning to use your design in a live host.

In a playback system (DAW) the CPU will vary based on the audio file (non-compressed WAV, compressed MP3 ) in addition to the sample rate of the audio file.

To get a better understanding of Synthmaker, you cannot be afraid of making mistakes to the point you need to force Synthmaker to shutdown. Taking chances is how you will learn the fundamentals of Synthmaker. Once you are afraid of doing something out of the ordinary in Synthmaker, you will never accomplish your goals.

Cheers!

[distante]

Thanks Dell!

[Xtinct]

Hi its not just mistakes that cause it to shut down sometimes a new connection will crash it, then when recovered
will work