3 No configuration is required if everything is to meant be run on a single
4 machine, and the version of Ardour comes from <a href="http://www.ardour.org"
5 title="http://www.ardour.org">http://www.ardour.org</a>. Everything is
6 pre-configured and included with the download/install.
9 <h2>Single Machine</h2>
12 If Ardour is compiled from source, or installed from a 3rd party
13 repository, three additional tools will need to be installed manually, which are
14 used by Ardour to provide video features:
18 <li>xjadeo (the video monitor application): <a
19 href="http://xjadeo.sourceforge.net/" title="http://xjadeo.sourceforge.net/"
20 rel="nofollow">http://xjadeo.sf.net</a></li>
21 <li>harvid (a video decoder used for the thumbnail timeline):
22 <a href="http://x42.github.io/harvid/" title="http://x42.github.io/harvid/"
23 rel="nofollow">http://x42.github.com/harvid/</a></li>
24 <li>ffmpeg, ffprobe (used to import/export video, extract soundtracks and query
25 video information): <a href="http://ffmpeg.org" title="http://ffmpeg.org"
26 rel="nofollow">http://ffmpeg.org</a></li>
30 Ardour requires xjadeo ≥ version 0.6.4, harvid ≥ version 0.7.0 and
31 ffmpeg (known to work versions: 1.2, 2.8.2)
35 The Ardour development team is in control of the first two applications.
36 ffmpeg however can be a bit of a problem. To avoid conflicts with distribution
37 packages, Ardour looks for <code>ffmpeg_harvid</code> and
38 <code>ffprobe_harvid</code>.
42 All four applications need to be found in <code>$PATH</code> (e.g.
43 <code>$HOME/bin</code> or <code>/usr/local/bin</code>). For convenience the
44 binary releases of harvid include ffmpeg_harvid and ffprobe_harvid, but if the
45 distribution provides suitable ffmpeg commands, symbolic links can be created
46 to the distribution-provided binaries:
49 <kbd class="cmd lin">sudo ln -s /usr/bin/ffmpeg /usr/bin/ffmpeg_harvid</kbd>
50 <kbd class="cmd lin">sudo ln -s /usr/bin/ffprobe /usr/bin/ffprobe_harvid</kbd>
53 Binary releases are available from ardour.org as well as an installer script:
54 <a href="https://github.com/Ardour/ardour/blob/master/tools/videotimeline/install_video_tools.sh"
55 title="https://github.com/Ardour/ardour/blob/master/tools/videotimeline/install_video_tools.sh"
56 rel="nofollow">install_video_tools.sh</a>.
60 The easiest way to install the video-utilities is by running the following
64 <kbd class="cmd lin">sh -c "$(curl -s -L http://git.io/tVUCkw)"</kbd>
69 As Setting up a proper A/V post-production studio can be a complicated task, it
70 is advised to read the info in the previous section to get familiar with
71 the tools involved first. As much as the Ardour team streamlines and simplifies
72 the <em>single machine</em> setup, the <dfn>studio setup</dfn> is focused on
78 <li>Synchronization ardour → video-display-box should be accomplished by
79 external means. Jack-transport(netjack), MTC, LTC
80 (<abbr title="Open Sound Control—"postmodern MIDI"">OSC</abbr>
81 and/or ssh-pipe work but introduce additional latency + jitter)</li>
82 <li>Ardour launches <code>XJREMOTE</code> (environment variable, default
83 'xjremote' which comes with xjadeo).</li>
84 <li>Either use a custom shell script that ssh'es into the remote box and
85 launches/controls xjadeo there, selects the sync-source and passes though
86 communication between ardour ⇔ xjadeo via ssh (xjadeo is launched stopped with
88 <li>…or override xjremote's behavior—instead of IPC with a local
89 running xjadeo-process, using <abbr title="Open Sound
90 Control—"postmodern MIDI"">OSC</abbr> for example. Xjadeo would
91 run permanently and Ardour will just tell it to load files and set offsets via
92 <acronym title="Open Sound Control—"postmodern
93 MIDI"">OSC</acronym>. See <a
94 href="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc"
95 title="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc"
96 rel="nofollow">xjremote-osc</a> example script.</li>
97 <li>If the video server runs remotely, Ardour needs to be configured in Ardour >
98 Preference > Video (hostname of the video-server).</li>
99 <li>Ideally the machines have a common shared folder (NFS or similar).
100 Ardour's import (audio-extract) and export (mux) functionality depends on
101 having access to the video file. Also Ardour's video-import transcodes the file
102 into a suitable proxy-format that allows reliable seeking to any