livetrax

History

Robin Gareus 962d8922ab Enforce session-util app name This fixes an issue with some macOS that create index oe meta-data files e.g. `session_utils/._export.cc`. Besides that it increases consistency.		2020-11-15 01:21:40 +01:00
..
ardour-util.sh.in
common.cc	Transmitter::Debug implementation 1/2	2020-10-13 21:58:26 +02:00
common.h	Transmitter::Debug implementation 1/2	2020-10-13 21:58:26 +02:00
copy-mixer.cc
debug
example.cc
export.cc
fix_bbtppq.cc	Fix --no-nls, i18n include order in UI -- #8361	2020-08-19 17:40:02 +02:00
new_empty_session.cc
new_session.cc
README	Enforce session-util app name	2020-11-15 01:21:40 +01:00
run
wscript	Enforce session-util app name	2020-11-15 01:21:40 +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