livetrax

History

Mads Kiilerich 8bb91099c5 wscript: drop configure statements already present in the top level wscript Avoid repeated pointless configure messages like: Checking for 'g++' (C++ compiler!) : /usr/lib64/ccache/g++ Checking for 'gcc' (C compiler) : /usr/lib64/ccache/gcc		2022-01-22 22:19:03 +01:00
..
ardour-util.sh.in
common.cc	Do not implicitly modify VST support config parameters	2021-08-10 15:54:37 +02:00
common.h
copy-mixer.cc
debug
example.cc
export.cc
new_empty_session.cc
new_session.cc
README
run
wscript	wscript: drop configure statements already present in the top level wscript	2022-01-22 22:19:03 +01: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).
Tool names must start with lower-case alphabetic letter [a-z].


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