It does seem that you are correct :)
The code I wrote at first fails for some reason. I don't know why, but I
can definitely do what I want now. Thanks a lot for the clarification!
- Jonatan
Den ons. 24. okt. 2018 kl. 19.32 skrev Yann Orlarey :
> Hi Jonatan,
>
> I am not sure to understand
Hi Jonatan,
I am not sure to understand what the problem is?
import("stdfaust.lib");
process = control(os.osc(440), choice==0), control(os.osc(660), choice==1)
:> _;
choice = button("choice");
In the above code, only one of the two branches will be computed and the
choice will be done at
A bit occupied these days, we’ll look at the issue not before next week.
Stéphane
> Le 24 oct. 2018 à 13:19, Jonatan Midtgaard a
> écrit :
>
> Just bumping this thread in case no one saw it.
>
> Should it possible to be change the branch at runtime? Because that seems
> broken at the
Just bumping this thread in case no one saw it.
Should it possible to be change the branch at runtime? Because that seems
broken at the moment.
- Jonatan
> On 17 Oct 2018, at 12.26, Jonatan Midtgaard
> wrote:
>
> Tested and it works!
>
> Follow-up question:
> Is it possible to change the
Tested and it works!
Follow-up question:
Is it possible to change the 'branch' that is calculated at runtime? Doing
this naively with an hslider or button
var(0) = 5;
var(1) = 9;
choice = button("choice");
process = control(var(0),choice==0), control(var(1),choice==1) :> _;
Still fails when
Fixed on GIT master-dev branch (compiler version 2.11.10)
Stéphane
> Le 12 oct. 2018 à 11:05, Jonatan Midtgaard a
> écrit :
>
> Thanks for the quick response. Looking forward to hearing about the
> developments.
>
> - Jonatan
>
> fre. 12. okt. 2018 17.02 skrev Stéphane Letz :
> >
> >
Thanks for the quick response. Looking forward to hearing about the
developments.
- Jonatan
fre. 12. okt. 2018 17.02 skrev Stéphane Letz :
> >
> > ASSERT : please report this message, the stack trace, and the failing
> DSP file to Faust developers (file: mterm.cpp, line: 511, version: 2.11.9,
>
>
> ASSERT : please report this message, the stack trace, and the failing DSP
> file to Faust developers (file: mterm.cpp, line: 511, version: 2.11.9,
> options: ocpp, -scal -ftz 0)
The reported message is indeed correct ! This reveal an issue in the compiler,
we are working on it.
Thanks.
A short code is attached. Compiling with
faust -scal -es 1 -lang ocpp controltest.dsp -o "controltest.faust.hpp"
this gives the error message
A[0] == SigEnable[5,0]
ASSERT : please report this message, the stack trace, and the failing DSP
file to Faust developers (file: mterm.cpp, line: 511,
Can you send the problematic code?
Stéphane
> Le 12 oct. 2018 à 08:47, Jonatan Midtgaard a
> écrit :
>
> I have updated to 2.11.9. I am still getting the same errors, and also the
> -lang ocpp option seems to be causing trouble. Is there an example of these
> primitives so I can check if I
I have updated to 2.11.9. I am still getting the same errors, and also the
-lang ocpp option seems to be causing trouble. Is there an example of these
primitives so I can check if I am doing things right?
- Jonatan
tor. 11. okt. 2018 20.28 skrev Stéphane Letz :
> The control/enable are «
The control/enable are « experimental » primitives that are still only
available using the old C++ backend in scalar mode (so doing something like
faust -lang ocpp foo.dsp, or explicitly giving the -lang ocpp argument to
faust2xx script, like for instance faust2caqt -lang ocpp foo.dsp and so
12 matches
Mail list logo
