Ctrl x means "press the Ctrl key, keep it pressed - and then also press the x key. You may also see key combinations + and then also press the x key. +
++ You may also see key combinations such as e, which mean that you should hold down the key and the - key, and then while keeping them both + key, and then, while keeping them both down, press the e key.
@@ -30,6 +33,44 @@ title: About Ardour documentation in the first example above). On other machines you will see Ctrl instead.
+ ++ We refer to mouse buttons as + Left, Middle and + Right. Ardour can use additional buttons, but they have + no default behaviour in the program. +
+ ++ Many editing functions are performed by clicking the mouse while holding a + modifier key, for example Left. +
+ ++ Many times the term context-click is used to indicate + that you should (typically) right-click on a particular element of the graphical + user interface. Although right-click is the common, default way to do this, there + are other ways to accomplish the same thing - this term refers to any of them, + and the result is always that a menu specific to the item you clicked on will be + displayed. +
+ ++ When the manual refers to the "pointer", it means the on-screen representation + of the mouse position or the location of a touch action if you are using a touch + interface. +
+ ++ Ardour supports hardware controllers, such as banks of + faders, knobs, or + buttons. +
@@ -54,6 +95,21 @@ title: About Ardour documentation
Option.
+ Some dialogs or features may require you to type in some data + such as this. In rare cases, you will be required to perform certain + operations at the command line of your operating system: +
+cat /proc/cpuinfo +sleep 3600 +ping www.google.com + ++ Important messages from Ardour or other programs will be displayed + like this. +
@@ -67,42 +123,3 @@ title: About Ardour documentation quality is displayed in this way.
- -- We refer to mouse buttons as - Left, Middle and - Right. Ardour can use additional buttons, but they have - no default behaviour in the program. -
- -- Many editing functions are performed by clicking the mouse while holding a - modifier key, for example Left. -
- -- Many times the term context-click is used to indicate - that you should (typically) right-click on a particular element of the graphical - user interface. Although right-click is the common, default way to do this, there - are other ways to accomplish the same thing - this term refers to any of them, - and the result is always that a menu specific to the item you clicked on will be - displayed. -
- -- When the manual refers to the "pointer", it means the on-screen representation - of the mouse position or the location of a touch action if you are using a touch - interface. -
- -- Ardour supports hardware controllers, such as banks of - faders, knobs, or - buttons. -
- diff --git a/_manual/03_setting-up-your-system.html b/_manual/03_setting-up-your-system.html index 67435ce..84c4a86 100644 --- a/_manual/03_setting-up-your-system.html +++ b/_manual/03_setting-up-your-system.html @@ -2,10 +2,12 @@ layout: default title: Setting Up Your System --- - - - -Using a general purpose computer for recording digital audio is not always trivial. This chapter will guide you through the basic steps and help you with some of the most common pitfalls.
++ Using a general purpose computer for recording digital audio is not + trivial. This chapter will guide you through the basic steps and help + you with some of the most common pitfalls on the way to a reliable and + powerful audio workstation. +
{% children %} diff --git a/_manual/03_setting-up-your-system/01_the-right-computer-system-for-digital-audio.html b/_manual/03_setting-up-your-system/01_the-right-computer-system-for-digital-audio.html index ed101a0..d09a5f2 100644 --- a/_manual/03_setting-up-your-system/01_the-right-computer-system-for-digital-audio.html +++ b/_manual/03_setting-up-your-system/01_the-right-computer-system-for-digital-audio.html @@ -4,56 +4,107 @@ title: The Right Computer System for Digital Audio menu_title: The Right Computer System --- -It would be nice to think that you could just go and buy any computer, install a bit of software on it and start using it to record and create music. This idea isn't wrong, but there some important details that it misses.
-Any computer that you can buy today (somewhere around the end of 2012) is capable of recording and processing a lot of audio data. It will come with a builtin audio interface that can accept inputs from microphones or electrical instruments. It will have a disk with a huge amount of space for storing audio files.
-When you are recording, editing and mixing music, you generally want to work with very little delay between the time that a sound is generated and when you can hear it. When the audio signal flows through a computer, that means that the computer has to be able to receive the signal, process it and send it back out again as fast as possible. And that is where it becomes very important what computer system you have, because it is absolutely not the case that any computer can do this job well.
-Routing audio through a computer will always cause some delay, but if it is small, you will generally never notice it. There are also ways to work in which the delay does not matter at all (for example, not sending the output from the computer to speakers).
-The delay or "latency" that you want for working with digital audio is more typically in the 1-5msec range. For comparison, if you are sitting 1m (3ft) from your speakers, the time the sound takes to reach your ears is about 3msec. Any modern computer can limit the delay to 100msec. Most can keep it under 50msec. Many will be able to get down to 10msec without too much effort. If you try to reduce the delay on a computer that cannot meet your goal, you will get clicks and glitches in the audio, which is clearly extremely undesirable.
-Many, many things can affect the lowest latency that a computer can support.
-+ It would be nice to think that you could just go and buy any computer, + install a bit of software on it and start using it to record and create + music. This idea isn't wrong, but there some important details that it + misses. +
++ Any computer that you can buy today (since somewhere around the end of + 2012) is capable of recording and processing a lot of audio data. It + will come with a builtin audio interface that can accept inputs from + microphones or electrical instruments. It will have a disk with a huge + amount of space for storing audio files. +
+
+ When you are recording, editing and mixing music, you generally want to
+ work with very little latency between the time that
+ a sound is generated and when you can hear it. When the audio signal
+ flows through a computer, that means that the computer has to be able to
+ receive the signal, process it and send it back out again as fast as
+ possible.
+ And that is where it becomes very important what computer system
+ you have, because it is absolutely not the case that any
+ computer can do this job well.
+
+ Routing audio through a computer will always cause some delay, but if it + is small, you will generally never notice it. There are also ways to work + in which the delay does not matter at all (for example, not sending the + output from the computer to speakers). +
++ The latency that you want for working with digital audio is typically in + the 1–5 ms range. For comparison, if you are sitting 1 m + (3 ft) from your speakers, the time the sound takes to reach your + ears is about 3 ms. Any modern computer can limit the delay to + 100 ms. Most can keep it under 50 ms. Many will be able to get + down to 10 ms without too much effort. If you try to reduce the delay + on a computer that cannot meet your goal, you will get clicks and + glitches in the audio, which is clearly extremely undesirable. +
+ +- diff --git a/_manual/03_setting-up-your-system/02_mouse.html b/_manual/03_setting-up-your-system/02_mouse.html index f56d66a..36e0c7b 100644 --- a/_manual/03_setting-up-your-system/02_mouse.html +++ b/_manual/03_setting-up-your-system/02_mouse.html @@ -2,18 +2,28 @@ layout: default title: Mouse --- - - - -
Ardour is designed to work best with a three button mouse equipped with a scroll wheel.
-It can be used with a two button mouse or touchpad, but at least two key operations will not (easily) be available to you:
++ Ardour is designed to work best with a three button mouse + equipped with a scroll wheel. +
++ It can be used with a two button mouse or touchpad, but at least two key + operations will not (easily) be available to you: +
You are strongly encouraged to invest in a two button mouse. You will find that a good quality mouse (especially one with a weighted, latchable scroll wheel) will make your use of Ardour vastly more efficient. They are cheap, and time is not.
- -For more detailed instructions see Using the mouse.
++ You are strongly encouraged to invest in a three-button mouse. You will + find that a good quality mouse (especially one with a weighted, + latchable scroll wheel) will make your use of Ardour vastly more + efficient. They are cheap, and time is not. +
++ For more detailed instructions, see + Using the mouse. +
diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi.html b/_manual/03_setting-up-your-system/05_setting-up-midi.html index 4300353..ba9d6e1 100644 --- a/_manual/03_setting-up-your-system/05_setting-up-midi.html +++ b/_manual/03_setting-up-your-system/05_setting-up-midi.html @@ -3,35 +3,62 @@ layout: default title: Setting Up MIDI --- -MIDI is a way of both describing musical data and controlling musical hardware\software. MIDI doesn't actually create any audio but rather describes the audio in order to control hardware/software. Ardour can import MIDI data, record MIDI data and allow MIDI data to be edited in a variety of ways. Also, MIDI can be used to control various things withing Ardour. This allows for the most flexible work flow with regards to MIDI. What Ardour doesn't have is any built in synthesis to turn the MIDI data into audio. Rather, this is handled through the use of plug-ins and external hardware/software. While this makes MIDI a powerful tool it can also be a stumbling block for first time users who expect MIDI input to result in audio output by default. Please see the section on working with plug-ins for more information on turning MIDI data into audio output with Ardour.
++ MIDI + is a way to describe music data and to control music hardware and + software. Ardour can import and record MIDI data, and perform a + variety of editing operations on it. Furthermore, MIDI can be used to + control various functions of Ardour. +
+
+ Ardour does not include a synthesis engine to produce audio
+ from MIDI data, but relies on plugins or external hard- and software
+ for the task. This can be a stumbling block for first time users who
+ expect MIDI input to result in audio output by default.
+ Please see the section on working with plug-ins for more information on
+ turning MIDI data into audio output.
Below is a list of various MIDI Frameworks for getting MIDI data into and out of Ardour in order to work with MIDI aware software/hardware.
-+ Ardour supports various ways of sending and receiving MIDI data: +
-CoreMIDI is the standard MIDI framework to comunicate with MIDI -hardware on OSX systems. It provides drivers and libraries needed by -MIDI clients. These ports do not show up in qjackctl
++ CoreMIDI is the standard MIDI framework on OSX systems. + It provides drivers for MIDI hardware and libraries needed by MIDI + software clients. +
+ ALSA MIDI + is the standard MIDI framework on Linux systems. It provides drivers + for MIDI hardware and libraries needed by MIDI software clients. +
++ The QJackCtl control software displays ALSA MIDI ports + under its "ALSA" tab (it does not currently display CoreMIDI ports). +
-ALSA MIDI is the standard MIDI framework to comunicate with MIDI -hardware on Linux systems. It provides drivers and libraries needed by -MIDI clients. These ports show up under the "ALSA" tab in qjackctl
+JACK MIDI is a framework used to comunicate between JACK MIDI -software clients. It provides zero jitter and a fixed latency of 1 -"period" (the same latency that exists for audio). These ports show up -under the "MIDI" tab in qjackctl. +
+ JACK MIDI + is a framework used to comunicate between JACK MIDI software clients. + It provides zero jitter and a fixed latency of one period, + the same latency as for JACK audio. +
++ JACK MIDI ports show up under the MIDI tab in + QJackCtl.
-Various ways of "bridging" between the native MIDI framework -(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections -below. + There are several ways of bridging between the native MIDI frameworks + (e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections + below.
{% children %} diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi/01_midi-on-os-x.html b/_manual/03_setting-up-your-system/05_setting-up-midi/01_midi-on-os-x.html index 84d0c24..c296261 100644 --- a/_manual/03_setting-up-your-system/05_setting-up-midi/01_midi-on-os-x.html +++ b/_manual/03_setting-up-your-system/05_setting-up-midi/01_midi-on-os-x.html @@ -2,17 +2,32 @@ layout: default title: MIDI on OS X --- + ++ In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI + bridge + is required. This feature is available on versions equal to or great than + version 0.89 of JackOSX. +
- - -In order for CoreMIDI to work with Jack MIDI a version of JACK for OS X that has a working CoreMIDI - JACK MIDI bridge is required. This feature is available on versions equal to or great than version 0.89 of JackOS X.
- -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.
-There are multiple options for connecting MIDI ports outside of Ardour
-MIDI Monitor is a handy tool for doing various things with midi on OS X.
-MIDI Patchbay is a handy tool for connecting MIDI ports.
++ MIDI ports show up in Ardour's MIDI connection matrix in multiple + locations. Bridged CoreMIDI ports as well as JACK MIDI ports that have + been created by other software clients will show up under the "Other" tab. + Bridged CoreMIDI hardware ports show up under the "Hardware" tab. +
+ ++ There are multiple options for connecting MIDI ports outside of Ardour. +
+a2jmidid is an application that "bridges" between the system MIDI ports and JACK.
First you should be sure that there is no ALSA sequencer support enabled in jack. To do that open qjackctl's Setup window.
-In the Settings tab set the MIDI Driver drop down to the none option.
-Then go to the Misc tab and uncheck the Enable ALSA Sequencer support option.
-Now it's time to restart your jack server before going on.
-First thing is checking if a2jmidid is already installed in your system. To do it first start your jack server and then call
-a2jmidid -e-
from the command. If a2jmidid is there go on with Checking surface control MIDI ports. Otherwise install the newest a2jmidid available and try again.
-After starting a2jmidid your control surface MIDI ports should appear in qjackctl's Connections window on the MIDI tab under a2j. If it does go on to the next step: Automatically calling a2jmidid when starting jack. If it doesn't you have to troubleshoot why it didn't. (How to troubleshoot a2jmidid?)
-It's troublesome to have to manually start a2jmidid by hand each time you start jack. Here is one way to do it automatically. This step isn't mandatory, it's just a convenience. If you are not interested you can go on to the next step Enabling Ardour's mackie control ports in qjackctl.
-Create a script that calls jack if you aren't using one yet. In it change the line that calls jack to have an ampersand at it's end like that:
--/usr/bin/qjackctl & --
In this case I call qjackctl that starts jack so I include the ampersand in qjackctl's call. If you call jack directly, put the ampersand at the end of it's call line.
-Now include the following lines after the line that calls jack:
--/usr/bin/sleep 5 -/bin/bash -c "/usr/bin/a2jmidid -e" & --
All you have to do now is use your new script to call jack.
+
+ a2jmidid is an application that bridges between the system
+ MIDI ports and
+
+ First you should make sure that there is no ALSA sequencer support enabled + in JACK. To do that open QJackCtl's Setup window. +
+
+ Set Settings > MIDI Driver to none.
+ Then uncheck the Misc > Enable ALSA Sequencer
+ support option.
+ Now it's time to restart your jack server before going on.
+
+ First, check whether a2jmidid is already installed in your system. After + starting your JACK server, go to the command line and type +
+a2jmidid -e ++ If a2jmidid does not exist, install it with the software manager of your + Linux distribution and try again. +
+ ++ After starting a2jmidid, your control surface MIDI ports should appear in + qjackctl under Connections > MIDI > a2j. +
++ You can now add a2jmidid -e as an "after start-up" script in the Setup > Options tab of QJackCtl, so that it is + started automatically whenever you start JACK. +
diff --git a/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html b/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html index b84805a..614146b 100644 --- a/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html +++ b/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html @@ -4,87 +4,83 @@ title: Using More Than One Audio Device ---- Ardour will only use a single interface. If you want to use more - than one interface you have two choices: + Ardour will only ever deal with a single audio device. If you + want to use more than one, you have two choices:
--Ardour is fundamentally designed to be a component in a -pro-audio/music creation environment and standard operating practice -for such setups involves using only a single digital sample "clock" -(something counting off the time between audio samples). This means -that trying to use multiple independent soundcards is problematic, -because each soundcard has its own sample clock, running independently -from the others. Over time, these different clocks drift out of sync -with each other, and cause glitches in the audio. You can't stop this -drift, although in some cases the effects may be insignificant enough -that some people might not care about them.
- + Ardour is fundamentally designed to be a component in a + pro-audio/music creation environment. Standard operating practice + for such setups involves using only a single digital sample + clock (something counting off the time between audio samples). + This means that trying to use multiple independent soundcards is + problematic, because each soundcard has its own sample clock, running + independently from the others. Over time, these different clocks drift + out of sync with each other, which causes glitches in the audio. You + cannot stop this drift, although in some cases the effects may be + insignificant enough that some people might not care about them. +Thus in an ideal world you should not use multiple independent soundcards but instead use a single device with a single clock and all the inputs, outputs and other features that you need.
-- Of course, a lot of people don't live in an ideal world, and believe that software should make up for this. + Of course, a lot of people don't live in an ideal world, and believe + that software should make up for this.
-Aggregate devices provide a method to use multiple soundcards as -a single device. For example, you can "aggregate" 2 different -8-channel devices so that you can record 16 channels into Ardour. + In CoreAudio, aggregate devices provide a method to use + multiple soundcards as a single device. For example, you can + aggregate two 8-channel devices so that you can record 16 channels + into Ardour.
- +
If you are using a single typical 3rd party
audio interface (such as those from Apogee, RME, Presonus, and many
others), OR you are using JackPilot or a similar
- application to start JACK, you do not need to worry about this.
+ application to start JACK, you do not need to worry about this.
+ You will need to set up an aggregate device only if either
+ of the following conditions are true:
You will need to set up an aggregate device ONLY if either of the following conditions are true:
- -In the case of your builtin audio device, you will need to create +
+ In the case of your builtin audio device, you will need to create an aggregate device that combines "Builtin Input" and "Builtin Output" into one device.
- -The precise instructions for creating an "aggregate device" on OS X have varied from one released to another.
- ++ The precise instructions for creating an "aggregate device" on OS X + have varied from one released to another. +
Please see the instructions at http://jackaudio.org/faq diff --git a/_manual/03_setting-up-your-system/08_platform-specifics.html b/_manual/03_setting-up-your-system/08_platform-specifics.html index 3cb4b04..ef6b154 100644 --- a/_manual/03_setting-up-your-system/08_platform-specifics.html +++ b/_manual/03_setting-up-your-system/08_platform-specifics.html @@ -4,7 +4,6 @@ title: Platform Specifics ---
This section of the manual collects together the collective wisdom of the user community regarding details of using Ardour on various diff --git a/_manual/03_setting-up-your-system/08_platform-specifics/01_ubuntu-linux.html b/_manual/03_setting-up-your-system/08_platform-specifics/01_ubuntu-linux.html index 1ba1cf8..d150927 100644 --- a/_manual/03_setting-up-your-system/08_platform-specifics/01_ubuntu-linux.html +++ b/_manual/03_setting-up-your-system/08_platform-specifics/01_ubuntu-linux.html @@ -4,7 +4,7 @@ title: Ubuntu Linux ---
- Ubuntu Linux is the most popular variety of Linux in use on desktop + Ubuntu Linux is the most popular variety of Linux in use on desktop and laptop systems. It has the backing of a for-profit corporation (Canonical Inc.), a defined philosophy and a huge and worldwide user base. As a result, it is a common platform for people @@ -13,7 +13,6 @@ title: Ubuntu Linux
Currently, installing pro audio applications on vanilla Ubuntu requires some configuration, in order for the user to gain realtime privilege @@ -27,6 +26,7 @@ title: Ubuntu Linux
There may be unintended differences, and even bugs in Ubuntu native packages, as a result of a different building method. For this reason, Ardour developers highly recommend you to install the official @@ -34,14 +34,13 @@ title: Ubuntu Linux href="http://ardour.org/download">ardour.org, as Ubuntu native packages are not supported in official Ardour forums or other support channels. +
- Like many distributions, Ubuntu has decide to use PulseAudio as the + Like many distributions, Ubuntu has decided to use PulseAudio as the default audio system. PulseAudio is a rich and capable system that provides excellent services for typical users of Linux on the desktop. However, it is not capable of the type of performance that @@ -68,74 +67,70 @@ title: Ubuntu Linux another message, and PulseAudio can once again use the soundcard directly.
-The specific issues known at this time for all flavors of Ubuntu 12.04 and 12.10 are:
-
These bugs do not affect the upcoming 13.04 release, and earlier releases (12.04 and 12.10) are in the process of being fixed.
-To function as intended, JACK needs to run with access to two - operating system facilities called "realtime scheduling" and "memory - locking". This means that you, the user who starts JACK, must be + operating system facilities called realtime scheduling and + memory locking. This means that you, the user who starts JACK, must be allowed access to these facilities. By default, Ubuntu does create a - user group that has this permission but ... it does not put new + user group that has this permission but — it does not put new users into this group by default. Read more about why here. Consequently, you will not have permission to run JACK in the way you should.
-- A message like "Cannot lock down memory" in the output from JACK as - it starts up. This output may be "hidden" in the Messages window of + A message like Cannot lock down memory in the output from JACK as + it starts up. This output may be hidden in the Messages window of QJackctrl (aka JACK Control), so you should check there.
-
Make sure the file /etc/security/limits.d/audio.conf exists. If it is
named /etc/security/limits.d/audio.conf.disabled, rename it to the former.
- Run the command sudo usermod -a -G
- audio YOUR-LOGIN-NAME. Then logout and login again.
- On Ubuntu Studio the user is a member of audio group by default, but not
- on other official flavors.
+ Run the command
Given the difficulties in supporting Ubuntu and the limited time/resources of the Ardour team, the Ubuntu Studio Project has requested that issues and bug reports related to Ubuntu, Ubuntu Studio and other derivitives be directed to them.
+ Then log out and log in again. On Ubuntu Studio the user is a member of audio + group by default, but not on other official flavors. +
+ ++ Given the difficulties in supporting Ubuntu and the limited time/resources + of the Ardour team, the Ubuntu Studio Project has requested that + issues and bug reports related to Ubuntu, Ubuntu Studio and other + derivitives be directed to them. +
- VBAP is short for Vector-base Amplitude Panning, - a versatile and - straightforward method to pan a source around on an arbitrary number - of speakers on a horizontal polygon or a 3D surface, even if the speaker - layout is highly irregular. + VBAP + is a versatile and straightforward method to pan a source around over an + arbitrary number of speakers on a horizontal polygon or a 3D surface, + even if the speaker layout is highly irregular.
- A horizontal VBAP panner has one parameter, the azimuth - angle. A 3D panner offers an additional elevation - angle control. + A horizontal VBAP panner has one parameter, the azimuth + angle. A full-sphere panner offers an additional + elevation angle control.
More elaborate implementations of VBAP also include a diff --git a/source/css/app.css b/source/css/app.css index e5c5f6e..b0786af 100644 --- a/source/css/app.css +++ b/source/css/app.css @@ -271,6 +271,32 @@ kbd { white-space:nowrap; } +kbd.input,kbd.lincmd,kbd.maccmd,kbd.wincmd { + font-family:mono; + border-width:0; +} + +kbd.lincmd,kbd.maccmd,kbd.wincmd { + display:block; + width:100%; + margin-bottom:1ex; +} + +kbd.lincmd:before { + content: 'user@linux:~ '; + color:#999999; +} + +kbd.maccmd:before { + content: 'MacBook:~/Desktop User\$ '; + color:#999999; +} + +kbd.wincmd:before { + content: 'C:\\Users\\myAccount> '; + color:#999999; +} + kbd.mouse { -moz-border-radius:10px; border-radius:10px; @@ -308,7 +334,7 @@ kbd.fader, kbd.knob, kbd.button { } kbd.fader { - border-width:2px 2px 4px 4px + border-width: 1px 1px 9px 9px; } kbd.knob { @@ -320,6 +346,24 @@ kbd.knob { kbd.button { -moz-border-radius:8px; border-radius:8px; + border-width: 1px 1px 3px 3px; +} + +samp { + font-family:mono; + font-style:italic; + color:#333333; + background-color:transparent; + margin-left: 1em; + margin-right: 1em; +} + +samp:before { + content:"\BB"; +} + +samp:after { + content:"\AB"; } #content td {