From the original SynthMaker forum (2004–2014), with its members’ names and dates.
TomC ·
For the coding handicapped, the interesting (new) things are bold. I could use those features all day, in fact there are loads of things that CAN'T be done without this basic functions.
streamin in; streamout out; floatin size; floatin counter; floatout result;
float array[size];
loop(counter) {
}
result = 1;
Cheers.
Tom
rl ·
vote++;
and since we are on topic, sometimes I'm dreaming about:
memin memi[size]; // mem array input... memout memo[size] // ..and output codein codeblock; double d = 0.10000003433something; int i;
eval codeblock (1.0, 2.0, 3.0); // parametrized evaluate function as subroutine memi[i] = 3.0; // faster int-math on array indexes
matti ·
rl wrote: vote++;
and since we are on topic, sometimes I'm dreaming about:
memin memi[size]; // mem array input... memout memo[size] // ..and output codein codeblock; double d = 0.10000003433something; int i;
eval codeblock (1.0, 2.0, 3.0); // parametrized evaluate function as subroutine memi[i] = 3.0; // faster int-math on array indexes
vote++;
floatarray inputs would also be cool.
electrogear ·
Can't believe there's no floatin/floatout's, I would have thought this would be an obvious one. Would it be so difficult to implement for the next release?
theun ·
@ Electrogear:
Not being able to declare ins and outs as floatin and floatout may seem an omission. However, functionally speaking I can't see how this would lead to any limitation: a float (even an int) can be connected to a stream. And a stream can be connected (if you know the trick with ctrl shift) to a float. So one can actually feed floats in and out a code module without having a formal floatin/floatout declaration available.
electrogear ·
Hi theun,
I was trying to extract coefficients from a code filter by declaring streamouts (a0out, a1out, a2out etc) and putting the a0, a1, a2 variables into those outputs. I then attached a float to each of the outputs (using the ctrl shift trick) and got 0 for all three outputs.... not sure why - is that the right way to do it? Take a look at the attached file if you like. Sorry if I'm being stupid.
http://www.box.net/shared/a93i5dqwwo
theun ·
electrogear wrote: Sorry if I'm being stupid.
If anybody is stupid it's me ... I should have checked better.. ahum .. apologies..(red face icon needed)
OK, my previous post is crap. Thank you for making this clear to me.
Though feeding in floats goes (I'm using this quite often when using the code module). You can do an attempt to read out the a0out, a1out and a2out in your osm using the poly readout module (in the analysis group) or use a combiner followed by an M2F driven by a ticker and feed the result into a float element. But take care to press only one key. When you press n keys the result of the n entities of the poly thread will be added to each other. In this case the endresult will be n times the value you'll get when pressing 1 key, as a0out (etc) is not depending on the main signal input.
However we could rewrite the code (light bulb icon needed) and define the outputs a0out (etc) such that they are depending on the main signal input. And that being the case this would result in different values for each of the voices. And this is the very reason why there is no floatout. And makes clear that adding the possibilty to declare a floatout is not trivial. As far as I can judge it now it can't be done as the value may be different for each voice.
Thank you once again
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker