From f04db3fe5d2b7eba806d154e215466a2884bdb0c Mon Sep 17 00:00:00 2001
From: Shamus Hammons Ch. ' + str(levelNums[level]) + ': ' + header['title'] + ' WTH is “Note Level Editing”? (See table below, “So, to summarize…”.)
- For light MIDI editing, the Internal Edit Mode can be used. This mode allows
- to select notes, copy, move or delete them and alter their properties. Adding
- new notes in this mode is done by Left dragging.
- For more extensive MIDI editing, the Draw Mode.
- allows to Left click or drag to add a new note, without
- having to hold down . However, Draw Mode doesn't offer
- region-level editing nor rubberband selection.
+
+ For light MIDI editing, Internal Edit Mode can be used. This mode allows
+ selecting, copying, moving and deleting notes, and also allows altering
+ notes’ properties. To add notes using the mouse, Left-drag. For more extensive MIDI editing, Draw Mode may be preferred. New notes can be added with
+ a click or drag, without having to hold down .
+ However, Draw Mode doesn't allow region-level
+ editing.
Not sure if the following paragraph is true.
- In both modes, a mouse click creates a note at the pointer location
- (or the nearest grid point if grid is enabled), and its duration is one Grid unit, even if the grid is disabled. A mouse
- drag creates the note like a click does, but allows to set the
- duration of the note until the mouse button is released.
+ In both modes, a mouse click creates a note at the pointer location
+ (or the nearest grid point if grid is enabled), and its duration is one Grid unit, even if the grid is disabled. A mouse
+ drag creates the note like a click does, but allows continuously
+ setting the duration of the note until the mouse button is released.
So, to summarize:
- There is also a step entry editor allowing to enter
- notes from a virtual keyboard and lots more besides.
+
+
+ There is also a step entry editor that allows the
+ entry of notes from a virtual keyboard.
\n'
lvl = lvl + 1
+
while lvl > level:
content = content + '
\n'
lvl = lvl - 1
@@ -398,11 +405,12 @@ def CreateLinkSidebar(fs, pos, childList):
# Build the list recursively from the top level nodes
content = BuildList(FindTopLevelNodes(fs), fs, pos, childList)
# Shove the TOC link and one file link at the top...
- active = ' class=active' if pos<0 else ''
- content = content.replace('','
', '
Adding new notes
-
-
-
- Selecting, moving, copying, trimming, deleting regions
- Note Level Editing disabled, using Grab,
- Range or other mouse modes
- Selecting, moving, copying trimming, deleting notes
- Note Level Editing enabled, and using Internal
- Edit mode
+ Adding new notes
- enabling "Note Level Editing" and then either
-
-
-
+
+ Selecting, moving, copying, trimming, deleting regions
+ Note Level Editing disabled, using object, range or other mouse modes
+
+
+ Selecting, moving, copying trimming, deleting notes
+ Note Level Editing enabled, and using mouse object mode
+
+
Adding new notes
+ Enabling "Note Level Editing" and then either
+
+
+
+
Any of these actions will open the Add Track/Bus/VCA dialog. @@ -21,74 +21,90 @@
The list of available track templates (both factory and user-created ones) - in the left panel allows to choose the track(s) type - (e.g. Audio, MIDI, bus, VCA etc.). Some templates can do even more, like the + in the left panel allows for choosing the track's type + (e.g. Audio, MIDI, bus, VCA, etc.). Some templates can do even more, like the factory-provided Live Band that automatically creates - a number of usual tracks for a common band setup. See New Session for more information about templates.
- The common templates have parameters to tweak: + Any template can be fine-tuned using the controls in the dialog:
Add | -Selects the number of tracks, busses or VCAs to create. |
---|---|
Name | -Defines the name of the new track(s). If multiple tracks are created, or if -a track with the same name already exists, a space and number will be happened -at the end (e.g.: Audio 1, Audio 2…). |
Configuration | -This menu allows to choose from a number of route templates, which determine -the number of input ports and optionally contain plugins and other mixer strip -configuration. The most common choices here are mono and -stereo. |
Instrument | +|
Add | +Selects the number of tracks, busses or VCAs to create. | +
Name | +Defines the name of the new track. If multiple tracks are to be created, + or if a track with the same name already exists, a space and number will be + appended to the end (e.g.: Audio 1, Audio 2…). | +
Configuration | +This menu allows choosing from a number of routing templates, which + determines the number of input ports and optionally contains plugins and + other mixer strip configurations. The most common choices here are + mono and stereo. | +
Instrument | This option is only available for MIDI tracks and busses and allows the -selection of a default instrument from the list of available plugins. |
Group | -Tracks and busses can be assigned groups so that a selected range of - operations are applied to all members of a group at the same time (selecting - record enable, or editing, for example). This option assigns the new track/bus - to an existing group, or create a new group. |
Pin Mode | + selection of a default instrument from the list of available plugins. +|
Group | +Tracks and busses can be assigned to groups so that a selected range of + operations are applied to all members of the group at the same time + (selecting record enable, or editing, for example). This option assigns the + new track/bus to an existing group, or creates a new group. | +
Pin Mode | Defines how the number of output responds to adding a plugin with a - different number of outputs than the track itself. In Strict I/O mode, - plugins cannot alter the track's channel count, while in Flexible I/O - mode, it will automatically adapt - to the I/O of its plugins. See Signal flow - to learn more about those options. |
Record mode | + different number of outputs than the track itself. In Strict I/O + mode, plugins cannot alter the track's channel count, while in Flexible + I/O mode, it will automatically adapt to the I/O of its plugins. See Signal flow for details. +|
Record mode | This option is only available for audio tracks and affects how it behaves when recording. See Track Modes for - details. |
Position | + details. +|
Position | Defines where in the track list is the track created. The default is -Last, i.e. after all the tracks and busses, and can also be -First, Before Selection (to place it just above the selected -track) or After selection. |
Multiple tracks of different types can be created by using the Add selected items (and leave dialog open) button, which, used - in conjunction with the Add field, allows for a very efficient - and fast way to create a base track setup. + class="menu">Add selected items (and leave dialog open) button, which, + when used in conjunction with the Add field, allows + for a very fast and efficient way to create an initial track setup.
New tracks appear in both the editor and mixer windows. The editor window shows the timeline, with any recorded data, and the mixer shows just the - processing elements of the track (its plugins, fader and so on). + processor elements of the track (its plugins, fader, etc).
- Removing tracks and busses, is done by selecting them, Removing tracks and busses is done by selecting them, right-clicking and choosing Remove - from the menu. A warning dialog will pop up, as track removal cannot be undone; - this option should be used with care! + from the menu. A warning dialog will ask for confirmation as track removal + cannot be undone; this option should be used with care!
diff --git a/include/change-note-properties.html b/include/change-note-properties.html index 6f23d36..f3743d7 100644 --- a/include/change-note-properties.html +++ b/include/change-note-properties.html @@ -1,23 +1,20 @@- All the details about a selected note can be viewed by context-clicking on - it. The dialog that pops up will also allow to modify all the properties - of the selected note(s). Individual properties can also be modified more efficiently - using the techniques described below. + All details about selected notes can be viewed by context-clicking on them. The dialog that pops up also allows for the modification of all properties of the selected notes. Individual properties can also be modified more efficiently using the techniques described below:
Moving notes | - Right arrow and Left arrow move the selected note(s) early and later in time. + ← and → move selected notes earlier and later in time. |
---|---|
Changing pitch values |
- ↑ increases the pitch of the selected notes. - ↓ reduces the pitch of the selected notes. - If any of the selected notes are already at the maximum or minimum value, - no changes will be made to any of the notes, to preserve relative pitches. - This can be overrode with . The default shift + ↑ raises the pitch of the selected notes. + ↓ lowers the pitch of the selected notes. + If any of the selected notes are already at their minimum or maximum values, + no changes will be made to any them, to preserve their relative pitches. + This can be overridden with . The default shift distance is one semitone. alters this to one octave. |
Changing channel | - Pressing c brings up a dialog that allows to see and alter the + Pressing c brings up a dialog that allows viewing and/or altering the MIDI channel of the selected notes. If the selected notes use different channels, they will all be forced to the newly selected channel. |
Changing start/end/duration |
- , (comma) will alter the start time of the note. + , (comma) will alter the start time of the note. . (period) will alter the end time of the note. Both keys will by default make the note longer (either by moving the start earlier or the end later). For the opposite effect, ,/q will quantize the selected notes using the current quantize settings. If the quantize settings have not been set for this session yet, the quantize dialog will appear. q will display the - quantize dialog to allow to reset the quantize settings, and then - quantizes the selected notes. The default quantize settings are: quantize + quantize dialog to allow editing the current quantize settings, and then + will quantize the selected notes. The default quantize settings are: quantize note starts to the current grid setting, no swing, no threshold, full strength. |
Step Entry, Quantize etc. | +|
Step Entry, Quantize, etc. | Refer to the Step Entry, Quantizing MIDI, etc. specific pages. |
- Although recording MIDI is a common way to create new MIDI regions, it is - often desirable to do so as part of editing/arranging. -
-- To create a new MIDI region with the mouse, simply enter draw mode (press - "d" or click on the pencil tool) and then Left-click in a MIDI track. This creates a region - that is one bar long. Alternatively, use the left button to - drag-create a new region of the desired length. + Although recording MIDI on an existing track is a common way to create new MIDI regions, it is often desirable create new MIDI regions as part of the editing and/or arranging process.
+- Once the region exists, to trim it to a different length, switch - back to grabber/object/select mode (press "g" or click on the - grabber tool). Then trim to your desired length. + A new MIDI region can be created with the mouse by entering Draw Mode (entered by pressing the d key or clicking on the Draw tool) and then left-clicking anywhere in an existing MIDI track; this will create a region that is one bar long. If longer regions are desired, they can be created by left-clicking anywhere in an existing MIDI track and dragging the mouse until the region is the desired length.
-- Once the region is ready, add some notes - to it. + +
+ Once created, all the typical methods of editing audio regions will work the same as they do for MIDI regions. See Editing Regions and Selections for more details.
diff --git a/include/create-midi-tracks.html b/include/create-midi-tracks.html index 4e51b50..b2693ec 100644 --- a/include/create-midi-tracks.html +++ b/include/create-midi-tracks.html @@ -1,17 +1,13 @@- To create MIDI track(s), choose Session > - Add Track/Bus from the main menu. In the Add - Track/Bus dialog, left pane, choose MIDI Tracks. + A MIDI track is created much like any other track (see Adding Tracks, Busses and VCAs). However, there are a few things that are unique to creating MIDI tracks.
- A track template can be used, by selecting it in the Configuration drop - down menu. + When adding a MIDI track using the Add Track/Bus/VCA dialog, the MIDI Tracks item should be highlighted in the Template/Type list on the left. This will enable the Instrument combobox while disabling the Configuration and Record Mode comboboxes.
- When you create a MIDI track you can select an instrument. The instrument in - this context is any plugin that will generate audio in response to receiving MIDI. + The Instrument combobox allows the selection of a plugin for the track to be created that will generate audio in response to MIDI data; if the track is intended to drive an external device then -none- should be selected instead.
diff --git a/include/edit-midi.html b/include/edit-midi.html index cccfb95..5dc4592 100644 --- a/include/edit-midi.html +++ b/include/edit-midi.html @@ -1,28 +1,24 @@- Ardour's handling of MIDI editing differs from most other DAWs - and MIDI sequencers. + Ardour's handling of MIDI and how it allows the editing of MIDI data differs + in key ways from most other DAWs and MIDI sequencers. Also, unlike its + handling of audio data, the editing of MIDI data in Ardour is necessarily + destructive by nature.
-Editing operations in a Digital Audio Workstation like Ardour can be broken down according to how many points on the timeline are required to carry the operation out. Splitting a region for example, requires just one position on - the timeline (the one where the split will happen). Cutting out a time range - requires two positions, one for the start of the cut and one for the end. + the timeline—the one where the split will happen. Cutting out a time + range requires two positions, one for the start of the cut and one for the end.
- In Ardour the edit point is the location where most single-point -editing operations take place. It can be set to either of the following: + In Ardour the Edit Point is the location where most single-point + editing operations take place. It can be set to any of the following:
- The default edit point is the location of the pointer. + The default edit point is the location of the mouse pointer.
diff --git a/include/gain-envelopes.html b/include/gain-envelopes.html index 5eca027..7d38953 100644 --- a/include/gain-envelopes.html +++ b/include/gain-envelopes.html @@ -41,5 +41,5 @@ dragged to the desired location. Hovering over a control point will show its current level in dB. Left clicking a control point and pressing Delete, or Right - clicking a point deletes it. + clicking a control point deletes it.
diff --git a/include/midi-automation.html b/include/midi-automation.html new file mode 100644 index 0000000..fe0ea24 --- /dev/null +++ b/include/midi-automation.html @@ -0,0 +1,7 @@ + +ADD CONTENT PLEASE
+ ++ MIDI automation works in a similar way to regular audio automation, but has a few key differences. +
+ diff --git a/include/midi-list-editor.html b/include/midi-list-editor.html index d6369b0..dde49eb 100644 --- a/include/midi-list-editor.html +++ b/include/midi-list-editor.html @@ -1,5 +1,5 @@ -The List Editor is a way to look at the MIDI data of a region, not graphically as they are displayed in the Editor, but in a tabular form. - This way of seeing the MIDI data allows for a quicker "debugging" of a MIDI region, - and for a fast non-graphical (i.e. no mouse involved) editing. This - list has a vertical flow, i.e. the first events (in time) are on the top - of the window, and the latest are at its bottom. + This way of seeing the MIDI data allows for quicker "debugging" of a MIDI + region, and for fast non-graphical (i.e. no mouse involved) + editing. The list has a vertical flow, i.e. the first events (in time) are + at the top of the window, and the last are at the bottom.
+- It is accessed by selecting the Region > MIDI > List Editor… - menu while having one MIDI region selected, or by Right - clicking the MIDI region and choosing Name_Of_The_Region - > MIDI > List Editor… + It is accessed by selecting the Region > MIDI > List + Editor… menu while having one MIDI region selected, or by Right clicking the MIDI region and choosing Name_Of_The_Region > MIDI > List + Editor….
+The window displays the following MIDI data:
+Start | the timestamp of the start of the note |
---|---|
Channel | the MIDI channel of the event |
Num | The MIDI number of the note |
Name | The MIDI name of the note, made of its English name and octave (e.g. "C4") |
Vel | the velocity of the note (i.e. its intensity, between 0 and 127) |
Vel | the velocity of the note, i.e. its volume, between 0 (silent) and 127 (full) |
Length | duration of the note, either expressed as a number (in ticks, related to the tempo) or as a text (fraction of a beat, also related to the tempo) |
- At the top of the window is a Sound Selected MIDI Notes, - which is a toggle button allowing to listen to a note as it is selected. + At the top of the window is a Sound Selected MIDI + Notes button, which toggles playing a note as it is selected.
- Each value can be manually modified, by Left clicking it. - The Name field is related to the Number one, and cannot be edited. To change a - note, its number must be changed, which will be reflected in the Name field. + Each value can be manually modified, by left + clicking it. However, the Name field is derived from the + Number field, and cannot be edited. To change a note, its number + must be changed, which will be reflected in the Name field.
diff --git a/include/midi-overview.html b/include/midi-overview.html new file mode 100644 index 0000000..47358e8 --- /dev/null +++ b/include/midi-overview.html @@ -0,0 +1,72 @@ + ++ MIDI (or Musical Instrument Digital Interface) is a method of representing + musical concepts in a form suitable for use in computers. MIDI defines 16 + different channels, along which messages are passed to instruments + or synthesizers that understand the MIDI protocol; notes are played by + sending appropriately crafted NoteOn messages that are followed + by NoteOff messages. MIDI channels can be manipulated with + special controller messages to alter the pitch of instruments, or + their volume or timbre, and they can also tell the instrument or synthesizer + what sound to play using Program Change and Bank Select + messages. +
+ ++ Typically Program Change and Bank Select messages are collectively referred to by the singular term Patch Change. +
+ +ADD CONTENT PLEASE
+ diff --git a/include/midi-scene-automation.html b/include/midi-scene-automation.html index 7750977..1b56288 100644 --- a/include/midi-scene-automation.html +++ b/include/midi-scene-automation.html @@ -1,4 +1,6 @@ +ADD IMAGES PLEASE
+Ardour is capable of being used to both record and deliver MIDI "scene" automation. These are MIDI messages typically used to switch presets or @@ -7,12 +9,14 @@ presets between songs or to change lighting conditions based on a specific position on the timeline.
+Each change from one scene to another is represented by a marker in the "Marker" bar.
+- Technically, scene changes are delivered as a combination of bank and + Typically, scene changes are delivered as a combination of bank and program change MIDI messages. MIDI allows for 16384 banks, each with 128 programs.
@@ -24,16 +28,19 @@ be done by connecting this port to whatever source(s) of MIDI scene (bank/program change) messages should be recorded. +Whenever the global record enable button is engaged and Ardour's transport is rolling, a new marker will be created for each scene change message received via the "Scene In" port.
+If two different scene changes are received within a certain time period, only the later one will be recorded as a new marker. The default threshold for this is 1 millisecond.
+If a scene change message is received while the playhead is close to an existing marker with an associated scene change, the recording @@ -55,6 +62,7 @@ changes can be done by connecting this port to whatever target(s) of MIDI scene (bank/program change) messages should be sent to.
+When the global record enable button is not enabled, the relevant message(s) will be sent via the "Scene Out" port as the playhead rolls past @@ -72,3 +80,4 @@
This feature is not currently implemented.
+ diff --git a/include/midi-tracer.html b/include/midi-tracer.html index 361071d..7bde96c 100644 --- a/include/midi-tracer.html +++ b/include/midi-tracer.html @@ -1,53 +1,95 @@ -- The MIDI Tracer is similar to the MIDI - List Editor, in the way that it displays MIDI information as a tabular text - view, and has a vertical flow, i.e. the events follow a top to bottom time - order. + The MIDI Tracer window, which is accessed by selecting Window > MIDI Tracer from the main menu, is similar to + the MIDI List Editor in that it displays + MIDI information as tabular text, and has a vertical flow (i.e. the + events follow a top to bottom time-oriented order).
+- Its use is different though, as it is not bound to a specific region or track: - the MIDI that is monitored is any global input or output Ardour presents to the - system. It is hence a very useful option to monitor a MIDI port, be it an external - controller/device or the in/output of any track. + Its use is different however, as it is not bound to a specific + region or track; the MIDI shown in the MIDI Tracer window is any global input + or output Ardour presents to the system. As such, it is a very useful way to + monitor MIDI traffic, whether it is an external controller or device or the + input or output of any track.
-- It is accessed by selecting the Window > MIDI Tracer - menu. + +
+ The MIDI Tracer can list all types of MIDI and "audio" events, and scene automation and timecode events as well.
+- The window is made of: + The window consists of:
+Port | a list of all the MIDI ports Ardour presents to the system. They - are both internal and external and are the same ports Ardour presents to JACK, if - enabled. |
---|---|
the events list | where all the events for this port are listed, see below |
Line history | how many lines should be kept in the events list |
Delta times | if checked, shows the times as the duration since the last event, instead of the absolute time |
Decimal | if checked, shows the MIDI data as decimal values instead of the original hexadecimal values |
Enabled | if checked, the events are displayed in the events list, otherwise stops the logging |
Auto-Scroll | if checked, the events list scrolls as new events are logged, allowing to keep the newest events on screen |
Port | +A list of all the MIDI ports Ardour presents to the system. They are both + internal and external and are the same ports Ardour presents to JACK, if + enabled | +
The events list | +Where all the events for this port are listed, see below | +
Line history | +How many lines should be kept in the events list; once this limit is + reached, older events will be removed from the list | +
Delta times | +If checked, shows the times as the duration since the last event, instead + of absolute times | +
Decimal | +If checked, shows the MIDI data as decimal values instead of + hexadecimal | +
Enabled | +If checked, events are displayed in the events list as they occur, + otherwise stops the logging | +
Auto-Scroll | +If checked, the events list scrolls as new events are logged, keeping the + newest events on screen | +
The events list displays the events as columns:
+time of the event | either absolute or relative, based on the Delta times checkbox |
---|---|
MIDI status (event type) | what midi events happened (e.g. Note On, Note Off, Pitch Bend, …) |
MIDI channel | in which MIDI channel did the event happen |
MIDI data bytes (event parameters) | parameters of the event, e.g. for a Note On: what note was it, and which was the note's velocity |
Time of the event | +Either absolute or relative, based on the Delta + times checkbox | +
MIDI status (event type) | +What MIDI events happened (e.g. Note On, Note Off, Pitch Bend, etc.) | +
MIDI channel | +The MIDI channel the event happened in | +
MIDI data bytes (event parameters) | +Parameters of the event, e.g. for a Note On: what the note was, and its velocity | +
- Note: The MIDI Tracer can lists all kind of MIDI events, "audio" ones, but also scene automation or timecodes ones. -
- diff --git a/include/midi-track-controls.html b/include/midi-track-controls.html index 6a4b596..72ee046 100644 --- a/include/midi-track-controls.html +++ b/include/midi-track-controls.html @@ -1,47 +1,53 @@ -A typical MIDI track header looks like this:
+Item #3 below does not hold in all cases; check to make sure the rest of the content is sane as well
+- To show the full set of MIDI track controls, the track height - must be increased beyond the default. MIDI tracks show only a few of the control elements - when there is insufficient vertical space. -
-- A MIDI track has the same basic controls as an audio track, - with the addition of three extra elements: + A MIDI track has the same basic controls as an audio track, with the following + differences:
+- Also, right clicking the ● - (record) button shows the Step Entry dialog instead of - controlling the rec-safe. +
+ To show the full set of MIDI track controls, the track height must be increased beyond the default + height. MIDI tracks will show only a few of the control elements when there + is insufficient vertical space. Further, the External MIDI Device and + External Device Mode comboboxes will not appear if there is + a synth plugin on the track that comes with an associated MIDNAM.
- The Scroomer performs a couple of functions: + The Scroomer performs the following functions:
+- A MIDI track's data may span any number of the 16 available MIDI channels, and sometimes it is - useful to view only a subset of those channels; different instruments may, - for example, be put on different channels. In the context menu (right click), - the Channel Selector allows to control the MIDI channel(s) - that will be visible in the editor. + A MIDI track's data may utilize any number of the 16 available MIDI channels, and it is useful to be able to filter out a subset of those or force the input or output to utilize only certain channels. The Channel Selector dialog allows for filtering or modification of both the input and output of any given MIDI track.
- This window also gives control over which channel(s) will be recorded, and which will be played back, choosing between: + The Channel Selector dialog is activated by right-clicking on a MIDI track's header and selecting Channel Selector... from the menu that appears. Filtering or modification of Inbound MIDI events for the given MIDI track is done by selecting among:
+ Selecting Record all channels does no filtering of inbound MIDI events. +
+ ++ If simple filtering of incoming MIDI events is desired, Record only selected channels should be selected. A 1-by-16 grid of squares with numbers in them will become sensitive to mouse clicks, and the desired channels to be allowed through the filter can then be selected by clicking on them. Channels that are allowed to pass through will be highlighted in green. +
+ ++ Force all channels to 1 channel will rewrite the channel number of all incoming events of the selected MIDI track to whichever channel is highlighted in the 1-by-16 grid of squares. When this option is chosen, one and only one channel can be selected. +
+ ++ Filtering or modification of outbound MIDI events is done by selecting among: +
+ ++ Selecting Playback all channels does no filtering of outbound MIDI events. +
+ ++ Simple filtering of outgoing MIDI events is done similarly to simple filtering of incoming MIDI events, and is done by selecting Play only selected channels. Also similarly to the incoming case, Use a single fixed channel for all playback will rewrite the channel number of all outgoing events of the selected MIDI track to whichever channel is selected. +
+ ++ When either Record only selected channels or Playback only selected channels is selected, a group of three buttons, each appearing below their respective 1-by-16 grids, will become sensitive to mouse clicks. They perform the following functions: +
+ +All | +Selects all the channels in the 1-by-16 grid above it; all the squares become lit with green | +
---|---|
None | +Deselects all the channels in the 1-by-16 grid above it; all the squares become unlit | +
Invert | +Any channel in the 1-by-16 grid that is lit green becomes unlit, and any unlit channel becomes lit with green | +
- The Patch Selector window is an easy way to set which instrument will be used on any of the MIDI channels. - Although patches can be changed at any time using a patch change, this dialog - provides an easy and convenient way to preview patches in software and hardware instruments. It - integrates fully with Ardour's support for MIDNAM (patch definition files), so Ardour can display named programs/patches - for both General MIDI synths and those with MIDNAM files. -
-- The window itself makes it easy to choose a channel, a bank number, optionally choosing a bank number through its MSB - and LSB numbers (CC#00 and CC#32) for large banks, then choosing an instrument. + The Patch Selector window is an easy way to set which instrument will be used on any of the MIDI channels. Although patches can be changed at any time using a patch change, this dialog provides an easy and convenient way to preview patches in software and hardware instruments. It integrates fully with Ardour's support for MIDNAM (patch definition files), so Ardour can display named programs/patches for both General MIDI synths and those with MIDNAM files.
+- The keyboard at the bottom of the window allows for a quick preview of the selected instrument, either automatically - (using the buttons on top of the keyboard) or manually by either clicking a note or using the computer keyboard as a - piano keyboard. + The window itself makes it easy to choose a channel, a bank number, optionally choosing a bank number through its MSB and LSB numbers (CC#00 and CC#32) for large banks, then choosing an instrument.
- To edit the contents of a MIDI track see MIDI Editing. + The keyboard at the bottom of the window allows for a quick preview of the selected instrument, either automatically (using the buttons on top of the keyboard) or manually by either clicking a note or using the computer keyboard as a piano keyboard.
+ diff --git a/include/midnam-ref.html b/include/midnam-ref.html new file mode 100644 index 0000000..e5f12ed --- /dev/null +++ b/include/midnam-ref.html @@ -0,0 +1,40 @@ + +Add information of how these files are defined instead of telling the user to go modify an existing file, also, remove the “you” language!
+ ++ MIDNAM files are XML, and can be edited using any text editor. When doing so, please ensure to change the "Model" of the device, as Ardour will only load each model once (i.e. it will skip files, if there are clashes). +
+ ++ After you have done modifications to a file, it is a good idea to validate it. This can be done using the tool xmllint as shown below: +
+ +$ xmllint --valid --noout myfile.midnam
+$ wget http://www.midi.org/dtds/MIDINameDocument10.dtd
+$ xmllint --dtdvalid MIDINameDocument10.dtd myfile.midnam
+
+
++ Once you are satisfied with your file, you have to put it at a location where Ardour picks it up. The best place would be the (hidden) directory Ardour configuration directory subdirectory patchfiles. in your home-folder. Should the sub-directory patchfiles not exist yet, just create it. The path and file-names are case-sensitive. The file should end with ".midnam". +
+ ++ After restarting Ardour, hit the small Log-button in the upper right corner of the main window. It should say something like (this is Linux, MacOS or Windows will be different): +
+ +[INFO]: Loading 3 MIDI patches from /home/username/.config/ardour5/patchfiles+ +
+ The added device should now show up in the dropdown mentioned in the previous paragraph. +
+ ++ Should the MIDNAM-file be useful for the general public, it would be nice to share it: Fork the Ardour-project on gitHub by hitting the "Fork"-Button. Go to the patchfiles-directory (and read the README). +
+ ++ You can upload the file using the Web-Interface. Be sure to select "Create a new branch for this commit and start a pull request". +
+ diff --git a/include/note-cut-copy-and-paste.html b/include/note-cut-copy-and-paste.html index fe29f5d..b110fab 100644 --- a/include/note-cut-copy-and-paste.html +++ b/include/note-cut-copy-and-paste.html @@ -1,18 +1,29 @@- While in note edit mode, selected notes can be - cut and paste as in most software, that is: + While in Internal Edit Mode, selected notes can be + cut, copied, pasted, or deleted using the following keyboard shortcuts:
-
Cut | +x | +
---|---|
Copy | +c | +
Paste | +v | +
Delete | +delete | +
- These operations use the same keyboard shortcuts as most editing software does, - and as Ardour uses for regions. Obviously, the paste operation only works if a - cut or copy operation has happened beforehand. +
+ Pasted notes will appear, in the region they were cut from, at the Edit Point.
+ diff --git a/include/note-selection.html b/include/note-selection.html index 9e9efd4..931bc89 100644 --- a/include/note-selection.html +++ b/include/note-selection.html @@ -1,38 +1,35 @@ -- While in Draw mode or Internal Edit mode, any note can be clicked to select - it. Once a note has been selected, Left-clicking on another selects all notes between them. Adding - or removing a note to/from the selection is done by Left clicking it. -
+ +- In any mode, left clicking on a note on the - Scroomer (the piano header of the track, see MIDI Track Controls) will add all - occurrences of that note to the selection, while middle clicking will only select/deselect all occurences - of that note, clearing the selection. These Scroomer selections works on all - MIDI regions of the track at once. + tab selects the next note in a MIDI region, while tab selects the previous note. Holding down the key as well prevents previously visited notes from being + deselected.
+- In Internal Edit mode only, left clicking and dragging - outside of a note rubberband selects a series of notes. - rubberband selecting adds the notes to the selection. + While in Object Mode, any note can be clicked on to select it. Once a note has been selected, left-clicking on another note selects all notes between the first note selected and the second one. Adding or removing a note to or from the selection is done by left-clicking it. Clicking and dragging outside of a note will rubberband select any notes enclosed by the selection rectangle; holding down the key will prevent any previously selected notes from being deselected.
-- Tab selects the next note as defined by their starting time. - Tab selects the previous note. Tab - or Tab adds the next/previous note to the selection. + In any mode, left-clicking on a note on the + Scroomer (the piano header of the track, see MIDI Track Controls) will add all + occurrences of that note to the selection, while middle-clicking will only select/deselect all occurances + of that note, clearing the previous selection. Scroomer selections work on + all MIDI regions of a track at once.
-- If Edit > Preferences > MIDI > Sound MIDI notes - as they are selected in the editor is enabled, Ardour will send a pair of - NoteOn/NoteOff messages through the track, which will typically allow to - hear each note as it is selected. + If Edit > Preferences > MIDI > Sound MIDI notes as + they are selected is enabled, Ardour will send a pair of NoteOn/NoteOff + messages through the track as notes are selected. Assuming there is an + appropriate device or synthesizer attached to the track, these should be + audible.
diff --git a/include/osc58-jog-modes.html b/include/osc58-jog-modes.html index ee6a12c..4b9549c 100644 --- a/include/osc58-jog-modes.html +++ b/include/osc58-jog-modes.html @@ -1,8 +1,8 @@
- The /jog
command will have a different affect depending
- on which jog mode is selected. The jog system has two commands and
- gives feedback of the mode chosen.
+ The /jog
command will have a different affect depending
+ on which jog mode is selected. The jog system has two commands and
+ gives feedback of the mode chosen.
grave | octave 0 |
1 to 9 | octave 1 to 9 |
0 | octave 10 |
F1 | note length whole |
F2 | note length half |
F3 | note length third |
F4 to F8 | note length quarter to sixtyfourth |
a | insert C |
w | insert C ♯ |
s | insert D |
e | insert D ♯ |
d | insert E |
f | insert F |
t | insert F ♯ |
g | insert G |
y | insert G ♯ |
h | insert A |
u | insert A ♯ |
j | insert B |
Tab | insert rest |
Primary Tab | insert snap rest |
BackSpace | back |
z | note velocity 𝆏𝆏𝆏 |
x | note velocity 𝆏𝆏 |
c | note velocity 𝆏 |
v | note velocity 𝆐𝆏 |
b | note velocity 𝆐𝆑 |
n | note velocity 𝆑 |
m | note velocity 𝆑𝆑 |
comma | note velocity 𝆑𝆑𝆑 |
Up | next note velocity |
Down | prev note velocity |
Primary Up | next note length |
Primary Down | prev note length |
apostrophe | toggle triplet |
period | toggle dotted |
Primary period | no dotted |
bar | toggle chord |
` (grave accent) | Set octave 0 |
1 to 9 | Set octave 1 to 9 |
0 | Set octave 10 |
f1 | Set note length whole |
f2 | Set note length half |
f3 | Set note length third |
f4 to f8 | Set note length quarter to sixtyfourth |
a | Insert C |
w | Insert C♯ |
s | Insert D |
e | Insert D♯ |
d | Insert E |
f | Insert F |
t | Insert F♯ |
g | Insert G |
y | Insert G♯ |
h | Insert A |
u | Insert A♯ |
j | Insert B |
tab | Insert rest |
tab | Insert snap rest (?) |
backspace | Set insert cursor back one note length |
z | Set note velocity 𝆏𝆏𝆏 |
x | Set note velocity 𝆏𝆏 |
c | Set note velocity 𝆏 |
v | Set note velocity 𝆐𝆏 |
b | Set note velocity 𝆐𝆑 |
n | Set note velocity 𝆑 |
m | Set note velocity 𝆑𝆑 |
, (comma) | Set note velocity 𝆑𝆑𝆑 |
↑ | Set next note velocity |
↓ | Set prev note velocity |
↑ | Set next note length |
↓ | Set prev note length |
' | Toggle triplet |
. | Set single dotted |
. | Clear dotted |
bar (?) | Toggle chord |
Richard Ames presents a long (28 minute) video that is very helpful if you want to understand these issues in more - depth. It is a little bit Windows-centric, but the explanations to + depth. It is a little bit Windows-centric, but the explanations apply to all types of computers and operating systems.
+ diff --git a/include/toolbox.html b/include/toolbox.html index 60a561f..8b6a5cc 100644 --- a/include/toolbox.html +++ b/include/toolbox.html @@ -1,16 +1,16 @@ +Requires sanity checking; the section on Internal Edit mode is wrong in a few places. It seems the description of Audition Mode is incorrect with respect to scrubbing; it seems to work but not in any predictable manner.
+- Ardour has a global edit mode selector at the left of the - Editing toolbar, which affect how regions are moved or copied: + Ardour has a global Edit Mode selector at the left side of the + Editing toolbar, which affects how regions are moved or copied:
- Ripple Edit mode provides the following conveniences: + Ripple Edit mode provides the following:
- The Smart Mode button to the left of the mouse mode buttons - modifies the Grab Mode. When enabled, the mouse behaves as if it - is in "Range Mode" in the upper half of a region, and in "Grab Mode" in the - lower half. This allows avoiding constant switching between these two modes. + The Smart Mode toggle button (shortcut: y) to the left + of the mouse mode buttons modifies the behavior of Grab Mode: when + enabled, the mouse behaves as if it is in Range Mode in the upper + half of a region, while behaving as if it is in Grab Mode in the + lower half. This makes it possible to avoid constant switching between these + two modes.
Grab Mode | -The Grab Mode is used for selecting, moving, deleting and - copying objects. When in object mode, the mouse pointer appears as a hand - whenever it is over the track canvas or the rulers. The mouse can now be - used to select and perform operations on objects such as regions, markers etc. - This is the most common mode to work in, as it allows you to select and move regions, - as well as modify automation points on the automation tracks. |
---|---|
Range Mode | -When in Range Mode, the mouse pointer appears as a vertical line
- whenever it is over the track canvas or the rulers. The mouse will now be
- able to select a point or range of time. Time ranges can be selected over
- one or several tracks, depending on the selection of your tracks. - If none of your tracks are selected, the Range Tool will operate on all the - session track visualized in the Editor. - If you want to edit only particular tracks, select them before you apply - the range tool. |
Cut Tool Mode | -When in Cut Tool Mode, the mouse pointer appears as a pair of scissors
- whenever it is over the track canvas or the rulers. This tools allows to cut
- any region into 2 regions at the mouse cursor, regardless of the Edit Point. - If one or more track(s) is selected, then all the regions on these tracks will - be split at the mouse cursor position. - If no track is selected, then only the region hovered by the mouse cursor will - be split. |
Stretch Mode | -When in time fx mode, the mouse pointer appears as a - distinctive expanding square symbol whenever it is over the track canvas or - the rulers. This mode is used to resize regions using a timestretch - algorithm. Click on an edge of a region of audio and drag it one way or the other to - stretch or shrink the region. |
Audition Tool | -Clicking a region using the audition tool will play this
- region to the control room outputs. - You can also scrub with this tool by clicking and dragging in - the direction you wish to listen. The amount you drag in one direction or - the other will determine the playback speed. |
Draw Tool | -When in Draw Tool mode, the mouse pointer will change to
- a pencil. You can then click within an audio region to change the gain
- envelope for that region. This curve is separate from fader automation
- for individual tracks. It will remain locked to the region's time, so if the
- region is moved, the region gain envelope is moved along with it. - The draw tool works on automation too, allowing the creation and modification - of control points on the automation curves. - Last, it is used on a MIDI region to edit the notes. |
Internal/Region Edit Mode | -When in Internal Edit mode, the mouse pointer will change to
- cross-hairs. This tool acts on region gain and automation as the Draw tool. - On a MIDI region, it allows to lasso-select multiple notes at a time. |
Mode | Keyboard Shortcut |
---|---|
Grab | g |
Range | r |
Cut | c |
Stretch | t |
Audition | None |
Draw | d |
Internal Edit | e |
+ Changes to the mouse pointer only occur when hovering over the track canvas; + the mouse pointer always changes to a hand in the ruler area + regardless of what mode is selected, and always moves the playhead to the position left-clicked on—as long as there is no marker or other tag under the mouse position clicked on. +
+ ++ Grab Mode is used for selecting, moving, deleting and copying + objects. In this mode, the mouse pointer appears as a hand and can be used to select and perform various operations on objects such as regions, markers and etc. This is the most common mode to work in, as it allows the for selection and moving of regions, as well as the modification of control points in automation lanes. +
+ ++ In Range Mode, the mouse pointer appears as a vertical line; left-clicking on the track canvas will display the time at the position clicked on. left-clicking and dragging on the track canvas will create a time range for the track clicked and dragged on; adjacent tracks can be selected as well by dragging the mouse into them. Once a time range has been defined, it can be resized by left-clicking on either the left-hand or right-hand side of the range and dragging the mouse to the desired position. +
+ ++ In Cut Tool Mode, the mouse pointer appears as a pair of scissors and allows for the separation of any region into two distinct regions by left-clicking at the desired point of separation. If more than one track is selected, then all the regions on the selected tracks will be split at the point clicked on. If no track is selected, then only the region hovered by the mouse cursor will be split. +
+ ++ In Stretch Mode, the mouse pointer appears as an expanding square symbol and is used to resize regions using a timestretch algorithm. Resizing a region is done by left-clicking on the right-hand side of the region and dragging the edge to the desired position; once the button is released a Time Stretch Audio dialog will appear. +
+ ++ left-clicking on a given region using Audition Mode will play the contents of that region (along with all other non-muted tracks). The regions can also be scrubbed by left-clicking and dragging in the direction desired; the amount dragged in one direction or the other will determine the playback speed. +
+ ++ In Draw Mode, the mouse pointer will change to a pencil; the effect it will have depends on the type of track or region it is utilized in. +
+ ++ In an audio track, a green line will appear in the region which is that region's gain envelope. left-clicking anywhere in a given region between two existing control points will add one to the region at the X-coordinate clicked on with the Y-coordinate being on the line connecting the control points on either side of the new one. left-clicking on a control point will allow it to be moved to any point in the region in between the control points that bound it on either side of itself. And finally, left-clicking on a control point and pressing the delete key or holding down the key while right-clicking on it will delete the control point. +
+ ++ In an automation lane, if any automation is defined in it, a green line connecting its control points will appear in the lane. Control points in the lane are manipulated in exactly the same way as they are in a region's gain envelope (see previous paragraph for details). +
+ ++ In a MIDI track, if the mouse is left-clicked in a part of the track that has no region, a region one bar long will be created. If the mouse is dragged after being left-clicked in a part of the track that has no region, a region of arbitrary length will be created by releasing the mouse at the desired length. + l-click in region depends on note mode, sustained inserts note with length of snap grid(?) while percussive enters a diamond; l-click & drag draws note of arb. length in sustained while percussive draws a succession of diamonds in the dragged area, # & type depend on grid & divisions. +
+ ++ In Internal Edit Mode, the mouse pointer will change to + cross-hairs. This tool acts on region gain and automation as the Draw tool. + On a MIDI region, it allows to lasso-select multiple notes at a time. +
+ diff --git a/include/track-automation.html b/include/track-automation.html index 12c52ac..98ce1bd 100644 --- a/include/track-automation.html +++ b/include/track-automation.html @@ -1,12 +1,12 @@- To automate a parameter on a given track, click on the track's A button and select a parameter to control from the menu + A parameter on a given track can be automated by clicking on the track's A button and selecting a parameter to control from the menu that appears. Once a parameter has been selected, an automation lane for that parameter will appear beneath the track. The lane thus shown will be empty; from here an automation curve must be defined. @@ -23,9 +23,9 @@
- In Draw mode, control points can be entered in the - automation lane by Left-clicking in the lane at a + In Draw mode, control points can be entered in the + automation lane by left-clicking in the lane at a point where there is no existing control point.
- Once added, a control point can be Left-clicked and - dragged to a desired location. Hovering over a control point will show its - current level in dB. To remove a control point, Left-click it and press Delete, or Right-click on it. + Once added, a control point can be left-clicked and + dragged to any desired location. Hovering over a control point will show its + current value. To remove a control point, left-click + it and press Delete, or right-click on it.
+ Clearing the automation lane is done by right-clicking on the lane to be cleared, and selecting + Clear from the menu that appears. +
+ diff --git a/include/track-types.html b/include/track-types.html index c1afee9..ad290ff 100644 --- a/include/track-types.html +++ b/include/track-types.html @@ -64,7 +64,7 @@ or "vocals") to allow controlling the gain of all those tracks at once in the mix while retaining their relative gain.- Considering the numerical nature of MIDI events, it can be tempting to apply - mathematical transformations to our MIDI regions by using mathematical - operations. Ardour makes it very easy and powerful with the Transform tool. + Considering the numerical nature of MIDI events, it can be useful to + transform a MIDI region by applying mathematical operations to it. Ardour + makes this kind of powerful transformation very easy with the Transform tool. The tool makes possible things such as humanizing (randomizing the velocity, start time and duration of all the notes), creating arpeggios, automating tedious tasks, transposing, etc.
-To access the Transform tool, right click the MIDI region > name_of_the_region > MIDI > Transform…
++ To access the Transform tool, right click the MIDI region > + name_of_the_region > MIDI > Transform…. +
-First, select the property you want to modify in the 'Set' field, then change the target value using the 2 following fields. If you want to add more operands, click the "+" sign to create new lines. You can remove a superfluous line using the "-" sign on the right of the newly created line.
++ First, the property to be modified in the Set field + is selected, then the target value is changed using the two fields that + follow. If more operands are desired, the + button is + clicked to create new lines. Any superfluous line can be removed by clicking + on the - button on the right side of the line to be + removed. Finally, once everything is set as desired, the Transform button is pressed to apply the transformation. +
- In the picture above, the Transform tool has been used to add a bit of - humanisation, by slightly changing the velocity of each note of the region, by - a random number between -19 and +19 from its original velocity. So - three operations are applied: + In the image above, the Transform tool has been used to add a bit of + humanization, by slightly changing the velocity of each note of the region by + a random number between -19 and +19 from its original velocity. So the + following three operations are applied:
- Each note will trigger a calculation of its own, so its velocity will be - increased by a random number between 1 and 20, then decreased by a random - number between 1 and 20. + Each note will trigger a unique calculation, where its velocity will be + increased by a random number between 1 and 20, then decreased by a random + number between 1 and 20. This will result in a new velocity being applied to + the note, which will be the original velocity plus or minus 19.
- The properties that can be computed are: + The parameters that can be transformed are:
- and the calculation may be based on the following properties: + and the transformation can be based on any of the following:
- The mathematical operators can be: + The mathematical operators are:
- All these operations can be very handy, as long as there is a mathematical way - to achieve the targeted goal. Beware though of odd "border cases": division by - zero (which does nothing), using the note's index and forgetting it starts at - 0 and not 1, etc. + Keep in mind that while the Transform tool is powerful, it is not infallible. + Things like division by zero (which does nothing), using the note's index and + thinking that it starts at one (instead of zero), etc. can yield + unexpected results.
-
- Very interesting results can nevertheless be created, like humanizing - (randomizing the velocity, start time and duration of all the notes), creating - arpeggios, automating tedious tasks, transposing, etc. -
diff --git a/master-doc.txt b/master-doc.txt index abf5c63..7565d2c 100644 --- a/master-doc.txt +++ b/master-doc.txt @@ -633,6 +633,7 @@ part: chapter --- title: Editor Tracks link: track-controls +uri: ardours-interface/editor-tracks part: chapter --- @@ -1294,10 +1295,9 @@ part: part --- --- -title: MIDI Editing -include: edit-midi.html -link: edit-midi -uri: working-with-midi +title: MIDI Overview +include: midi-overview.html +link: midi-overview part: chapter --- @@ -1306,7 +1306,7 @@ title: Creating MIDI Tracks include: create-midi-tracks.html link: create-midi-tracks uri: working-with-midi/create-midi-tracks -part: chapter +part: subchapter --- --- @@ -1314,6 +1314,14 @@ title: Creating MIDI Regions include: create-midi-regions.html link: create-midi-regions uri: working-with-midi/create-midi-regions +part: subchapter +--- + +--- +title: MIDI Editing +include: edit-midi.html +link: edit-midi +uri: working-with-midi part: chapter --- @@ -1322,15 +1330,7 @@ title: Adding New Notes include: add-new-notes.html link: add-new-notes uri: working-with-midi/add-new-notes -part: chapter ---- - ---- -title: Changing Note Properties -include: change-note-properties.html -link: change-note-properties -uri: editing-and-arranging/editing-midi/changing-note-properties -part: chapter +part: subchapter --- --- @@ -1339,15 +1339,7 @@ menu_title: Overlapping Notes include: handling-overlapping-notes.html link: handling-overlapping-notes uri: working-with-midi/handle-overlapping-notes -part: chapter ---- - ---- -title: Note Cut, Copy and Paste -include: note-cut-copy-and-paste.html -link: note-cut-copy-and-paste -uri: working-with-midi/note-cut-copy-and-paste- -part: chapter +part: section --- --- @@ -1355,23 +1347,23 @@ title: Note Selection include: note-selection.html link: note-selection uri: editing-and-arranging/edit-midi/note-selection -part: chapter +part: subchapter --- --- -title: Quantizing MIDI -include: quantize-midi.html -link: quantize-midi -uri: working-with-midi/quantize-midi -part: chapter +title: Note Cut, Copy and Paste +include: note-cut-copy-and-paste.html +link: note-cut-copy-and-paste +uri: working-with-midi/note-cut-copy-and-paste- +part: subchapter --- --- -title: Step Entry -include: step-entry.html -link: step-entry -uri: working-with-midi/step-entry -part: chapter +title: Changing Note Properties +include: change-note-properties.html +link: change-note-properties +uri: editing-and-arranging/editing-midi/changing-note-properties +part: subchapter --- --- @@ -1379,7 +1371,7 @@ title: Patch Change include: patch-change.html link: patch-change uri: working-with-midi/patch-change -part: chapter +part: subchapter --- --- @@ -1388,7 +1380,15 @@ menu_title: Copy MIDI Region include: independent-and-dependent-midi-region-copies.html link: independent-and-dependent-midi-region-copies uri: working-with-midi/copy-midi-region -part: chapter +part: subchapter +--- + +--- +title: Quantizing MIDI +include: quantize-midi.html +link: quantize-midi +uri: working-with-midi/quantize-midi +part: subchapter --- --- @@ -1396,52 +1396,67 @@ title: Transposing MIDI include: transposing-midi.html link: transposing-midi uri: working-with-midi/transpose-midi -part: chapter +part: subchapter --- --- -title: Automating MIDI-Pitch bending and aftertouch -menu_title: Automating MIDI -include: automating-midi---pitch-bending-and-aftertouch.html -link: automating-midi---pitch-bending-and-aftertouch -uri: working-with-midi/automation-midi -part: chapter +title: MIDI List Editor +include: midi-list-editor.html +link: midi-list-editor +part: subchapter --- --- -title: Transforming MIDI-Mathematical operations +title: Transforming MIDI—Mathematical Operations menu_title: Transforming MIDI include: transforming-midi---mathematical-operations.html link: transforming-midi---mathematical-operations uri: working-with-midi/transformation-midi -part: chapter +part: subchapter --- --- -title: MIDI List Editor -include: midi-list-editor.html -link: midi-list-editor +title: MIDI Recording +include: midi-recording.html +link: midi-recording part: chapter --- --- -title: MIDI Tracer -include: midi-tracer.html -link: midi-tracer -part: chapter +title: Step Entry +include: step-entry.html +link: step-entry +uri: working-with-midi/step-entry +part: subchapter --- --- -title: MIDI Recording -link: midi-recording +title: MIDI Automation +include: midi-automation.html +link: midi-automation part: chapter --- +--- +title: Pitch Bend & Aftertouch +include: automating-midi---pitch-bending-and-aftertouch.html +link: automating-midi---pitch-bending-and-aftertouch +uri: working-with-midi/automation-midi +part: subchapter +--- + --- title: MIDI Scene Automation include: midi-scene-automation.html link: midi-scene-automation uri: automation/midi-scenes +part: subchapter +--- + +--- +title: MIDI Tracer +include: midi-tracer.html +link: midi-tracer part: chapter --- @@ -1585,7 +1600,7 @@ title: Mono Panner include: mono-panner.html link: mono-panner uri: mixing/panning/mono_panner -part: subchapter +part: section --- --- @@ -1593,7 +1608,7 @@ title: Balance Control include: balance-control.html link: balance-control uri: mixing/panning/balance_control -part: subchapter +part: section --- --- @@ -1601,7 +1616,7 @@ title: Stereo Panner include: stereo-panner.html link: stereo-panner uri: mixing/panning/stereo_panner -part: subchapter +part: section --- --- @@ -1609,7 +1624,7 @@ title: VBAP Panner include: vbap-panner.html link: vbap-panner uri: mixing/panning/vbap_panner -part: subchapter +part: section --- --- @@ -1785,7 +1800,7 @@ part: chapter --- --- -title: OSC: Controlling Ardour with OSC +title: Controlling Ardour with OSC include: osc58-controlling-ardour-with-osc.html link: osc58-controlling-ardour-with-osc uri: using-control-surfaces/controlling-ardour-with-osc/osc-control @@ -1793,7 +1808,7 @@ part: subchapter --- --- -title: OSC: Using the Setup Dialog +title: Using the Setup Dialog include: osc58-using-the-setup-dialog.html link: osc58-using-the-setup-dialog uri: using-control-surfaces/controlling-ardour-with-osc/osc-setup-dialog @@ -1801,7 +1816,7 @@ part: subchapter --- --- -title: OSC: Linking Surfaces +title: Linking Surfaces include: osc58-linking-surfaces.html link: osc58-linking-surfaces uri: using-control-surfaces/controlling-ardour-with-osc/linking-surfaces @@ -1809,7 +1824,7 @@ part: subchapter --- --- -title: OSC: Querying Ardour +title: Querying Ardour include: osc58-querying-ardour.html link: osc58-querying-ardour uri: using-control-surfaces/controlling-ardour-with-osc/querying-ardour-with-osc @@ -1817,7 +1832,7 @@ part: subchapter --- --- -title: OSC: Feedback +title: Feedback include: osc58-feedback.html link: osc58-feedback uri: using-control-surfaces/controlling-ardour-with-osc/feedback-in-osc @@ -1825,7 +1840,7 @@ part: subchapter --- --- -title: OSC: Feedback and Strip-types Values +title: Feedback and Strip-types Values include: osc58-feedback-and-strip-types-values.html link: osc58-feedback-and-strip-types-values uri: using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values @@ -1833,7 +1848,7 @@ part: subchapter --- --- -title: OSC: Jog Modes +title: Jog Modes include: osc58-jog-modes.html link: osc58-jog-modes uri: using-control-surfaces/controlling-ardour-with-osc/jog-modes @@ -1841,7 +1856,7 @@ part: subchapter --- --- -title: OSC: Custom Strip Lists +title: Custom Strip Lists include: osc58-custom-strips.html link: osc58-custom-strips uri: using-control-surfaces/controlling-ardour-with-osc/custom-strips @@ -1849,7 +1864,7 @@ part: subchapter --- --- -title: OSC: Automation +title: Automation include: osc58-automation.html link: osc58-automation uri: using-control-surfaces/controlling-ardour-with-osc/automation @@ -1857,7 +1872,7 @@ part: subchapter --- --- -title: OSC: Personal Monitoring Control +title: Personal Monitoring Control include: osc58-personal-monitoring-control.html link: osc58-personal-monitoring-control uri: using-control-surfaces/controlling-ardour-with-osc/osc-personal-monitoring @@ -1865,7 +1880,7 @@ part: subchapter --- --- -title: OSC: Parameter Types +title: Parameter Types include: osc58-parameter-types.html link: osc58-parameter-types uri: using-control-surfaces/controlling-ardour-with-osc/parameter-types-in-osc @@ -1873,7 +1888,7 @@ part: subchapter --- --- -title: OSC: Selection and Expansion Considerations +title: Selection and Expansion Considerations include: osc58-selection-and-expansion-considerations.html link: osc58-selection-and-expansion-considerations uri: using-control-surfaces/controlling-ardour-with-osc/selection-considerations-in-osc @@ -2056,8 +2071,16 @@ part: chapter --- --- -title: MIDI notes reference +title: MIDI Notes Reference include: midi-notes-ref.html link: midi-notes-ref part: chapter --- + +--- +title: MIDNAM Reference +include: midnam-ref.html +link: midnam-ref +part: chapter +--- + diff --git a/source/css/screen.css b/source/css/screen.css index bb0f469..6c38a03 100644 --- a/source/css/screen.css +++ b/source/css/screen.css @@ -166,7 +166,7 @@ #content figcaption.titleover { text-align: center; - caption-side: top ; + caption-side: top; } #content figure.right { @@ -194,6 +194,10 @@ width: 100%; } +#content img.fit { + width: 100%; +} + kbd { text-shadow: 0 0 2px rgb(255, 255, 255); box-shadow: inset 0 0 1px rgb(255, 255, 255), inset 0 0 .4em rgb(200, 200, 200), 0 .1em 0 rgb(130, 130, 130), 0 .11em 0 rgba(0, 0, 0, .4), 0 .1em .11em rgba(0, 0, 0, .9); diff --git a/source/images/automation-audio-r-click-menu.png b/source/images/automation-audio-r-click-menu.png new file mode 100644 index 0000000000000000000000000000000000000000..6a6134d4c3f79dcc3c337a4b6a29096a54519239 GIT binary patch literal 25372 zcmeFZbyOVPwl9hV2~Kbl9D=)hf&_PWZQL7ohhV`HAZTzWxVuB};O>yd32v{*x6j_+ zd2hdS?-}FX|4#R4M%AjhX3d&w+HbBJd{mT|Kt&=%f`WoVm68-whJu1_0FEyZ;eo&8 zUTd{bP&huGs+!KqMsB1IPWEP&HXu@G4+jt_$lcNm3d((5md3lE7E-)yfEcm>nZt zd>^TLtW3l57&wj=ZfT_OPYkSSk67Chl2mx3P;s;jjSQS8*cww#5q}roG99nXl+M
zf2v4M o&!C&+xMJx_KITcw&sQueQimCzm{2T}DFp
zqc(Wtk&zKqZEX^Met!1SSJMj#Mm4Ws+c8us=ItLuh-j9^kHX(;*Id#{Sgv7~mM(|l
ztvvOjjep|*skt}IVK%|F%OvFCL4r4eiw816Fzh-hO=o|_9e2>FV|Q?^@0-G@z#m!Y
z$N#t**}q;jyN^u3=GcnpUR)s$Fx5iae964hrYK_E(&|>m#JJ9(5crtlm&8h%*o VXmr4$Z;0|+{h3c@)$2V{S3US?VfRwbZjllP&`vt{?%~xSS2eu{WPXow8=78!8WeO`uN-6o!8z!hC
zJJL8#eDA=+aLQZS942x+i_C@n(`2C
3Pv9*Q|KjJ^9^FNGn>-kW>of
z%P^fDZZAwWdOpgg^VN11D+tCVrJuw=C7=B5OJ
zbEo`6m*p*jQ2*%XU%iO@%?b!eNi=VzX8Qx{kH2~eVHAzEELChGbbd#5X}Mx5lj-0
zF#C&|fB1Lu0&gr%>Up%@ad~EEKkLJpBCiCnVGchO>68m11r+VeO&4Z2hwehQ=Fv}D
zU;nGLqfY1_?ukW4N4Gf*3b!Hcn#CXx=9T0FToMuz_v49`)6EJRoU(;3gWmky)Hg0J
z+^h||UGFYhFev**H4LQn^(oM-5hV*>2=%{bnF#u0U@s3#QO&7YN)
zDtqoi=}X3zc9&scn6`~B9Kb&a?f