Fx Processing Release

[Christoph Hart]

The SimpleReverb module actually checks if there's something to process in the pipeline, but the convolution reverb is not suspending processing when there's nothing to do.

But actually the new engine with the multithreaded convolution engine is not a terrible CPU hog (it's about 1% - 2% CPU usage in the audio thread), so I didn't bother about adding this.

@d-healey those REAPER CPU meters are a joke, I really don't know what they measure, but every other DAW (and HISE itself) come up with a CPU usage at least 10x as large.

[d.healey]

@christoph-hart I think it must be average CPU and others show peak perhaps? or something to do with multiple-cores/threads? Hard to cram all this into a screenshot but Reaper and Task manager roughly agree with each other (they fluctuate) and HISE and Kontakt seem to agree with Reaper. I have some old Kontakt projects with 100 instances of Kontakt, if the usage was 10X that displayed my CPU would explode :)

[Tod Slaughter]

The problem will arise when you have multiple send convolutions similar to string audio dark matter library for kontakt

[Tod Slaughter]

Anything on the parameter mapping q?

[Tod Slaughter]

@d-healey said in Fx Processing Release:

@christoph-hart I think it must be average CPU and others show peak perhaps? or something to do with multiple-cores/threads? Hard to cram all this into a screenshot but Reaper and Task manager roughly agree with each other (they fluctuate) and HISE and Kontakt seem to agree with Reaper. I have some old Kontakt projects with 100 instances of Kontakt, if the usage was 10X that displayed my CPU would explode :)

I have the same experience. They seem to match pretty well imo.

[d.healey]

@tod-slaughter In the interface designer select a control you've added to the interface and in the properties list you can assign it to one of the macro knobs

[Tod Slaughter]

So that gives you 8 fixed parameters only. Good to know.

[Christoph Hart]

So that gives you 8 fixed parameters only. Good to know.

Nope, you can have as much parameters as you want (there's a bunch of other properties related to plugin parameter management). The macro control system is just a handy way of quickly mapping multiple elements to 8 controls and automating them when you run HISE as plugin in a host.

But to be honest, if you're making a plugin with parameters, you most likely won't touch the macro controls.

[Tod Slaughter]

@christoph-hart said in Fx Processing Release:

So that gives you 8 fixed parameters only. Good to know.

Nope, you can have as much parameters as you want (there's a bunch of other properties related to plugin parameter management). The macro control system is just a handy way of quickly mapping multiple elements to 8 controls and automating them when you run HISE as plugin in a host.

But to be honest, if you're making a plugin with parameters, you most likely won't touch the macro controls.

Thanks for correcting this. As I understand it then there's no end user parameter mapping but parameters can be scripted to appear?

[Christoph Hart]

What do you mean with end user mapping?

You can publish as many parameters as your project needs, and the user can choose them in the DAW automation lanes. There's no need for a fixed size slot like KONTAKT or Falcon because they need to have a dynamic amount of parameters.

[Tod Slaughter]

That's much more clear now thank you.