@aaronventure The reason is that maintaining this enable/control feature adds complexity in the compiler that we want now to cleanup.

@Soundavid is this still an issue? I was just researching the same thing as I noticed significantly more CPU usage on an M2 ultra studio mac than on an m1 macbook pro....

@aaronventure yes thats actually the one I was referring to it should be smooth already.

@udalilprofile

1: your picture is un readable - so I have no idea what the error actually is
2. You will need to provide some sort of value set for the parameters you are using - and from what I can see of your code - you havent done that.

@aaronventure Thats exactly what I would like to do. I've been trying to figure that out from the start. I know thats ambitious for a noob but i've figured out most of the stuff I need to know to get started. Im alot more comfortable on the design and audio side than scripting so im currently trying to learn as much as I can from everyone here. Thanks everyone!

@Mighty23 well thats one way to do it....

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

@Morphoice said in mixing an envelope signal with an aftertouch signal:

@VirtualVirgin superb thank you. How would you go about to make the aftertouch value variable to be either 0 (aftertouch closes the filter) or 1 (aftertouch opens the filter) or have no effect at all (I would Imagine the aftertouch"intensity slider to go from -1 to 1 where 0 is no effect)

I'm trying to understand what you are asking here.
So you want to to turn the aftertouch control signal into a 3 way switch?
Where in the signal path is the aftertouch happening?

@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!