This is probably because the same labels (like BOOST, ATTEN) are used in different places.

try to use unique labels to confirm this hypothesis

then @Christoph-Hart this should be considered as a bug. Same labels can be used, but will internally correspond to differents pathnames (built following the group hierarchy).

The code https://github.com/christophhart/HISE/blob/develop/hi_faust/FaustUI.h does not use the pathname model so I guess UI items with same labels will be considered the same, which is not what is needed. Look at MapUI code to see how labels/shornames/pathnames can be used: https://faustdoc.grame.fr/manual/architectures/#some-useful-ui-classes-and-tools-for-developers

@sletz fixed thanks

@toxonic I have the same error "expecting LPAR or DEF" in an effect made with Faust. The problem is only on Linux. I tried installing Faust again in a folder in my user directory, then changed the path of Faust on Hise, but it still gives me the error.

Any ideas?

thanks @Mighty23 & @aaronventure !

Success 😍

It seems to matter that:

the original script node containing the faust dsp needs to be deleted, not just 'switched' off. in hardcodedMasterFX the scriptnode needs to be selected. (in the case above scrip_fx1, not 'minimalGain'.)

It's a bit tricky. Thanks a lot!
Moving on... ;)

@Matt_SF brilliant, I didn't notice, so you beat me to that with an even better solution ;)))

@HISEnberg helpful - thanks!

@sletz thanks for that!

the relevant bit is at the end in The Future of Faust. I was curious about the enable primitive and even though it's undocumented, it seems to work!

1e890d7d-cef7-4bae-a53a-952c78c79d4e-image.png

It's somewhat limited in usage so looking forward to trying out ondemand.

@Lindon As long as it works, glad to hear!

@Lindon Yes I think the mid value (or skew factor) just need to be set the same

@DanH yes "fun"..

So the only way I can get this to work is to remove the (silly) normalisation all together and replace it with the valid Freq values like this:

import("stdfaust.lib"); korg35LPF(theFreq,Q) = _ <: (s1,s2,s3,y) : !,!,!,_ letrec{ 's1 = _-s1:_*(alpha*2):_+s1; 's2 = _-s1:_*alpha:_+s1:_+(s3*B3):_+(s2*B2):_*alpha0:_-s3:_*alpha:_+s3:_*K:_-s2:_*(alpha*2):_+s2; 's3 = _-s1:_*alpha:_+s1:_+(s3*B3):_+(s2*B2):_*alpha0:_-s3:_*(alpha*2):_+s3; 'y = _-s1:_*alpha:_+s1:_+(s3*B3):_+(s2*B2) :_*alpha0:_-s3:_*alpha:_+s3; } with{ invSqrt2 = 1/sqrt(2); freq = theFreq; K = 2.0*(Q - invSqrt2)/(10.0 - invSqrt2); wd = 2*ma.PI*freq; T = 1/ma.SR; wa = (2/T)*tan(wd*T/2); g = wa*T/2; G = g/(1.0 + g); alpha = G; B3 = (K - K*G)/(1 + g); B2 = -1/(1 + g); alpha0 = 1/(1 - K*G + K*G*G); }; // Filter Frequency myFreq = (hslider("Freq.", 3000, 20, 20000, 1)); Res = hslider("Res.", 1, 0.3, 9.0, 0.1); // The filter is a mono effect, so duplicated here for stereo usage process = _,_:korg35LPF(myFreq,Res),korg35LPF(myFreq,Res);

I assume this is more like what most "HISE-people" would want - as we can add our own ScriptNode/UI skewing as we like it. If theres no complaints I will work my way through the versions on faust_fx_library replacing the ones I uploaded with these versions....

@d-healey @Lindon

I added a page in the Glossary Section of the docs: Development Recipes

This can be used for little best-practice and workflow tips. So if you've got other examples that you stumble over repeatedly and which solution could be useful to others, please don't hesisitate to add.

All best,
Dominik

@treynterrio said in Faust node Channel mismatch:

processed_left = (parametric_controller(cntrl, envelope, speed, depth) * shift <: transpose(c_samples, c_xfade));

You can write

processed_left = (parametric_controller(cntrl, envelope, speed, depth) * shift <: transpose(c_samples, c_xfade)); process = processed_left,processed_left;

@aaronventure Finally. 🐷💯

@orange said in How to enable Faust on Mac:

to set the Faust folder path in the Hise settings.

Yeah, I Did, Compiling my first Test project Now
Update: All went well, Tested one Ableton, and Everything works as expected

@Natan so build your faust node, and if you are selecting from some list of faust code items then you should be fine - I always just take the faust code (.dsp) and build a new faust item in my project - so I always have to compile it.. .so I'm gonna say safest bet - compile your faust code.

@d-healey said in WDF Model is not working in Faust:

Interesting that it gave you the right answer,

because the 4o is guessing. You can ask it to run a python script that counts rs in a string and you'll get the correct answer. Pure inference in this case is mostly guesswork, because it works with tokens, not letters.

07eec81d-c908-44ee-b8a3-c2a703e8f569-image.png

The o1 has reflection so it can catch itself doing this. Plus, this test comes up so often that I wouldn't be surprised it already made its way into the training data.