- This tab is used to change how Ardour names recorded regions.
- If Prefix track number is selected a unique number will appear on each track
- in the Editor window and will prefix the region name. If the track number
- is 2 and the region would have been Gtr-1.1 with track number prefix turned on the region
- will be named 2_Gtr-1.1 instead. See XX for base of the region name.
-
-
-
- If Prefix take name is selected and the Take name has Take1 the region
- will have the name Take1_Gtr-1.1 instead. If both boxes are checked the name will be
- Take1_2_Gtr-1.1 instead.
-
-
-
- When Prefix take name is enabled, the first time a track is recorded it will
- have the specified take name. When recording is stopped, any trailing number on the
- end of the take name will incremented by 1. If the track name specified doesn't have
- a number on the end, the number 1 will be suffixed.
-
- These options add file locations that will be searched to find the audio and
- midi files used by the session. This is useful when the files have been
- imported into the session but not copied into the session.
-
-
-
- To add a location, navigate to the directory where the files are stored.
- Drill down into the directory and then click open. The directory will
- show up in the dialog. The remove button next to the added directory can be used
- to remove it from the search path.
-
- Change how sound is stored on disk. These options do not change how sound is handled
- internally.
-
-
-
-
- Sample format defaults to 32-bit floating point, the same as
- the internal representation. 24 and 16-bit integer representation are
- also available.
-
The Monitor section is an optional feature that provides Control Room/Monitor Speaker outputs.
It can be activated for the current session in the
-
+ Session > Properties window by enabling the
Use monitor section in this session option in the
Monitoring tab. By default the Monitor Section is fed with audio from the Master Bus,
diff --git a/include/monitoring-tab.html b/include/monitoring-tab.html
deleted file mode 100644
index 31951d14..00000000
--- a/include/monitoring-tab.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
- Provides options affecting monitoring.
-
-
-
-
-
- The Track Input Monitoring automatically follows transport state
- affects how input monitoring is handling. See
- Monitor Setup in Ardour.
-
-
-
- The 'Use monitor section' displays an extra section in the Mixer
- window that is modelled on the similarly named section on large analog consoles.
- More information can be found on the Monitor Section page.
-
Templates can be huge time savers when working on similar projects, or on
usual projects, as they allow to preset and tweak a lot of the session properties, (like the
+ href="@@session-properties">session properties, (like the
availability of a monitoring section,
connection to a Master Bus, etc.), and handle the creation of tracks of any kind.
diff --git a/include/preferences.html b/include/preferences.html
index 7e1f13c2..83aa681c 100644
--- a/include/preferences.html
+++ b/include/preferences.html
@@ -1,3 +1,10 @@
+
+
Global preferences control general workflow and system
configuration, and should apply to all sessions. They are located in
- This tab has several things that don't fit on the other tabs.
-
-
-
-
-
-
- MIDI Options
-
-
- If MIDI region copies are independent is selected, when a
- MIDI region is copied or duplicated, the new region is not linked to
- the region it was copied from. If it is not selected, the copied regions
- are linked and any editing of one of the linked regions changes all
- of the linked regions.
-
-
- The Editor can be configured to handle overlapping MIDI notes
- several ways.
-
-
never allow them
-
don't do anything in particular
-
replace any overlapped existing notes
-
shorten the overlapped existing note
-
shorten the overlapped new note
-
replace both overlapping notes with a single note
-
-
-
-
-
- Glue to bars and beats
-
-
New markers can be glued to bars and beats
-
New regions can be glued to bars and beats
-
-
-
- Settings from the session properties dialogs can be saved to the
- default session template.
-
- Session properties control aspects of the workflow or
- configuration that pertain to the current session only; these settings are
- initially set from the template used to create the session. They can be found
- in Session > Properties, and are stored in the
- session file.
-
+ Session properties control aspects of the workflow or
+ configuration that pertain to the current session only; these settings are
+ initially set from the template used to create the session. They can be found
+ in Session > Properties, and are stored in the
+ session file.
+
+ Timecode frames-per-second: defines how many frames of
+ timecode are in one second. This can differ from the actual frame rate
+ depending on the standard used.
+
+
+ Pull-up / pull-down: sets the speed correction to match one
+ actual second, e.g. a 4.1667 pull-up matches a 24fps cinema movie to a
+ 25 fps PAL TV broadcast format.
+
+
+
+
+ Ext Timecode Offsets
+
+
+ Slave Timecode offset: when an external timecode source is used,
+ adds or substracts the specified offset to the received timecode (MTC or LTC).
+
+
+ Timecode Generator offset: adds the specified offset to
+ the timecode generated by Ardour (so far only LTC) before sending it to
+ the external synchronized system.
+
+
+
+
+ JACK Transport/Time Settings
+
+
+ Ardour is JACK Time Master (provides Bar|Beat|Tick and other information
+ to JACK) Aside from synchronizing any JACK slave, Ardour can also
+ provide musical time information (Bar/Beat/Tick) for the current absolute
+ position for all the JACK-aware clients (N.B. the first jack client that
+ asks for this wins).
+
+
+
+
+
+
Sync
+
+
+
+ A/V Synchronization
+
+
+ Use Video File's FPS Instead of Timecode Value for Timeline and Video
+ Monitor when checked, uses the timecode FPS value of the standard
+ used by the video file instead of forcing the FPS set in the
+ Timecode tab.
+
+
+ Apply Pull-Up/Down to Video Timeline and Video Monitor (Unless using
+ JACK-sync) allows to apply the pull-up/down as set in the
+ Timecode tab to the video
+ timeline as displayed in the editor and to the Video Monitor, resulting
+ in a shorter/longer video in the editor and a speed-up/down in the Video
+ Monitor.
+
+
+
+
+
+
Fades
+
+
+
+ Audio Fades
+
+
+ Destructive crossfade length: sets the duration of the crossfade
+ Ardour automatically creates when an operation on a region is destructive,
+ such as when recording in a track in tape mode.
+ This does not change the length of the crossfade Ardour automatically creates
+ at regions boundaries on non-destructive operations (recording, slicing etc...)
+ which is set to 1 ms.
+
+
+ Declick when transport starts and stops creates an artificial
+ fade in/out when starting or stopping playback, to avoid the 'click' sound
+ resulting in starting it at a non zero value.
+
+
+ Declick when monitor state changes also creates an artificial
+ fade in/out to avoid clicks when a parameter in the monitor changes.
+
+
+ Region fades active when checked, Ardour applies the region
+ crossfades to each
+ region's start and end. When unchecked, no fades are applied, and clicks
+ may be heard at regions boundaries.
+
+
+ Region fades visible when checked, the region fades are visible
+ in the the Editor. Unchecking may increase readability for sessions made
+ of a lot of tiny regions.
+
+
+
+
+
+
Media
+
+
+ Change how sound is stored on disk. These options do not change how sound is handled
+ internally.
+
+
+
+
+ Audio File Format
+
+
+ Sample format: defaults to 32-bit floating point, the same as
+ the internal representation. 24 and 16-bit integer representation are
+ also available, for more lightweight sessions at the cost of a reduced
+ audio definition.
+
+
+ File type: defines what format is used to store the audio
+ files. The default is WAVE, and can be changed to Broadcast Wave to
+ store metadata and timecodes, CAF to overcome WAVE's limitation to 4Gb in size, RF64
+ to add more channels, etc. The chosen format is usually very
+ workflow-specific.
+
+
+
+
+
+
Locations
+
+
+ These options add file locations that will be searched to find the audio and
+ midi files used by the session. This is useful when the files have been
+ imported into the session but not copied into the session.
+
+
+
+
+ File Locations
+
+
+ Search for audio files in: allows to add a location to look
+ for audio files. Adding a location is done by navigating to the
+ directory where the files are stored, selecting it and clicking Open. The directory will show up in the dialog. The
+ Remove button next to the added directory can
+ be used to remove it from the search path. Multiple paths can be added
+ this way.
+
+
+ Search for MIDI files in: is exactly the same, but for MIDI files.
+
+
+
+
+
+
Filenames
+
+
+ This tab is used to change how Ardour names recorded regions.
+
+
+
+
+ File Naming
+
+
+ Prefix Track number when checked, a unique number will
+ appear on each track in the Editor window and will prefix the region
+ name. If the track number is 2 and the region would have
+ been named Gtr-1.1, with track number prefix turned on the
+ region will be named 2_Gtr-1.1 instead. See Region Naming.
+
+
+ Prefix Take Name when enabled, the first time a track is
+ recorded it will have the specified take name. When recording is
+ stopped, any trailing number on the end of the take name will be
+ incremented by 1. If the specified track name doesn't have a number on
+ the end, the number 1 will be suffixed.
+
+
+ Take name specifies what name is prefixed if Prefix Take Name is checked.
+
+
+
+
+
+
+
Monitoring
+
+
+ Provides options affecting monitoring.
+
+
+
+
+ Monitoring
+
+
+ Track Input Monitoring automatically follows transport state
+ ("auto-input") affects how input monitoring is handling. See Monitor Setup in Ardour
+
+
+ Use monitor section in this session when enabled, displays
+ an extra section in the Mixer window that is modelled on the similarly
+ named section on large analog consoles. More information can be found
+ on the Monitor Section page.
+
+
+
+
+
+
+
Meterbridge
+
+
+ This tab changes what controls are displayed in the Meterbridge that is
+ available in the Window > Meterbridge menu.
+
+
+
+
+ Route Display
+
+
+ Show Midi Tracks displays/hides MIDI tracks (even when no
+ synth, hence no audio output exists)
+
+ Include Master Bus displays/hides the Master Bus
+
+
+
+
+ Button Area
+
+
+ Rec-enable Button displays/hides the record arm button (for audio
+ and MIDI tracks only)
+
+
+ Mute Button displays/hides the mute button (for all
+ tracks/busses types)
+
+
+ Solo Button same for solo
+
+
+ Monitor Buttons displays/hides the two (input and playback)monitoring buttons, selecting what is played at
+ record and playback time.
+
+
+
+
+ Name Labels
+
+
+ Track Name adds the tracks' names bellow the buttons.
+
+
+
+
+
+
Misc
+
+
+ This tab has several things that don't fit on the other tabs.
+
+
+
+
+ MIDI Options
+
+
+ MIDI region copies are independent if selected, when a MIDI
+ region is copied or duplicated, the new region is not linked to the
+ region it was copied from. If it is not selected, the copied regions
+ are linked and any editing done on one of the linked regions changes
+ all of the linked regions.
+
+
+ Policy for handling overlapping notes on the same MIDI channel:
+ Selects how Ardour reacts to possibly conflicting MIDI notes:
+
+
never allow them
+
don't do anything in particular
+
replace any overlapped existing notes
+
shorten the overlapped existing note
+
shorten the overlapping new note
+
replace both overlapping notes with a single note
+
+
+
+
+
+ Glue to Bars and Beats
+
+
+ Glue new markers to bars and beats if checked, a newly
+ created marker will always be placed at the nearest musical time
+ instead of right where the mouse pointer is.
+
+
+ Glue new regions to bars and beats same as above, for regions.
+
+
+
+
+ Metronome
+
+
+ Always count-in when recording when checked, waits for two
+ bars before the actual recording begins. The Metronome will tick (even if
+ disabled) during the count-in. Same as recording with Transport > Record w/Count-In.
+
+
+
+
+ Defaults
+
+
+ Use these settings as defaults clicking this buttons makes all
+ the present Session Properties default, by recording them in the
+ default session template.
+
- This tab is used to modify the timecode settings when working with video to
- use the imported video's timecode settings instead of the session defaults.
-
- This tab is used to change how Ardour interprets and manipulates timecode.
-
-
-
-
- Timecode Settings lets you set the number of frames per second
- and pull up/down to match the timecode used other synchronized systems.
-
-
- External Timecode Offsets allows Ardour to a fixed offset from other
- synchronized systems. Slave Timecode offset adds the
- specified offset to the received timecode (MTC or LTC).
- Timecode Generator offset adds the specified offset to
- the timecode generated by Ardour (so far only LTC).
-
-
- Jack Transport / Time Settings determines whether Ardour controls
- Bar|Beat|Tick and other information for Jack.
-
-
-
-
diff --git a/include/workflow-amp-operations.html b/include/workflow-amp-operations.html
index facd0f05..49a695c1 100644
--- a/include/workflow-amp-operations.html
+++ b/include/workflow-amp-operations.html
@@ -70,7 +70,7 @@
Window > Video Monitor menu which is binded to
V by default.
Adjust Session Framerate to Match Video Framerate
- which can also be set later with the Session Properties.
+ which can also be set later with the Session Properties.
Having the session and video framerate at the same value allows their sync not to
drift off.