Oh right, it's table lookup that's crashing, not division by zero
directly. Thanks for the info.
On Mon, Apr 19, 2021 at 7:46 PM Stéphane Letz wrote:
>
> All backends actually crash. Read again:
>
> ==
> In Faust, the interval calculation system on signals is supposed to detect
> possible p
All backends actually crash. Read again:
==
In Faust, the interval calculation system on signals is supposed to detect
possible problematic computations at compile time, and refuse to compile the
corresponding DSP code. But since the interval calculation is currently quite
imperfect, it can
Thank you. But should the interpreter crash though?
This program does not crash:
import("stdfaust.lib");
process = 1000 / hslider("divPitch", 10, 0, 10, 0.01);
While this one does crash:
import("stdfaust.lib");
process = os.osc(1000 / hslider("divPitch", 10, 0, 10, 0.01));
Thread 14 "
This is a the kind of problematic code that the compiler does not correctly
handle in a perfect way. More info here:
https://faustdoc.grame.fr/manual/faq/#produced-nan-or-infinity-values-and-table-access
Stéphane
> Le 19 avr. 2021 à 19:10, Kjetil Matheussen a écrit
> :
>
> Hi,
>
> I don't
Hi,
I don't know if this is a bug in the compiler, the interpreter
backend, or the faust code itself, but the interpreter backend crashes
when it runs this code:
import("stdfaust.lib");
divPitch = hslider("divPitch", 10, 0, 10, 0.01);
enable5 = button("enable2");
process = os.osc(1000 / d