On Sat, 2012-03-03 at 07:36 +0100, Albert Graef wrote: > On 03/03/2012 06:50 AM, David Robillard wrote: > > There is also the chicken& egg problem, last I checked there wasn't an > > OSC note standard in use anywhere to have Ardour send... > > I don't see why an OSC track should make any assumptions about the > semantics of OSC messages. It should just treat it as control data and > allow to record it from an OSC client (which might also be an LV2 plugin > which produces OSC messages), edit it, and play it back to another OSC > server (or LV2 plugin which consumes OSC messages).
Hm? How would a sequencer display or edit OSC data without even knowing how to represent a note or a control? Sure, you could just implement dumb raw OSC recording and playback, but there's little point in using a DAW for that (not to mention little practical musical use) -dr _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
