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

@JulesV
I don't remember your snippet exactly, but yes, eqBrdCst.setEnableQueue(true) is important for the logic to work. Christoph gave me this tip when I was writing the script.

@Christoph-Hart @HISEnberg Good examples, thanks.

@d-healey said in Table curvy shape issue:

HISE_Definitions

It would be really great to have this added to the HISE documentation!

@JulesV start here:

const var externalDat = { "Option 1": A, "Option 2": B, "Option 3": C, "Option 4": D }; inline function CheckOnLoad() { local data = Engine.loadFromJSON("../MyFile.dat");); Console.print(trace(data)); //data = externalDat; //Engine.dumpAsJSON(data, "../MyFile.dat"); }; CheckOnLoad();

@aaronventure Thanks, looks interesting :)

@JulesV The problem is that the different positions the event object holds are related to the node when you hover it, and the whole tile when not on a node...
This makes the tracking impossible. There might be another solution that would allow to discriminate if on a node or not, but I am not aware of...

Or do the same as for the y position, using the frequency from the module that you convert to a 0-1 position then multiply with the FoaltingTile witdth

@JulesV
You're welcome! :-)