2017-02-25 00:30:29 -05:00
|
|
|
|
2013-02-14 07:30:39 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
Ardour will only ever deal with a single <dfn>audio device</dfn>. When it is
|
|
|
|
desired to use more than one audio device at the same time, there are two
|
|
|
|
choices:
|
2014-02-02 18:09:23 -05:00
|
|
|
</p>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<ul>
|
2017-03-14 23:57:34 -04:00
|
|
|
<li>Use Ardour to start JACK (which handles all audio I/O), and create a
|
|
|
|
"fake" audio device which represents all the multiple devices to be used. How
|
|
|
|
to do this is platform dependent and described below.</li>
|
|
|
|
<li>Use a different tool to start JACK and manage all the devices.</li>
|
2014-02-03 19:33:51 -05:00
|
|
|
</ul>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2013-02-14 07:30:39 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
Ardour is fundamentally designed to be a component in a pro-audio/music
|
|
|
|
creation environment. Standard operating practice for such setups involves
|
|
|
|
using only a single digital <dfn>sample clock</dfn> (something counting off
|
|
|
|
the time between audio samples). This means that trying to use multiple
|
|
|
|
independent soundcards is problematic, because each soundcard has its own
|
|
|
|
sample clock, running independently from the others. Over time, these
|
|
|
|
different clocks <dfn>drift</dfn> out of sync with each other, which causes
|
|
|
|
glitches in the audio. This drift cannot be stopped, although in some cases
|
|
|
|
the effects may be insignificant enough that they might not be noticeable.
|
2013-02-14 07:30:39 -05:00
|
|
|
</p>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2013-01-29 19:26:36 -05:00
|
|
|
<p>
|
2019-01-24 06:00:52 -05:00
|
|
|
Thus, in an ideal world, a single device with a single clock and all the inputs,
|
|
|
|
outputs and other features needed should be used. Of course, there are those
|
|
|
|
who like to point out that this is not an ideal world, and believe that software
|
|
|
|
should make up for this.
|
2013-01-29 19:26:36 -05:00
|
|
|
</p>
|
2013-02-14 07:30:39 -05:00
|
|
|
|
2014-02-02 18:09:23 -05:00
|
|
|
<h2>OS X</h2>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2013-02-20 19:19:11 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
In CoreAudio, <dfn>aggregate devices</dfn> provide a method to use multiple
|
|
|
|
soundcards as a single device. For example, two eight-channel devices can be
|
|
|
|
aggregated so that 16 channels can be recorded in Ardour.
|
2013-02-20 19:19:11 -05:00
|
|
|
</p>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2020-09-17 11:57:06 -04:00
|
|
|
<p>
|
|
|
|
Another example is using Soundflower to route audio to Ardour. To output the
|
|
|
|
audio through the speakers you will have to create an aggregate device to specify
|
|
|
|
Soundflower as the input and Built-in-Output as the output. In the Audio/MIDI Setup
|
|
|
|
in Ardour specify the aggregate device as both the Input and Output devices. And then
|
|
|
|
on the master track ensure you have specified the correct output channels. For example,
|
|
|
|
if you are using Soundflower(64) as input, Channels 65/66 will be the output
|
|
|
|
channels on your master track.
|
|
|
|
</p>
|
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<div class="note">
|
2013-02-20 19:19:11 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
When using a <em>single</em> typical 3rd party audio interface (such as those
|
|
|
|
from Apogee, RME, Presonus, and many others), <em>or</em> using JackPilot or
|
|
|
|
a similar application to start JACK, there is no need to worry about any of
|
|
|
|
this. An aggregate device only needs to be set up if any of the following
|
|
|
|
conditions are true:
|
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<ul>
|
2017-03-14 23:57:34 -04:00
|
|
|
<li>Two entirely separate devices are used <em>and</em> JACK is started using
|
|
|
|
Ardour</li>
|
|
|
|
<li>A <dfn>builtin audio device is used</dfn> <em>and</em> JACK is started
|
|
|
|
using Ardour</li>
|
|
|
|
<li>More than two entirely separate devices are used</li>
|
2014-02-03 19:33:51 -05:00
|
|
|
</ul>
|
2017-02-25 00:30:29 -05:00
|
|
|
</div>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
In the case of a builtin audio device, an aggregate device that combines
|
|
|
|
"Builtin Input" and "Builtin Output" into one device needs to be created.
|
2013-02-20 19:21:15 -05:00
|
|
|
</p>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<p>
|
2017-03-14 23:57:34 -04:00
|
|
|
The precise instructions for creating an aggregate device on OS X have varied
|
|
|
|
from one released to another. Please read <a
|
|
|
|
href="https://support.apple.com/en-us/HT202000">https://support.apple.com/en-us/HT202000</a>.
|
2014-02-03 19:33:51 -05:00
|
|
|
</p>
|
2013-02-14 07:30:39 -05:00
|
|
|
|
2014-02-02 18:09:23 -05:00
|
|
|
<h2>Linux</h2>
|
2017-03-14 23:57:34 -04:00
|
|
|
|
2013-02-14 07:30:39 -05:00
|
|
|
<p>
|
2017-01-03 12:03:08 -05:00
|
|
|
Please see the instructions at <a href="http://jackaudio.org/faq/"
|
2017-03-14 23:57:34 -04:00
|
|
|
title="http://jackaudio.org/faq/">http://jackaudio.org/faq</a>.
|
2013-02-14 07:30:39 -05:00
|
|
|
</p>
|
2017-02-13 14:53:37 -05:00
|
|
|
|