Precisely Defining Curves

I still use Max to drive GP via OSC when I want to use Max style abstractions. Works very well

Yep, I think the hardest work is defining the lines where each one does its job best…which takes time
Dave, would you have a simple example of coordination between GP/Max via OSC?

Not simple (at least not from development perspective, but trivial for use) - here’s an example

The interesting abstraction is that red one. It presents itself as an extended [midiformat] object with inputs that accept note, cc messages, aftertouch, etc but internally those messages get translated into OSC messages that the GP Midi In OSC blocks can parse.

In this model, Max handles all keyboard input - e.g, the [KronosXCore] and [BottomLeftCore] objects represent a Kronos keyboard and (in my system) the bottom of three light weight controllers and they look like [midiparse] objects that just produce notes, CC messages etc.

Then lots of abstractions to make it easy to construct useful processes, eg the [KeyboardLayer] object lets you define a split range with an optional transpose value

1 Like