How realistic would it be to use Ardour as a control surface?

There is the online low-latency software Jamulus <https://jamulus.io>
that features a comparatively familiar mixer strip in its UI.  It has a
primitive input-only optional Midi connection to a controller that only
serves the volume faders.  The mixer strips, though, have mute and solo
buttons and (depending on the mode) pan controls.

The Jamulus server can create recordings of online session which it puts
down in the form of .lof (Audacity session files) and .rpp (Reaper) as
well as stem wavs.  It cannot serve them, however.

The mixer strips are actually per-client, are communicated to the
central server which then creates a mix particular to each client.  So
basically every user gets to create his own mix from the _live_ stems.

Now instead of teaching the Jamulus client more details about a
wagonload of potentially suitable control surfaces, the cheap trick
would be to teach it how to let Ardour do all the work and then pick up
(and communicate back) the mixer strip settings from and to Ardour.

Does Ardour do something like that?  Can two Ardour instances, for
example, synchronise/share some mixer strips via OSC or, say, a Jack
Midi connection?

-- 
David Kastrup

_______________________________________________
Ardour-Users mailing list
[email protected]
To unsubscribe  or change your mailing preferences please visit:
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org