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 <[email protected]>:

> 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
> on…)
>
> I’ve just pushed on master-dev some improvements in error message
> reporting when using control/enable incorrectly:
> https://github.com/grame-cncm/faust/commit/d0c5bae907380f2be8c2ff7dc90e5c5a0006892a
>
> And we’ll have to implement them in -vec mode, then for all FIR based
> backends.
>
> Stéphane
>
> > Le 11 oct. 2018 à 12:52, Jonatan Midtgaard <[email protected]>
> a écrit :
> >
> > What is the state of 'true' if statements in Faust at the moment? My
> current understanding was that if i have a series of block diagrams
> >
> > f(0) = a;
> > f(1) = b;
> > ...
> >
> > and I want to be able to choose which block-diagram to execute without
> the others being executed in the background, it could be done with the
> control primitive, e.g.
> >
> > in = hslider("Choice",0,0,N,1) : int;
> > process = par( i, N, control(f(i),in==i) ) :> _;
> >
> > I also saw in an old thread that this requires the -es 1 compiler flag.
> However, this results in a compiler error, referring to SigEnable.
> >
> > How correct is my understanding, and should this work?
> >
> > - Jonatan
> >
> > PS: compiler version is 2.10.0
> > _______________________________________________
> > Faudiostream-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/faudiostream-users
>
>
_______________________________________________
Faudiostream-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Reply via email to