[Ardour-Dev] OSC sequencing with Ardour?

Pau Arumí Albó parumi at iua.upf.edu
Fri May 16 10:22:40 PDT 2008

El dv 16 de 05 de 2008 a les 10:51 -0600, en/na Michael Taht va
> Pau Arumí wrote:
> > Hi all,
> >
> > I have a need to sequence (play and record) OSC messages. 
> > The scenario is that i have an app that generates OSC events (reacting
> > to the user) and a second app that receives the events to render audio.
> >
> > The question is: would Ardour be useful for sequencing arbitrary OSC
> > messages*? I guess the answer is no. But in that case: are there tools
> > for that job? and would it be interesting (or is it planned) to add this
> > kind of feature in Ardour?
> >
> > * or a restricted form of messages: "PATH/ value" 
> >
> >   
> >To be more specific: i am interested in seeing/editing OSC messages as
> >track automation data.
> Your second message clarified matters considerably. I think.
> If I understand you correctly, OSC would be the transport for controller data like pan/gain, etc, which would then be stored in ardour as normal automation data. An OSC standard for ardour

> I am in the process of improving ardour's OSC support - and rolling a protocol specification
> see http://tracker.ardour.org/view.php?id=2239 for current progress and patches
> ... and am very interested in the types of messages potential controllers generate, and use cases in general. What kind of device(s) are you using? 

> As for storing OSC data directly on a timeline track, and regenerating it on playback, this strikes me as doable (in ardour 3.x!), and "interesting" for driving external OSC devices that ardour does not need to understand (say, for example, theater lighting) 

I'm not interested in using OSC to control the mix (or whatever Ardour
control) but only in the second case you mentioned.

It is not theater lighting in the case at hand but a 3-D acoustic
modeler app. And the OSC message sender is not a hardware controller but
a 3-D graphics (gaming) engine that sends the sound sources and
listeners positions.

The benefits i see in using Ardour for this are:
      * aligned to the OSC controls i also need to record and play audio
        sources (that also feeds the acoustic renderer)
      * the existing automation user interface is already suitable for
        editing each OSC control.

It is good to know that sounds interesting and seems doable in 3.x


More information about the Ardour-Dev mailing list