Re: Ardour-Dev Digest, Vol 134, Issue 1
Paul Davis <[email protected]>
| Newsgroups | gmane.comp.audio.ardour.devel |
|---|---|
| Message-ID | <CAFa_cK=0K1tEWNDSV2VOnPrr5kN0Og9uO+Ng58csgumk8++iJg@mail.gmail.com> |
On Fri, Jun 5, 2015 at 3:18 PM, Patrick.Gilles Maillot < [email protected]> wrote: > I was just hoping to find something similar (better in fact) from Ardour “probably > one of the most OSC-controllable audio applications around”. While this may > be the case from Ardour to its clients, the other way around doesn’t seem > so (i.e. what is the receiving port for Ardour?). > Ardour uses 3189, or whatever value you configure via the OSC GUI (double click on "OSC" in the list of available control surfaces. Nobody developing Ardour has ever had an interest in making it a *controller* for another OSC receiver. Doing so wouldn't be very hard, but it has never been anyone's goal. As you yourself noted, you had to create a middle-man between Reaper and the X32 (mostly because you don't have access to the relevant source code in Reaper, I would guess). Doing this directly in Ardour is entirely possible, though it should probably be done as a new dedicated X32 control surface module (all control surface code is dynamically discovered and loaded). --p _______________________________________________ ardour-dev mailing list [email protected] http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org