livetrax

History

Paul Davis c60d8cf747 (libs) call ARDOUR::init_post_engine() from within libardour rather than requiring "users" of the library to arrange for it		2019-01-16 15:29:38 -06:00
..
ardour-util.sh.in
common.cc	(libs) call ARDOUR::init_post_engine() from within libardour rather than requiring "users" of the library to arrange for it	2019-01-16 15:29:38 -06:00
common.h	Add session-util to create a new empty session	2017-09-27 18:22:49 +02:00
copy-mixer.cc	Yet another spelling mistake fix	2018-02-28 20:48:49 +01:00
debug
example.cc
export.cc	Wimplicit-fallthrough fixes for tools/utils	2018-10-26 14:53:53 +02:00
fix_bbtppq.cc	convert codebase to use Temporal for various time types	2017-09-24 12:03:54 -04:00
new_empty_session.cc	Minor refinement of new session util	2017-09-27 18:50:24 +02:00
README	Update session-utils Readme	2017-09-27 20:03:08 +02:00
run
wscript	convert codebase to use Temporal for various time types	2017-09-24 12:03:54 -04:00

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