From the original SynthMaker forum (2004–2014), with its members’ names and dates.
rl ·
- allow other datatypes (float, int,...) for in- and outputs (I think this was already requested before)
- currenly inputs are processed at sample rate. This is not always necessary. In order to improve performance, e.g. the phase increment of an oscillator needs only be recalculated when the frequency input changes, the coefficients of a filter need only be calculated, when cutoff or frequency changes.
I'm thinking about some sort of event handler that gets fired when changed data arrives; maybe:
polyin in;
polyout out;
floatin resonance;
floatin cutoff;
float a1, a2, a3;
float b1, b2;
out=.......;
on resonance, cutoff changed {
a1 = ...
a2 = ...
...
}
jorge ·
rl wrote: currenly inputs are processed at sample rate. This is not always necessary. In order to improve performance, e.g. the phase increment of an oscillator needs only be recalculated when the frequency input changes, the coefficients of a filter need only be calculated, when cutoff or frequency changes.
I'm thinking about some sort of event handler that gets fired when changed data arrives
I agree with you, eventually the events processing and sample rate processing will be integrated in one code component. For now, the way around it, is to create the event related part of your schematic using green data components and feed the result into a poly input. The green sections of the schematic are not compiled into the sound processing machine code, they only use CPU when there are events.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker