---
<p>
-Ardour 3.x requires no configuration if you intend to run everything on a single machine, and if you acquired Ardour 3.x from <a href="http://www.ardour.org" title="http://www.ardour.org" rel="nofollow">http://www.ardour.org</a>, everything is pre-configured and included with the download/install.
+No configuration is required if you intend to run everything on a single machine, and if you acquired Ardour from <a href="http://www.ardour.org" title="http://www.ardour.org">http://www.ardour.org</a>, everything is pre-configured and included with the download/install.
</p>
-
<h2>Single Machine</h2>
<p>
-If you compile Ardour 3.x from source, or have installed it from a 3rd party, additional tools will need to be installed.
+If you compile Ardour from source, or have installed it from a 3rd party repository, additional tools will need to be installed manually.
</p>
<p>
-There are three separate standalone tools involved which are used by Ardour 3.x to provide video facilities.
+There are three separate standalone tools which are used by Ardour to provide video features.
</p>
<ul>
<li>xjadeo – the video monitor window<a href="http://xjadeo.sf.net" title="http://xjadeo.sf.net" rel="nofollow">http://xjadeo.sf.net</a>
</ul>
<p>
-Ardour 3.x requires xjadeo >= version 0.6.4, harvid >= version 0.7.0 and ffmpeg == 1.2.
+Ardour requires xjadeo ≥ version 0.6.4, harvid ≥ version 0.7.0 and ffmpeg = 1.2.
</p>
<p>
-The ardour-dev team is <em>in control</em> of the first two applications. ffmpeg can be a bit of a problem.
-To avoid conflicts with distribution packages, ardour looks for <code>ffmpeg_harvid</code> and <code>ffprobe_harvid</code>.
+The Ardour development team is <em>in control</em> of the first two applications. ffmpeg can be a bit of a problem.
+To avoid conflicts with distribution packages, Ardour looks for <code>ffmpeg_harvid</code> and <code>ffprobe_harvid</code>.
</p>
<p>
</p>
<p>
-You can run it directly as:
+The easiest way to install the video-utilities is by running the following line in a terminal:
</p>
<pre class="code">sh -c "$(curl -s -L http://git.io/tVUCkw)"</pre>
<h2>Studio Setup</h2>
<p>
-Please read the info in the previous section to familiarize yourself with the tools involved.
+Please read the info in the previous section to familiarize yourself with the tools involved first.
Setting up a proper A/V post-production studio can be a complicated task. As much as we streamline and simply the <em>single machine</em> setup, the studio-setup is focused on modularity.
</p>
<p>
<em>TODO</em>
</p>
+
<ul>
-<li>Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (<acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym> and/or ssh-pipe work but introduce additional latency + jitter)
+<li>Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (<abbr title="Open Sound Control - "postmodern MIDI"">OSC</abbr> and/or ssh-pipe work but introduce additional latency + jitter)
</li>
</ul>
<ul>
-<li>Ardour launches <code>XJREMOTE</code> (environment variable, default 'xjremote' which comes with xjadeo also on OSX).
+<li>Ardour launches <code>XJREMOTE</code> (environment variable, default 'xjremote' which comes with xjadeo).
</li>
</ul>
<ul>
</li>
</ul>
<ul>
-<li>..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using <a
cronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym> for example. xjadeo would run permanently and ardour will just tell it to load files and set offsets via <acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym>. see <a href="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" title="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" rel="nofollow">xjremote-osc</a> example script.
+<li>..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using <a
bbr title="Open Sound Control - "postmodern MIDI"">OSC</abbr> for example. xjadeo would run permanently and Ardour will just tell it to load files and set offsets via <acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym>. see <a href="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" title="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" rel="nofollow">xjremote-osc</a> example script.
</li>
</ul>
<ul>
</ul>
<p>
-Ideally the machines have a common shared folder (NFS or similar). Ardour's import (audio-extract) and export (mux) functionality depends on having access to the video file. Also ardour video-import transcodes the file into a suitable proxy-format that allows reliable seeking to any frame…
+Ideally the machines have a common shared folder (NFS or similar). Ardour's import (audio-extract) and export (mux) functionality depends on having access to the video file. Also Ardour's video-import transcodes the file into a suitable proxy-format that allows reliable seeking to any frame…
</p>
projects / ardour-manual / blobdiff