Hi,

I'm experimenting with the Convolution node, and I have a few questions:

1- Predelay : When I set the predelay to 1000, I expected a delay of 1 second, but it doesn’t seem to match. Is it possible that the value 1000 equals 0.1 seconds ?

2 - Hi-cut : The hi-cut filter doesn’t seem to affect the signal. Am I missing something ?

3 - Block size : What would be a good block size to use for convolution reverb in terms of balancing CPU performance and audio quality? I was thinking of using a FixedBlockSize of 128, but I’m a bit concerned it might introduce too much latency.

Thanks in advance for any insight!

@Orvillain
Oh ok, my bad then. Maybe it’s your sample that’s below 0dB, so it goes up and then drops back down. Anyway, glad it’s working for you now!

@Orvillain

From the doc :
"this value will be used as start ramp value whenever the node is being resetted (eg. when the network is unbypassed)."

I suppose that setting a smoothing value along with a resetValue of -100 dB will create an attack-like effect, gradually ramping the signal up to the target gain after a bypass or a initialize start

Hi everyone,

I’ve been going through the Stereo Widener example in the HISE documentation, and I noticed something that seems strange for me: the routing.ms_decode node appears before the routing.ms_encode node in the signal chain.

However, according to the documentation for routing.ms_encode, it should be placed at the beginning of the chain to encode a stereo signal into Mid-Side, which can then be processed and later decoded with routing.ms_decode.

From Doc about ms_encode : "To use the routing.ms_encode node, you would typically place it in a processing chain with the stereo input you want to encode, and then use a container.multi node to split the signal into its mid and side components. You can then process the components separately and recombine them using a routing.ms_decode node placed later in the chain."

This seems like a contradiction

Image from Hise Documentation :

@modularsamples

Thank you! That was very helpful.

I just have one last question:
If I want to modulate the gain using the LFO from GlobalModulator Container (the one in your snippet), how can I make the last gain node from my screenshot effectively control the gain of the AudioLoopPlayer1, which is located higher in the module tree?

Hi,

I'm wondering if it's possible to make the Global Modulation LFO start or retrigger only when an audio signal is detected, like when sound enters.

@Lindon
Mhh, I'm not sure I fully understand what "compiling the project" means exactly.
I get the part about compiling HISE itself, but I thought compiling a project was just the same as exporting it as a VST or instrument.

Anyway, I simply created a new project from scratch and now 5sec delay with jdelay in scriptnode works!
Thanks a lot!

@Lindon
Sorry, I'm having an issue again, I must be doing something wrong.
I tried compiling with the extra definition in JUCE, and I can see that the extra delay time is recognized in the Help > Toolbar info.

However, as soon as I use jDelay with a delay time above 3 seconds, HISE crashes.
.

Do I just need to write the line in the HISE settings?

But then, how do I compile it so that it actually takes effect?

@Lindon

Thanks!

@Lindon
Thanks!

But sorry , I still can't figure out how to access or modify HISE_MAX_DELAY_TIME_SAMPLES.

For example, in scriptnode, when using djDelay, how exactly do I access the extra definition you're referring to?