+ This section of the manual collects together the collective wisdom + of the user community regarding details of using Ardour on various + specific platforms +
+ +{% children %} 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 new file mode 100644 index 00000000..d1735b7e --- /dev/null +++ b/_manual/03_setting-up-your-system/08_platform-specifics/01_ubuntu-linux.html @@ -0,0 +1,183 @@ +--- +layout: default +title: Ubuntu Linux +--- + ++ 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 + who want to use Ardour and other tools for music creation and + pro-audio work. +
++ Unfortunately, Ubuntu has repeatedly caused major headaches for + people who want to use Ardour. These problems have arisen from a + combination of two basic issues: + +
+ If you are really committed to using Ubuntu for pro-audio or music + creation work, you should .... +
+
+ If you not yet committed to using Ubuntu for pro-audio or music + creation work, you should probably consider using a different + distribution that has a demonstrated history of not making life for + users like you more complex than it needs to be. In particular you + might want to consider a distribution such + as AVLinux + or Dreamstudio + that is specifically focused on media creation work. +
+ ++ It is not possible to know whether the current package of Ardour + released by Ubuntu has been correctly built or not. Ubuntu has a + history of making packaging errors that lead to crashes, missing + functionality and odd behaviour that is not present in the + ready-to-run version of the program that you can get from ardour.org (or in the packages + released by other distributions) +
++ Ardour starts up and basically runs, but you encounter subtle + problems (for example, with plugin GUIs or with export, or with the + use of certain specific plugins), or are missing functionality, or + run into crashes. +
++ Download the ready-to-run version + from ardour.org. Ardour's + lead developer (and many of the most active members of our user + community) will not provide support for, and will not investigate + bugs reported for, Ubuntu's own packages of Ardour. The ardour.org + packages install along side your distribution versions, and do not + interfere or interact in anyway other than sharing your own personal + Ardour settings and configuration choices. +
++ Like many distributions, Ubuntu has decide 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 + tools like Ardour require and in particular does not offer the + possibility of sending audio between applications that can makes the + Linux audio environment a very interesting one. +
++ This would not a problem if it were not for the fact that JACK will + not run correctly (if at all) if it needs to use the same + soundcard/audio interface that PulseAudio is using. And since on + Ubuntu, PulseAudio is configured by default to always use the + (typically single) audio interface on your computer, this is a bit + of a problem. +
++ The developers of JACK and PulseAudio got together in 2009 and + agreed upon a mechanism by which PulseAudio and JACK could cooperate + in their use of a single soundcard. Whether or not PulseAudio is running by + default, when JACK starts up it sends out a request to use the + soundcard. If PulseAudio is running, it will give up its use of the + soundcard to allow JACK to take over (and can optionally be told to + route its own audio through JACK). When JACK finishes, it sends out + another message, and PulseAudio can once again use the soundcard + directly. +
++ This relatively simple system ought to be the basis for excellent + cooperation between PulseAudio and JACK. Unfortunately, it relies on + everything being correctly configured for it to work, and Ubuntu + have repeatedly failed to get this configuration correct. +
++ The specific issues known at this time (spring 2013) are: +
+
+ 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 + allowed access to these facilities. By default, Ubuntu does create a + user group that has this permission but ... it does not put new + users into this group by default. 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 + QJackctrl (aka JACK Control), so you should check there. +
+
+ Run the command sudo usermod -a -G
+ audio YOUR-LOGIN-NAME. Then logout and login again.
+
Ardour does not come with any built-in signal processors of its own (other than volume faders) and it also generally doesn't ship with any -plugins. They are written by 3rd parties, though we do provide some +plugins. They are written by 3rd parties, though we do provide some information on how to get them..
diff --git a/_manual/11_working-with-plugins/06_getting_plugins.html b/_manual/11_working-with-plugins/06_getting-plugins.html similarity index 100% rename from _manual/11_working-with-plugins/06_getting_plugins.html rename to _manual/11_working-with-plugins/06_getting-plugins.html