Changes

:One *perceived* problem that a typical "end-user" would face is having to '''manually connect''' (patch) various Devices (like a keyboard), with various keyboard emulators generally assumed (like '''Qsynth''' and '''Bristol''' organincorrect). But it perception of recording in Linux is important to realise that these "graphical applications" are just convenient "front-ends" or user-friendly graphical representations the complexity of Linux commandsadvanced recording.

Since they are Linux commands:In order to perform advanced recording with multi-track applications, several applications required to be launched. :Here would be an example of some of these commandapplications: ::*Jack Audio Server;;*'''Hydrogen Drum Machine'''::*'''Qsynth Synthesizer/Sampler'''::*'''Bristol Organ'''::*'''Rakarrack effects processor''' (Note: vocals, guitar, bass guitar can be recorded by connecting to launch the USB recording device, for example the Tascam US-122, and selecting the recording device in the Audacity Preferences dialog box as "system"...) At the heart of these applications is the Jack audio server. It acts like a "conductor" that controls and make patches (connectionsi.e. connects) instruments from various applications together. Other applications accomplish this task by using features such as VST or VSTi (which Linux supports that technology). In order to simplify things for the Westminster Computer Lab users, and simply be added to a file (called a '''program (Bash shell script) has been created to automatically launch and connect these programs together''' (in a very user-friendly manner), so individuals can concentrate on just recording their music. The user simply logs into the Teacher account, and run like program (either as an desktop double clicks on the '''Recording Studio''' icon), or a start-up program from boot-up.