how an empty node can produce a value?

[tester]

Looks that some sort of magic is going on.
Run audio.
I'm getting readouts out of the empty air and empty nodes.
???

[tester]

I have reduced the code to minimum. The same happens.

[tester]

Hmm... It looks serious. I tried to copy/paste the content of the code to new schematic and re-produced the same design. Readouts show activity from empty air. I have no idea what and why is happening, but looks like a bug.

[Nubeat7]

you need some input on the phase.. because you calculate with an input with no value

[tester]

It does not matters. Readout should not show anything, neither connected nor floating in the air. Besides as I said - I reduced the schematic to minimum in order to reproduce error.

[Nubeat7]

btw your osc isnt playing the right frquencies, it is playing the double freq, if you use

Code: Select all

ph = ph + freq*0.5

it should be fine, here is the corrected version with comparsion

[MyCo]

You are not allowed to write to a streamin variable. You code does:

Code: Select all

streamin ph;
ph = ph + freq;
ph = ph-(ph>=1&1);

ph is an input memory address, you are not allowed to reassign it.

[tester]

Nubeat7, yes, I know. It's a partial/fractional schematic, scaling is elsewhere.

MyCo, so how is that possible, that the initial design, commented by Trog - works?

I mean - should not be, that blue input node, not connected to anything - should have "input = 0" by default? Check this. When float is connected to ph (or whatever you rename it inside the code) - it works, when you disconnect it - the whole design starts to get sick. What I'm missing? How to make this ramp/triangle thing differently?

[MyCo]

You are not allowed to write to an input. That's all that I can tell you. It messes up the whole compiler code. Infact FS should throw a big red stop sign error message when someone tries to do something like this.
Sometimes it works, but as soon you have more stream processing everything goes crazy, because you overwrite outputs from previous modules with writing to an input.

[tester]

Okay, I read you, but on the other hand I admit - I have rather vague understanding about this thing. So let me rephrase the question. In the example above - what should be changed in the code, to make it work correct?

//edit:
This general issue drew attention of devs, so it's possible that the behavior will be corrected.