Some more nubie questions.

[joejoe]

Ok, so I've been hitting the FS user manual pretty hard and have a few questions.

Ruby vs DSP code. So I see in this manual there's plenty of info about using ruby for GUI, MIDI data and even doing actual DSP related work with the mono to frame and fram to mono mods. This DSP component looks fairly powerful even though your working with limited expressions. So my question is:

Is ruby not ideally meant for DSP processing of audio? Would it be better to use the DSP component? Is Ruby better for handling the tasks of the user interface over wireing components togeather in FS? Are the expressions listed in the user manual for the dsp component the only expresions avialable? If not where could I get more info on these expresions? If I use Ruby for DSP work will there be higher CPU load?

[nix]

You can't process at samplerate with Ruby essentially.
The mono to frames is the way to work with streams and Ruby,
but the general consensus is that Ruby isn't really for stream processing,
as the frames are not at a per sample level, they are blocks of samples.
However, Ruby is fast enough for MIDI, and quite flexible at MIDI tasks.
I can recommend it's use for MIDI,
but if you want to build guitar fx, the DSP window is where it's at,
and also the stream primitives.

Ruby can somewhat simplify GUI design,
and all drawing abilities that prims have,
are also possible with Ruby.

The expressions are basic with the DSP window,
but the speed is sooo nice.

I think prolly nearly all functions are listed in the manual.