blob: 4ee2fda69899eaa9221677681d21c9e5a43ecbc1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
<?xml version="1.0" standalone="no"?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<section id="sn-video-sync-via-mtc">
<title>Video Synchronization via MTC</title>
<note>
<para>
if you do not have any MIDI I/O available on your system, then it is
impossible to use MIDI Time Code.
</para>
</note>
<section id="ardour-as-mtc-master">
<title>Using Ardour as an MTC Master</title>
<para></para>
</section>
<section id="ardour-as-mtc-slave">
<title>Using Ardour as an MTC Slave</title>
<orderedlist>
<listitem>
<para>
ensure that you have defined at least one MIDI port in your ardour.rc
file. The default configuration includes a single port that is part of
the ALSA MIDI router/sequencer system.
</para>
</listitem>
<listitem>
<para>
open the Options Editor.
</para>
</listitem>
<listitem>
<para>
switch to the <guilabel>MIDI</guilabel> tab.
</para>
</listitem>
<listitem>
<para>
if you have more than one MIDI port, click on the button in the <guilabel>MTC</guilabel> column
for the port you plan where MTC will be received.
</para>
</listitem>
<listitem>
<para>
if you have more than one MIDI port, then you should probably click on
the button in the <guilabel>MMC</guilabel> column for the port you plan where MMC will be
received. This is not required, but many devices that send MTC also send
MIDI Machine Control commands and may not be able to control Ardour
correctly unless Ardour is also responding to MMC.
</para>
</listitem>
<listitem>
<para>
switch to the <guilabel>Sync</guilabel> tab. Open the <guilabel>Positional Sync</guilabel> selector to see the
list of possible sources of timeline synchronization:
</para>
<variablelist>
<title>Syncronization Options</title>
<varlistentry>
<term>Internal</term>
<listitem>
<para>
use Ardour's own sense of position and time
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Slave to JACK</term>
<listitem>
<para>
follow JACK Transport information
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Slave to MTC</term>
<listitem>
<para>
follow incoming MTC information
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
<listitem>
<para>
choose <guimenuitem>Slave to MTC</guimenuitem>
</para>
</listitem>
</orderedlist>
<para>
To test that Ardour is now slaved, press the <guibutton>Play</guibutton> button on the MTC
master, or some other action that will cause it to start transmitting MTC.
Ardour should jump to the position indicated by incoming MTC, and start
playing. Press <guibutton>Stop</guibutton> on the master (or do some other action that will
cause the master to stop sending MTC) and Ardour should stop at the precise
time indicated by the master.
</para>
</section>
<!--
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="Some_Subsection.xml" />
-->
</section>
|
