MMultiBandConvolution

[jens]

Here's a few points I'm wondering about:

- The Melda modulators are superb. However what I don't understand is that with them onboard, there are so few modulation-targets in MMultiBandConvolution. Why isn't it possible to modulate e.g. 'Stretch' and 'Interval' and parameters of the 'Reverb'?

- What exactly is the 'Reverb'? It seems it is calculating an IR on the fly (depending on 'mode'). Is it some kind raytracing-reverb?

- why is there no pre-delay for 'File'?

- Why does the plugin not include Melda's 'Multiparameters'?

[MeldaProduction]

Here's a few points I'm wondering about:

- The Melda modulators are superb. However what I don't understand is that with them onboard, there are so few modulation-targets in MMultiBandConvolution. Why isn't it possible to modulate e.g. 'Stretch' and 'Interval' and parameters of the 'Reverb'?

- What exactly is the 'Reverb'? It seems it is calculating an IR on the fly (depending on 'mode'). Is it some kind raytracing-reverb?

- why is there no pre-delay for 'File'?

- Why does the plugin not include Melda's 'Multiparameters'?

1. This cannot be done, because convolution takes a long impulse response that needs to be generated and preprocessed. That takes LOTS of time, so modulation in realtime is just impossible.

2. Yes, but no raytracing. It implements a few specialized algorithms.

3. New version will have predelay (and will be changed a little anyway)

4. Because there are just a few parameters that can be controlled - multiparameters can only control the same parameters as modulators.

[jens]

ah, ok - thanks for clearing that up!

[JBlongz]

Another question about MConvolution: Any change of using multiple inpulse files in the future?

[MeldaProduction]

Another question about MConvolution: Any change of using multiple inpulse files in the future?

What you mean by that? Right now you can use A and B for modulation, and if you need more response (which I don't know why), you can just use multiple instance of the plugin.