@d-healey That's the other reason why I bring this up: I don't know for certain. My guess is it won't affect other platforms since the only difference is that I explicitly specify which Point class the code is referring to, which, evidently, was JUCE's anyway.

I appreciate the suggestion of combining separate modulators. Thankfully, I've just found a method that makes use of the apparent fact that the modulation amount can be scripted to have a value greater than one, so the problem is solved. :)

@Cyberdyne387 scriptnode is your friend...☺

Hi Cyberdyne,

yes it was pretty embarassing to go to the ADC this year running an ancient JUCE version and there are a ton of cool features that have been added since then (a better convolution engine, DSP algorithms and many improvements for iOS).

It's definitely on my top priority list to take the leap to the current JUCE version, but it involves changing the entire build procedure and modifying the JUCE codebase with the few custom additions I made for HISE. Don't hold your breath for it (but I try to do it this year).

I said I fix it right away, but then I got lazy :)

Yeah, first time I was literally pointing my finger at the debugger and laugh :)

I regret to say I just left the house for the weekend, so you'll have to wait until Monday before I can confirm how many outputs are listed in the JUCE plugin host. Logic itself is fine now, though!