Thank you for sharing these!

the inflator algorithm looks a lil bit weird, i think it should be like this:

a1=1+(curve+50)/100
a2=curve/50
a3=(curve-50)/100
a4=0.0625-curve/400+curve^2/40000

x=a1・x+a2・x^2+a3・x^3-a4・(x^2-2・x^3+x^4)

the curve value should be in the range of -50 to 50 but you could intentionally set it to somewhere over 50 to achieve some weird distortion effect.

also, the inflator is mainly control by input gain and curve so you may need to add a input gain by doing something like:

x=x0・preGain

(the effect param in the original plugin is actually a little bit misleading, it's just a dry wet mix and seems like it was only designed to be set to 100% or 0% to make it sounds "natural")

I'm sure several inflator clone use this algorithm and with linear phase oversampling it somehow even sounds better then the original one :)

Well, I guess I didn't read the header file carefully...
Seems like the FIR one is disabled in the header file by default.

Make sure enable the filterHalfBandFIREquiripple in the header file before compiling Hise if you decide to use oversampling in linear phase plugins.

I noticed there are two oversampling methods in JUCE source code (FIR & IIR).

What method is defaulty used Hise? And how to switch from one to another one?

@Christoph-Hart

@Christoph-Hart said in Number of vst plugin parameters:

There are ways to use dynamic plugin parameters for this scenario.

Thank you! I'll definitely gonna look into that.

Actually my synth has almost fully separated LR channels, and i really wanna give users an option which is setting some basic stuffs independently on each channel so a lot of these parameters are doubled. Also, there're several complex mod matrices and unison effects need to be done, which probably gonna bring another bunch of parameters here. Anyway I'll keep that number as lower as i can.

Are there any limit on the the number of paramaters in vst format or in daws?

The synth i'm currently working on has about 500-600 paramaters and I just realized like it will most likely be 1000+ when i finish it...

I want to use my rnbo wavetable engine in hise but it has 8 buffers and I decided to make it lighter first before i compile it.

So is there a buffer amount limit of the Rnbo node in hise? And how many bufffers can the rnbo node actually handle?

@Mighty23
Nice work!
For the band split, you may want to use the linkwitz riley instead of svf.

About the denormal protection, may I know what CPU you're are running this code on? Does this directly cause the crashing?
This might be useful for some legacy CPUs and it won't likely really be a problem for modern x64 CPU afaik.

@JeanC
I don't think scriptnode currently support that...
If your're writing something like a plugin host, you could take look at the audio plugin host in JUCE source code.

@Christoph-Hart

@Christoph-Hart said in CPU usage - clone container:

have you compiled the network to a C++ node already?

No, because I'm still working on the faust node inside the container.

I made it a little bit lighter and the cpu usage dropped down to about 50% now.

@Dan-Korneff You could already switch that manually through the JUCE souce code anyway

I'm working on a script synth with a clone container which is used for a unisono effect. This is the first time i use this node. It works fine but the CPU usage goes up to 85%-95% when full 16 unisons being used. So now i decide to compile everything inside the clone container into one node. But will that actually make a difference to cpu usage?

That's quite a big task for this project (like i need to reconnect 40-50 parameters), so i'd like to know if it's really worth to do that.

Has anyone tried to implement dsp code from csound in Hise?
I don't really familiar with csound but I found there're several good filter functions in the source code.
https://github.com/csound/csound/tree/develop/Opcodes

I want to implement some of these in Hise through the third party c++ node but i don't quite know about the structure of csound and a lot of variables passing though the functions make me a little bit confused.
(for example like the "csound", it that basically the signal path?)

Any ideas are welcome!

Thank you for sharing these!

the inflator algorithm looks a lil bit weird, i think it should be like this:

a1=1+(curve+50)/100
a2=curve/50
a3=(curve-50)/100
a4=0.0625-curve/400+curve^2/40000

x=a1・x+a2・x^2+a3・x^3-a4・(x^2-2・x^3+x^4)

the curve value should be in the range of -50 to 50 but you could intentionally set it to somewhere over 50 to achieve some weird distortion effect.

also, the inflator is mainly control by input gain and curve so you may need to add a input gain by doing something like:

x=x0・preGain

(the effect param in the original plugin is actually a little bit misleading, it's just a dry wet mix and seems like it was only designed to be set to 100% or 0% to make it sounds "natural")

I'm sure several inflator clone use this algorithm and with linear phase oversampling it somehow even sounds better then the original one :)