Check, in order, if the io is connected to another Ardour route, then a user bundle, then some physical ports with simple configuration, and lastly another client. Before, Routes were considered connected as long as every io port connected to that route, even if the channel order was mixed or worse if all ports were connected to the same channel. Now Routes and Bundles are considered connected if they are exclusively connected, in the right order, to all their ports with matching datatype. |
||
---|---|---|
doc | ||
export | ||
gtk2_ardour | ||
headless | ||
libs | ||
mcp | ||
midi_maps | ||
msvc_extra_headers | ||
MSVCardour3 | ||
MSVCMixbus3 | ||
MSVCvst_scan | ||
osc | ||
osc_interfaces/touchosc | ||
patches | ||
patchfiles | ||
scripts | ||
session_utils | ||
templates | ||
tools | ||
vst | ||
.dir-locals.el | ||
.gitattributes | ||
.gitignore | ||
ardour-3.ttl | ||
ardour.1 | ||
ardour.1.es | ||
ardour.1.fr | ||
ardour.1.ru | ||
COPYING | ||
instant.xml | ||
instant.xml.sae | ||
msvc32-fixup.pl | ||
PACKAGER_README | ||
README | ||
README-GITHUB.txt | ||
system_config | ||
testfile.flac | ||
testfile.ogg | ||
TRANSLATORS | ||
waf | ||
wscript |
Please see the Ardour web site at http://ardour.org/ for all documentation.. For information on building ardour: http://ardour.org/development.html