@JulesV My solution is to use a flag. If the plugin is being initialized, load a specific preset that has my settings. if the plugin isn't being initialized, it doesn't do anything special.

@JulesV
I've never worked with it before. If it doesn't work right away, you could maybe use a broadcaster for it. But @David-Healey probably knows more about that! :-)

If there are any problems, it definitely makes sense to compile HISE as a plug-in and then load the project directly into the DAW to try it out.

@Christoph-Hart I understand, thanks for the helpful advice.

@JulesV Yep it's broken, make a bug report. I suspect this is related to all the recent mod matrix changes.

@dannytaurus @resonant Thanks!

@sletz Thanks for the suggestion. I tried that and same result.

Now I understand that rather than versions, it is about input output numbers.

For example the below one. Naturally Hise complains about the input output channels. I am not sure how to handle that.

Screen Shot 2025-12-30 at 23.05.26.png

Screen Shot 2025-12-30 at 23.09.38.png

@JulesV You can possibly use ba.selectmulti as in:

process = ba.selectmulti(100, (fx1, fx2, fx3), nentry("Model", 0, 0, 2, 1)) with { fx1 = re.jcrev; fx2 = re.zita_rev1_stereo(20, 200, 2000, 3.0, 2.0, 48000); fx3 = re.dattorro_rev(200, 0.5, 0.7, 0.6, 0.5, 0.7, 0.5, 0.2); };

But yes the 3 branches will always run here.

@ustk Yes, I deleted the Binaries folder and tried again and again. HISE already gives a "build failed" error and doesn't say why.

So, when I try to manually open and compile the AutogeneratedProject.jucer file in the Binaries folder, I see that error in XCode.

This is probably a bug with the current commit.

@dannytaurus said in Scheduled knob task after initialization:

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

It can actually be used for other purposes.

But in my case, I'm actually using it for a bug workaround. When I buld a complex custom node with 23 parameters and use it in HardcodedFX, I noticed that in one parameter, the knob, wasn't getting its value during plugin initialization.

However, after init, when the knob is tweaked, the value is updated. That's why I chose this method. Creating a custom node with fewer parameters isn't a problem, by the way. As the number of parameters increases in custom nodes, the problems increase.

@d-healey or this

return Math.sign(x) * Math.pow(Math.abs(x), 1/3);

But a benchmark shows no difference in efficiency

@JulesV Yes you need to uncheck that box. Yes all files in the Audio Files folder are in the .dat

@d-healey Clever! Thank you!

@JulesV I seem to remember getting that too but everything worked fine, the project would compile and export. @Lindon's explanation seems plausible.

@JulesV Yeah you can use the HISE command line interface to compile your projects.

If you write a batch script you can get it to run the commands automatically and generate the installer. ChatGPT is quite useful for this kind of thing, but make sure you understand the output it gives you because batch scripts are powerful things that can run any command, including deleting files.

@Lindon said in How to include external .dsp files into the faust node?:

@JulesV open the included file - copy its contents into your Faust file....

Thanks. I think I need those t-shirts now :))

@JulesV Not sure, you could try storing the X position of each node in an array. You'd need to attach a broadcaster to the Band Selected event of the EQ to keep track of it.