Open main menu

CDOT Wiki β

Changes

Performing Live with Jack,Qsynth, and Bristol Organ

170 bytes added, 18:56, 20 November 2011
no edit summary
:* Ran '''Synaptic Package Manager''' (from Admin), and installed '''Ubuntu Studio Desktop''' (I selected ALL packages associated with Ubuntu Studio).
:* Followed '''instructions to make my Tascam US122 device work''' with my netbook: [ [https://help.ubuntu.com/community/TASCAM_US-122 https://help.ubuntu.com/community/TASCAM_US-122] ]<br /><br />
* I "Tweaked" the appearance of my Gnome Desktop like running the '''Avant Window Navigator (docking panel appearance like Mac OSX)''', and '''removed the "old-style" gnome-panels'''. Here is a resource that I created to help: [ [[Replacing Panels with Docking Station (awn)]] ][[Image:awn-pic.png|thumb|right|550px|<b>Avant Window Navigator</b> gives a Mac OSX '''docking station''' appearance<br />(A welcome change from traditional panels). ] ]<br /><br />
*'''NOTE:''' I had trouble when displaying my net-book on the data display in class. '''Every time I pressed a key, the screen would go blue and return display to my net-book.''' I thought it was attributed to Ubuntu, but all I needed to do was update (flash) my '''BIOS from v3010 to v3012'''. Refer to the section below labelled:<br />'''Steps to Enhance CPU performance (Acer AspireOne a751h)''' for a full set of procedures to solve this problem. It seems to have also solved the '''hibernation problem''', <u>and</u> also the problem of '''not displaying Python applets on my Avant Window Navigator docking tray...!''' <br /><br />
* Now that you have Ubuntu Studio on your machine, here are some guides that I have written to help you get started<br /> (This is assuming that you are using the ''Tascam US122 usb interface'', although that is NOT necessary if you have a ''USB keyboard''):
[[Image:netbook2.png|thumb|right|400px|<b>Ubuntu Studio Desktop</b> with Applications (<b>Jack Audio Server</b>, <b>Bristol Hammond B3 Emulator</b>, and <b>Qsynth</b>) Automatically Launched and Connected or "patched" via a <b>Bash Shell script</b>]]
The organ emulator called '''Bristol Organ''' can simply be run via the '''startBristol''' command ''(after the Jack audio server has been started)''. To simplify the process of starting jack audio server, launching and making input/output connections for both '''Qsynth''' and several '''Bristol Organ''' emulations, it is easier to place commands into a '''Bash shell script''' and run shell script as a program! ''Please see next section for an example of how I did this...''
 
 
=== "Putting it All Together" with a Bash Shell Script ===
 
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 (like '''Qsynth''' and '''Bristol''' organ). But it is important to realise that these "graphical applications" are just convenient "front-ends" or user-friendly graphical representations of Linux commands.
 
Since they are Linux commands, these command, to launch and make patches (connections), and simply be added to a file (called a ''shell script''), and run like program (either as an desktop icon), or a start-up program from boot-up.
 
'''For reference, here is a link to my Bash Shell script:''' [ [http://matrix.senecac.on.ca/~murray.saul/netbook.bash.txt txt] ]
 
For additional reference, '''here is a link that explains how above shell script works:''' [ coming soon ]
 
=== YouTube Tutorials ===
LMMS Synth: [ [http://www.youtube.com/watch?v=boRmY9jH7fs http://www.youtube.com/watch?v=boRmY9jH7fs] ]
 
=== "Putting it All Together" with a Bash Shell Script ===
 
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 (like '''Qsynth''' and '''Bristol''' organ). But it is important to realise that these "graphical applications" are just convenient "front-ends" or user-friendly graphical representations of Linux commands.
 
Since they are Linux commands, these command, to launch and make patches (connections), and simply be added to a file (called a ''shell script''), and run like program (either as an desktop icon), or a start-up program from boot-up.
 
'''For reference, here is a link to my Bash Shell script:''' [ [http://matrix.senecac.on.ca/~murray.saul/netbook.bash.txt txt] ]
 
For additional reference, '''here is a link that explains how above shell script works:''' [ coming soon ]
=== Using Ubuntu Studio for Live Performances ===
I have see some misinformation regarding the use of sound-fonts with Qsynth. You can add in a lot of sound-fonts with Qsynth, and then assign them (either using a particular sound, or incorporating "sound banks") to midi channels. I am currently have assigned instruments to 10 midi channels (2 have been reserved for my B3 Organ. In addition, you can save these midi assigns as different "preset names" to be saved and loaded as needed during performance or practice.
In order to assign MIDI channels in Qsynth, when you click the '''Channels''' button, you will see the '''Channels dialog box''' appear. Notice that this dialog box allows for a total of 16 midi channels (this is more than I require for a typical practice or performance). If you require more, you can save different midi instrument assignments to various profiles (perhaps to be loaded between your sets).
Steps to Assignment Instruments:
[ [http://www.m-audio.com/images/global/manuals/050505-KSSeries_UG_EN01.pdf http://www.m-audio.com/images/global/manuals/050505-KSSeries_UG_EN01.pdf] ]
 
= Sound Font Editing in Linux =
13,420
edits