OSC Control strategies

Imagemap

hide

OSC Control strategies

hide

hide

Per-note parameters

leaf

Possible with protocols like OSC

leaf

Parameters are sent to particular nodes

hide

The node id can be part of the address or part of the attributes

leaf

If part of the address, it means that applications might require different handlers, so this is useful when the number of nodes is limited at compile time

leaf

If part of the attributes, it means that pattern matching is no longer available, but parsing can be handled in a single function

hide

Interpolation/smoothing

leaf

OSC messages arrive at an unexpected rate and granularity

leaf

And jumps can be large

leaf

Smoothing: Constant rate or constant time?

leaf

non-linear smooting (different rate at start and end)

hide

Using low-pass filters

leaf

Filters tend not to arrive at their destination, so additional checks might need to be added

hide

leaf

Events initiate a sound, by allocating a voice, placing a node in the rendering graph, triggering an envelope, etc.

leaf

Like MIDI and other control systems, OSC does not have any information about the audio engine, and cannot know when a voice is free or has finished its release after an "off" message has been sent

leaf

Events can also directly map to specific function on the receiver