It’s close enough that if they patent it, I’ll be extremely pissed off.

Beta and Presets just wrapped up on this one.

Of course, a controlling function, f(t) or f(c) (c for controller input), can also be controlled by another controller function, but that’s its own can of worms. I really need to update that article and add some diagrams, to see if I can clarify things. I really hate not being able to communicate what I can see clearly in my head.

The audio-rate key frames would only apply to key frames that are set up as a function of time f(t). Yes, the idea is that they’ll evaluate for every sample (in blocks, like all the other sample-rate stuff). What this would possibly allow is to run a function so fast that it outputs a signal that can be heard.

So, to answer your question, yes. :-)

I had a look at your wiki article – I’m particularly interested by your idea of audio rate keyframe morphing. Are you talking about modulating that at an audio rate, producing FM and AM effects (depending on the synth controls affected), or just having the modulation curves work at extra high sampling rate and bit depth for super smoothness and accuracy?

Darren Landrum: as it happens, your keyframes are a perfect analogy for the sound variations in Kore. Each sound variation holds different synth knob settings and depending on what cells you save the variations into and how you morph through them, you get slight or radical movements of the different synth controls. You can also snap instantly to the different variations with the controller. The interesting thing is, this works for any third-party instrument or effect that allows host automation and can be hosted in Kore, not only for NI plugins.