- <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>
- <li>Ardour launches <code>XJREMOTE</code> (environment variable, default 'xjremote' which comes with xjadeo).</li>
- <li>Either use a custom shell script that ssh'es into the remote box and launches/controls xjadeo there, selects the sync-source and passes though communication between ardour ⇔ xjadeo via ssh (xjadeo is launched stopped with the session).</li>
- <li>..or override xjremote's behavior—instead of IPC with a local running xjadeo-process, using <abbr 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>
- <li>If the video server runs remotely, Ardour needs to be configured in Ardour > Preference > Video (hostname of the video-server).</li>
- <li>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…</li>
+ <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>
+ <li>Ardour launches <code>XJREMOTE</code> (environment variable, default
+ 'xjremote' which comes with xjadeo).</li>
+ <li>Either use a custom shell script that ssh'es into the remote box and
+ launches/controls xjadeo there, selects the sync-source and passes though
+ communication between ardour ⇔ xjadeo via ssh (xjadeo is launched stopped with
+ the session).</li>
+ <li>…or override xjremote's behavior—instead of IPC with a local
+ running xjadeo-process, using <abbr 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>
+ <li>If the video server runs remotely, Ardour needs to be configured in Ardour >
+ Preference > Video (hostname of the video-server).</li>
+ <li>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…</li>