Capitalization: ardour -> Ardour
This commit is contained in:
David Bolton
parent
037f00b703
commit
ae870f36cf
|
|
@ -11,7 +11,7 @@ title: MIDI on OS X
|
|||
<h4>Inside Ardour</h4>
|
||||
<p>There are multiple locations MIDI ports can show up in Ardour's MIDI connection matrix. CoreMIDI ports that are created by other software clients as well as JACK MIDI ports created by other software clients will show up under the "Other" tab. CoreMIDI hardware ports show up under the "Hardware" tab.</p>
|
||||
<h4>External Applications</h4>
|
||||
<p> There are multiple options for connecting MIDI ports outside of ardour</p>
|
||||
<p> There are multiple options for connecting MIDI ports outside of Ardour</p>
|
||||
<p><a href="http://www.snoize.com/MIDIMonitor/">MIDI Monitor</a> is a handy tool for doing various things with midi on OS X.</p>
|
||||
<p><a href="http://notahat.com/midi_patchbay">MIDI Patchbay</a> is a handy tool for connecting MIDI ports.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Clocks in Ardour are the basic way of displaying time values precisely. In many
|
|||
In the transport bar of the editor window there are two (or, if you are on a very small screen, just one) clocks that display both the current position of the playhead, and additional information related to transport control and the timeline. These are called the "transport clocks"; the leftmost one is the primary transport clock and the rightmost one is the secondary transport clock. They look like this:
|
||||
</p>
|
||||
<p>
|
||||
<img src="/files/manual/a3/images/new_main_clocks.png" alt="an image of the transport clocks in ardour 3"></p>
|
||||
<img src="/files/manual/a3/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour 3"></p>
|
||||
<p>
|
||||
Editing the time in the transport clocks will reposition the playhead in the same way that various other editing operations will.
|
||||
</p>
|
||||
|
|
@ -36,7 +36,7 @@ Having two transport clocks lets you see the playhead position in two different
|
|||
The transport bar also contains a set of 5 clocks that show the current selection range and punch ranges. Clicking on the punch range clocks will locate to either the beginning or end of the punch range. Similarly, clicking on the range clocks will locate to either the beginning or end of the current selection. In this screen shot there is no current selection range, so the selection clocks show an "off" state.
|
||||
</p>
|
||||
<p>
|
||||
<img src="/files/selectionpunchclocks.png" alt="an image of the the selection and punch clocks in ardour 3"></p>
|
||||
<img src="/files/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour 3"></p>
|
||||
<p></p>
|
||||
<h2>Clock Modes</h2>
|
||||
<p>Every clock in Ardour has four different modes it can be set to, each of which displays time using different units. You can change the clock mode by right-clicking on the clock and selecting the desired mode from the menu. Some clocks are entirely independent of any other clock's mode; others are linked so that changing one changes all clocks in that group. The different modes are:</p>
|
||||
|
|
@ -64,7 +64,7 @@ Note that when set into this "Delta to Edit Point" mode, the transport clocks ca
|
|||
<p>
|
||||
New values for the clock can be typed from the keyboard after clicking on the relevant clock. Clicking on the clock will show a thin vertical cursor bar just to the right of the next character to be overwritten. Enter time in the same order as the current clock mode - if the clock is in Timecode mode, you need to enter hours, minutes, seconds, frames. So, to change to a time of 12:15:20:15 you would type <code> 1 2 1 5 2 0 1 5</code>. Each number you type will appear in a different color, from right to left, overwriting the existing value. Mid-edit, after typing <code>3 2 2 2</code> the clock might look like this:</p>
|
||||
<p>
|
||||
<img src="/files/clockedit.png" alt="an image of a clock being edited in ardour 3"></p>
|
||||
<img src="/files/clockedit.png" alt="An image of a clock being edited in Ardour 3"></p>
|
||||
<p>
|
||||
To finish the edit, press the enter/return or tab key. To exit an edit without changing the clock press the escape key. If you mis-type an entry so that the new value would be illegal (for example, resulting in more than 30 frames when Timecode is set to 30 frames per second), the clock will reset at the end of the edit, and move the cursor back to the start so that you may begin again.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The timecode is sent to jack-ports <code>ardour:MTC out</code>, <code>ardour:MID
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Note that - at the time of writing this - only the LTC generator supports latency compensation. This is due to the fact the ardour MIDI ports are not yet latency compensated.
|
||||
Note that - at the time of writing this - only the LTC generator supports latency compensation. This is due to the fact the Ardour MIDI ports are not yet latency compensated.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -99,11 +99,11 @@ LTC is send regardless of Ardour's transport-speed. It is accurately generated e
|
|||
<h2>Ardour Slave Configuration</h2>
|
||||
|
||||
<p>
|
||||
Switching the timecode-source can be done via the button just right of Ardour's main clock. By default it is set to <code>Internal</code> in which case ardour will ignore any external timecode. The button allows to toggle between Internal and the configured timecode source which is chosen in <code>Edit > Preferences > Transport</code>.
|
||||
Switching the timecode-source can be done via the button just right of Ardour's main clock. By default it is set to <code>Internal</code> in which case Ardour will ignore any external timecode. The button allows to toggle between Internal and the configured timecode source which is chosen in <code>Edit > Preferences > Transport</code>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
When ardour is chasing an external timecode source the following cases need to be distinguished:
|
||||
When Ardour is chasing an external timecode source the following cases need to be distinguished:
|
||||
</p>
|
||||
<ol>
|
||||
<li>the timecode source shares the clock</li>
|
||||
|
|
@ -114,7 +114,7 @@ When ardour is chasing an external timecode source the following cases need to b
|
|||
and
|
||||
</p>
|
||||
<ol>
|
||||
<li>the timecode source uses the same FPS setting as ardour</li>
|
||||
<li>the timecode source uses the same FPS setting as Ardour</li>
|
||||
<li>the timecode source runs at different frames-per-second</li>
|
||||
</ol>
|
||||
|
||||
|
|
@ -127,7 +127,7 @@ In both cases the first option is preferred: clock sync + same FPS setting.
|
|||
<h3>Frames-per-second</h3>
|
||||
|
||||
<p>
|
||||
If the frames-per-second don't match, ardour can either re-calculate (map) the frames or the configured FPS (<code>session > properties</code>) can be changed automatically while the slave is active. The behavior is configured with the checkbox in <code>Edit > Preferences > Transport</code> labeled <code>Match session video frame rate to external timecode</code>: When enabled the session video frame rate will be changed to match that of the selected external timecode source. When disabled the session video frame rate will not be changed to match that of the selected external timecode source. Instead the frame rate indication in the main clock will flash red and Ardour will convert between the external timecode standard and the session standard.
|
||||
If the frames-per-second don't match, Ardour can either re-calculate (map) the frames or the configured FPS (<code>session > properties</code>) can be changed automatically while the slave is active. The behavior is configured with the checkbox in <code>Edit > Preferences > Transport</code> labeled <code>Match session video frame rate to external timecode</code>: When enabled the session video frame rate will be changed to match that of the selected external timecode source. When disabled the session video frame rate will not be changed to match that of the selected external timecode source. Instead the frame rate indication in the main clock will flash red and Ardour will convert between the external timecode standard and the session standard.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -151,11 +151,11 @@ The checkbox <code>External timecode is sync locked</code> allows to select the
|
|||
</p>
|
||||
|
||||
<p>
|
||||
In other words: if enabled, ardour will only use perform initial synchronization and keep playing at speed 1.0 instead of vari-speed adjusting to compensate for drift.
|
||||
In other words: if enabled, Ardour will only use perform initial synchronization and keep playing at speed 1.0 instead of vari-speed adjusting to compensate for drift.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Note that vari-speed is unavailable when recording in ardour and all tracking happens at speed 1.0. So if you want to record in sync with external timecode it must be sample-locked or it will drift over time.
|
||||
Note that vari-speed is unavailable when recording in Ardour and all tracking happens at speed 1.0. So if you want to record in sync with external timecode it must be sample-locked or it will drift over time.
|
||||
</p>
|
||||
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ While Ardour is chasing LTC, the main transport clock will display the received
|
|||
</p>
|
||||
|
||||
<p>
|
||||
A global offset between incoming timecode and ardour's transport can be configured in <code>Session > Properties</code>.
|
||||
A global offset between incoming timecode and Ardour's transport can be configured in <code>Session > Properties</code>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -235,6 +235,6 @@ JACK-transport does not support vari-speed, nor offsets. Ardour does not chase t
|
|||
</p>
|
||||
|
||||
<p>
|
||||
JACK-transport also includes temp-based-time information ie. Bar:Beats:Ticks and beats-per-minute. However, only one JACK application can provide this information at a given time. The checkbox <code>JACK Time Master</code> in the <code>Session > Properties</code> dialog allows to configure ardour to act as translator from timecode to BBT information.
|
||||
JACK-transport also includes temp-based-time information ie. Bar:Beats:Ticks and beats-per-minute. However, only one JACK application can provide this information at a given time. The checkbox <code>JACK Time Master</code> in the <code>Session > Properties</code> dialog allows to configure Ardour to act as translator from timecode to BBT information.
|
||||
</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Ardour 3.2 (and later) facilities to:
|
|||
<ul>
|
||||
<li>Import a single video and optionally extract the soundtrack from it.
|
||||
</li>
|
||||
<li>Provide a Video-monitor window, or full-screen display, of the imported video in sync with any of the available ardour timecode sources.
|
||||
<li>Provide a Video-monitor window, or full-screen display, of the imported video in sync with any of the available Ardour timecode sources.
|
||||
</li>
|
||||
<li>Display a frame-by-frame (thumbnail) timeline of the video.
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -30,8 +30,8 @@ Ardour requires xjadeo ≥ version 0.6.4, harvid ≥ version 0.7.0 and ffmpeg
|
|||
</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>
|
||||
|
|
@ -72,7 +72,7 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc
|
|||
</li>
|
||||
</ul>
|
||||
<ul>
|
||||
<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>..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>
|
||||
</ul>
|
||||
<ul>
|
||||
|
|
@ -81,5 +81,5 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc
|
|||
</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>
|
||||
|
|
|
|||
|
|
@ -32,11 +32,11 @@ All in all it is a very wide and deep field. Suffice there are different uses fo
|
|||
<h2>Ardour specific</h2>
|
||||
|
||||
<p>
|
||||
Ardour supports a wide variety of video file-formats and video-codecs. More specifically, ardour itself actually does not support any video at all but delegates handling of video files to <a href="http://ffmpeg.org">ffmpeg</a> which supports over 350 different video-codecs and more than 250 file-formats.
|
||||
Ardour supports a wide variety of video file-formats and video-codecs. More specifically, Ardour itself actually does not support any video at all but delegates handling of video files to <a href="http://ffmpeg.org">ffmpeg</a> which supports over 350 different video-codecs and more than 250 file-formats.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
When importing a video into ardour, it will be <em>transcoded</em> (transcoding: change from one format and codec to another) to avi/mjpeg for internal use (this allows reliable seeking to frames at low CPU cost - the file-size will increase, but hard-disks are large and fast).
|
||||
When importing a video into Ardour, it will be <em>transcoded</em> (transcoding: change from one format and codec to another) to avi/mjpeg for internal use (this allows reliable seeking to frames at low CPU cost - the file-size will increase, but hard-disks are large and fast).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ The second step analyzes the video file in more detail and offers import options
|
|||
By default the video is imported using the original width/height.
|
||||
If it is a large video (e.g. full-HD) it makes sense to scale it down to decrease the CPU load and disk I/O which required to decode and play the file.
|
||||
A small, low-quality representation of the image is usually sufficient for editing sound-tracks.
|
||||
The default bitrate in kbit/sec is set to use 0.7 bits per pixel. (compare: the average DVD medium uses 5000kbit/sec; at PAL resolution this is about 0.5 bits per pixel - but the DVD is using the <em>mpeg2</em> - a denser compression algorithm than the <em>mjpeg</em> codec used by ardour.)
|
||||
The default bitrate in kbit/sec is set to use 0.7 bits per pixel. (compare: the average DVD medium uses 5000kbit/sec; at PAL resolution this is about 0.5 bits per pixel - but the DVD is using the <em>mpeg2</em> - a denser compression algorithm than the <em>mjpeg</em> codec used by Ardour.)
|
||||
</p>
|
||||
|
||||
<h2>Working with A/V</h2>
|
||||
|
|
@ -95,7 +95,7 @@ The soundtrack of the video is taken from an audio-export of Ardour's master bus
|
|||
</p>
|
||||
|
||||
<p>
|
||||
The video file can be chosen freely, For high quality exports, the original file (before it was imported in the timeline) should be used. This is also the default if the file can be found, if not ardour will suggest to use the imported proxy-video which is currently in use on the timeline. Any existing audio tracks on the video-file are stripped.
|
||||
The video file can be chosen freely, For high quality exports, the original file (before it was imported in the timeline) should be used. This is also the default if the file can be found, if not Ardour will suggest to use the imported proxy-video which is currently in use on the timeline. Any existing audio tracks on the video-file are stripped.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -116,5 +116,5 @@ Note: not all combinations of format+codec+settings produce files which are acco
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Ardour video export is not recommended for mastering!\nWhile 'ffmpeg' (which is used by ardour) can produce high-quality files, this export lacks the possibility to tweak many settings. We recommend to use 'winff', 'devede' or 'dvdauthor' to mux & master. Nevertheless this video-export comes in handy to do quick snapshots, intermediates, dailies or online videos.
|
||||
Ardour video export is not recommended for mastering!\nWhile 'ffmpeg' (which is used by Ardour) can produce high-quality files, this export lacks the possibility to tweak many settings. We recommend to use 'winff', 'devede' or 'dvdauthor' to mux & master. Nevertheless this video-export comes in handy to do quick snapshots, intermediates, dailies or online videos.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user