13
0
livetrax/manual/xml/video_synchronization_via_mtc.xml
Tim Mayberry 56e384349b Add the ardour manual converted to docbook format with only a few minor
additions.

Add dbhelper.vim key stroke mappings I use for working with docbook source.

There are no xsl or css files for customizing the html output so it will 
look really boring...this will only be temporary.

Support for content localization and generation of pdf's is planned.



git-svn-id: svn://localhost/ardour2/trunk@1405 d708f5d6-7413-0410-9779-e7cbd77b26cf
2007-02-02 04:29:55 +00:00

111 lines
3.2 KiB
XML

<?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>