[Ardour-Dev] hardour (headless ardour)

Paul Davis paul at linuxaudiosystems.com
Tue Jul 8 05:08:30 PDT 2014

On Tue, Jul 8, 2014 at 4:01 AM, David Santamauro <david.santamauro at gmail.com
> wrote:

> On 07/07/2014 06:26 AM, Paul Davis wrote:
>> On Mon, Jul 7, 2014 at 6:16 AM, David Santamauro
>> <david.santamauro at gmail.com <mailto:david.santamauro at gmail.com>> wrote:
>>     Paul,
>>     On 02/24/2014 08:06 PM, Paul Davis wrote:
>>         git, in the cairocanvas branch, now contains a standalone,
>>         command line
>>         program that loads and runs an Ardour session. It has no GUI and
>>         is not
>>         interactive via the terminal.
>>     What is the use-case for something like this?
>> (1) a working example of the code required to load and run an ardour
>> session
>> (2) building standalone systems based on ardour that are controlled by
>> means other than a GUI (MIDI, OSC, etc)
> Very interesting. What do you see as communication protocol between this
> headless ardour and some future client application if not MIDI or OSC?

It isn't something I'm thinking about. Various people ask from time to time
about a non-GUI version of Ardour, so I took some work Carl Hetherington
had done, cleaned it up just a little bit, and put it into the repository
as a build target. MIDI (Mackie Control, probably) and OSC are the obvious
choices, but in an ideal world there are better protocols like Euphonix
stuff that one could consider.

> Is the ultimate goal seeking functionality like these?
> http://www.soundcraft.com/apps/visi-remote.aspx?pid=176
> http://www.behringer.com/en/products/x32.aspx

I guess so, but I have way too much else on my plate to be thinking about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20140708/ae514d97/attachment.htm>

More information about the Ardour-Dev mailing list