livetrax

History

Paul Davis bd229936ec add finite state machine to control/manage transport state		2019-09-17 18:26:03 -06:00
..
ardour-util.sh.in
common.cc	Update utility and tools GPL boilerplate and (C) from git log	2019-08-03 15:53:17 +02:00
common.h	Update utility and tools GPL boilerplate and (C) from git log	2019-08-03 15:53:17 +02:00
copy-mixer.cc	Don't print usage to stdout for invalid parameters	2019-08-15 01:09:26 +02:00
debug
example.cc	Update utility and tools GPL boilerplate and (C) from git log	2019-08-03 15:53:17 +02:00
export.cc	add finite state machine to control/manage transport state	2019-09-17 18:26:03 -06:00
fix_bbtppq.cc	Don't print usage to stdout for invalid parameters	2019-08-15 01:09:26 +02:00
new_empty_session.cc	Don't print usage to stdout for invalid parameters	2019-08-15 01:09:26 +02:00
new_session.cc	Don't print usage to stdout for invalid parameters	2019-08-15 01:09:26 +02:00
README	Update session-utils Readme	2017-09-27 20:03:08 +02:00
run
wscript

README

Ardour Session Utilities
========================

This folder contains some tools which directly use libardour to access ardour
sessions.

The overall goal it to provide some non-interactive unix-style commandline
tools, which are installed along with DAW.

These tools depend on the "dummy" backend to be available, configure ardour with e.g.

  ./waf configure --with-backends=jack,alsa,dummy ...


Adding new tools
----------------

One C++ source per tool, see "example.cc" and "export.cc"

  cp session_utils/example.cc session_utils/your_new_tool_name.cc
  edit session_utils/new_tool_name.cc
  ./waf

The tool is automatically compiled and deployed when installing, using the
program-name as prefix.  e.g.  "export.cc" becomes "ardour4-export".
(or "mixbus3-export", depending on the project configuration)


Test run from the source
------------------------

  cd session_utils
  ./run ardour6-your_new_tool_name

or

  ./run ardour6-export --help

and to debug the tool under gdb/lldb:

  ./debug ardour6-export