ardour

History

Robin Gareus d9ce918c41 Small test tool for PBD::Transmitter thread-safety tests Launch as ``` ./session_utils/run ardour7-debug_transmitter ./session_utils/debug ardour7-debug_transmitter ```		2022-06-24 21:11:51 +02:00
..
ardour-util.sh.in
common.cc	Update call_slot() API, inform caller if slot cannot be queued	2022-06-09 01:46:27 +02:00
common.h
copy-mixer.cc	Fix various typos	2022-04-08 19:51:02 +02:00
debug
debug_transmitter.cc	Small test tool for PBD::Transmitter thread-safety tests	2022-06-24 21:11:51 +02:00
example.cc
export.cc	Bail out if export cannot be started	2020-12-08 01:10:00 +01:00
new_empty_session.cc
new_session.cc
README	Enforce session-util app name	2020-11-15 01:21:40 +01:00
run
wscript	wscript: consistently have at most one empty separator line	2022-04-09 12:16:40 +02: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