'''''Break the misconception that once you have a home recording studio, you can do it all yourself.''' I perform in a band, and benefit from the expertise of my the other group members...

The problem with collaborating online with Ardour is that the files that are generated when you record an auditory product using Ardour are very LARGE. For example, if you decide to create a '''zipped tarball ''' (a method to build a single file from a group of directories/files and then compress or "zip" “zip” that file ) can balloon to save space) a simple 5 minute song with just percussion and bass guitar could take up somewhere between '''90 Mb MB to 120 Mb MB of hard disk space'''for a simple 4-5 minute song... Imagine posting that file on the cloud, or making that file available on a distribution server!Then just consider the pain of compressing and decompressing those files - there must be an easier method...

If you are not concerned with more than one person '''<u>notsimultaneously editing</u>''' concerned with collaborating simultaneously on a projectthe same session, there is a python script (program) that will will allow the user you to visually easily share ongoing Ardour projects your sessions for collaboration with editing by other online users of Ardour. The name of this program application is called '''session-exchange''', and it has been around for several years...

The advantage of '''session-exchange ''' is that the user can allow for uploading and downloading of files to other usersall collaborators of a session, and only have the musicians work on the most recent edits of the auditory product (i.e. "songs"). When you create a song in Ardour, you are required to either '''create a session''', or '''open an existing session'''. This allows ardour to create subdirectories to store all audio data into a concise location on your computer system. Ardour uses the term '''snapshot''' to relate to a '''new session''' file that is generated (i.e. not affecting the original session) that simply stores the '''current state of the edited session'''. No doubtTherefore, all of the original files are shared with the other users, but as other users add their own contributions to the song, then only snapshots (and the snapshot needs related data updates) need to be shared, thus saving space and transmission time. This is an efficient method of collaborating a song via Ardour sessions over the Internet...

 '''An analogy:''' This may be an oversimplification, but relate it to how the '''vi text editor ''' works: there is a '''swap file''' (editing transaction) file ''' and the '''original file'''. Only upon saving the editing session is the original file updated with the newer information... information… No doubt, the '''the swap file is smaller than the actual file, and thus easier to transfer between computer systems'''. Also, the '''the swap file is useful for backup purposes''' (eg. in case of accidental disconnection from your remote editing session)… The only difference from this vi text editor comparison is that the snapshot informs the session exchange program which other auditory files are required to be downloaded in addition to the snapshot file...

The easiest method to install session-exchange is to download the source from '''Ardour SVN site'''. '''SVN''' stands for''' Apache Subversion''' which is a method to make it easier for programmers to collaborate together on complex programming projects. This basically the online version of '''RCS''' which stands for '''Revision Control System'''.

<li>'''Open a shell terminal window''', and login as root or super-user (eg. '''sudo su''' )</li> <li>'''Switch to the Ardour Download site''', copy and paste the command (listed in the Public read-only SVN access sectionunder '''tools''' and '''look for file called session_exchange.py''') into your shell window:<br /><br />'''svn co http://subversion.ardour.org/svn/ardour2/branches/2.0-ongoing''' <br /><br />(It is recommended to use the command stated on the site, since the version may change over time...)</li>

<li>In the Add Collaborator dialog box, '''create a username''', and then '''enter the IP address for that user's computer system'''.<br /><br />In order to obtain the IP address for a computer system, you can open a shell terminal window and issue the command: '''ifconfig'''<br />(look for the value labelled '''inet addr''').<br /><br />('''Note: ''' accept the default port number)... You can create other users for sharing as well...<br /><br />'''Also note:''' If your computer is connected via a router, you can configure your router to "route" the port number to a specific IP address to your networked machine. Your router's user manual should provide information how to do this. This is NOT a very complicated operation, and is usually located under "Advanced Settings"...<br /><br /></li>

Note #In order to deal with this challenge, Ninjam allows user to collaborate in "Fake-Time".''' A common beat track is used, which allows users to start recording their measure, then other user's will start playing their measures, etc.  The Ninjam in a Nutshell" guide then states:  ''"The end result is that nobody hears the exact same jam. It’s a bit contrary to classical jamming and requires everyone to adhere to a common tempo, but once you get used to it many find that it’s compatible with most styles of jamming and the strict tempo enhances the experience."''  '''There are 2separate applications that run for Ninjam:''' T  <ul> <li>'''Ninjam Client:'''he An application that allows the user to connect to a Ninjam Server (nicknamed a "Ninjam Farm"), to play with other users MUST create . For example, here is a link to various Ninjam farms:<br /><br />[http://ninjam.com/jamfarm/index.php http://ninjam.com/jamfarm/index.php]<br /><br />Note: You should use the sessions using ones for testing purposes only, and NOT the exact spelling or BPM contest servers if you are just testing-out your session namesconnection...<br /><br /></li> <li>'''Ninjam Server: otherwise''' An application that allows the user to run a Ninjam server to '''create your own Ninjam Farm''' (private area) for user jam sessions...<br /><br /></li></ul> == Installing Ninjam Client (via wine) == Although there is a Linux version for Ninjam, I can't seem to get it installed on my Ubuntu Studio 10.04 64-bit system... I'm not certain this is the BEST method for running Ninjam client in Linux, I did have success in running the Windows version of Ninjam client via wine.Here is how I was able to do it..  '''STEPS TO INSTALL NINJAM CLIENT (VIA WINE):'''  <ol> <li>Make certain that you will have already installed the '''wine application'''. If you are not certain, refer to this link to learn how to install applications (like wine) via the Synaptic Package Manager: [ [[Install_Applications_in_Ubuntu]] ]<br /><br /> </li>  <li>'''Go to the Ninjam website'''.<br /><br />Here is a link to the Ninjam Download Page: [ [http://ninjam.com/download.php http://ninjam.com/download.php] ]<br /><br /> <li>'''ATTENTION:''' In my situation, I was not be able to exchange use wine to install the Ninjam installer, application, so I actually '''downloaded and installed the Windows version of Ninjam on a Windows system'''. I copied the entire NINJAM directory into a USB stick, and then copied over to my Linux system.<br /><br /></li> <li>'''Open a shell terminal window, and run wine to run your Windows (i.e. Ninjam) application'''<br /><br />For example, assume that I copied to the NINJAM directory and its contents to my home directory (/home/msaul). Then I ran the wine application as follows:<br /><br />'''wine /home/msaul/NINJAM/ninjam.exe'''<br /><br /></li> <li>'''After a <u>while</u>, the Ninjam Client application window should appear...'''<br /><br /></li> <li>In the future, '''you can create a shortcut''' to run this wine application for Ninjam client for convenience...</li></ol>   == Configuring Ninjam Client for Jack (via wineasio) == If you wish, you can connect to a session to listen to a session in progress. The Ninjam Farm page (refer to link above) provides updates (if you refresh your web-browser) of users currently participating in various test jam sessions.  On the other hand, if you wish to participate in the Jam Sessions with your own instruments, you must setup your computer system to do this. This tutorial will assume that we are running Jack Audio server. In my situation, I am running Jack, Qsynth, and Bristol Organ via my Tascam US122 USB device to record MIDI data from my old Yamaha keyboard... 

To STEPS TO CONFIGURE NINJAM CLIENT WITH WINEASIO: [[Image:ninjam1.png|thumb|150px|right ]]<ol> <li>'''Start the Jack Audio server'''. If you are not certain how to do this, refer to one of my other tutorials: [ [[Quick & Simple - Setting up Jack Server and Q-synth]] ]</li> <li>'''Open a shell terminal window''', and use wine to start the Ninjam client. Your situation will be different than the following example, but let's assume that Ninjam client has been copied over to my home directory, and my home directory pathname is /home/msaul. Under that assumption, the command to startup the Ninjam client would be:<br /><br />'''wine /home/msaul/NINJAM/ninjam.exe'''<br /><br /></li> <li>When the Ninjam Client application window appears, click on the '''Options''' menu, then click '''Audio Configuration'''.[[Image:ninjam5.png|thumb|200px|right ]]</li> <li>The NINJAM audio I/O configuration dialog box will appear.</li> <li>Set the Input/Output System to '''ASIO'''.</li> <li>If all is well, you should see the '''ASIO Driver display Wine ASIO Driver''', and the Input Range and Output Range values should appear in the text boxes...</li> <li>You can now click on the '''ASIO Configuration''' button to display the Jack Audio Connection dialog box.<br /><br />You will not see anything until you actually connect to a Ninjam session, then the NINJAM SESSION will appear in the connections dialog box...</li> <li>'''Switch back to the NINJAM audio I/O configuration dialog box''', click '''OK''' to exit ...</li> <li>'''Switch to the Ninjam Client window'''.</li> <li>Click on the '''file''' menu, then select '''Connect'''.<table align="right"> <tr> <td>[[Image:ninjam2.png|thumb|300px|right ]]</td> <td>[[Image:ninjam3.png|thumb|300px|right ]]</td> </tr></table></li> <li>The NINJAM Connection Configuration dialog box will appear.</li> <li>Enter a host number to connect (preferably '''test.ninjam.com:2600''' or '''test.ninjam.com:2601''') for testing purposes.</li> <li>Click the Connect button, and click the '''"I agree"''' checkbox in the NINJAM Server License Agreement, and then click the '''Accept''' button.</li> <li>'''Switch to the Jack Connections dialog box'''. Select the '''ALSA''' tab, and connect the device (In my situation, '''Tascam US-122''') to '''Bristol (B3) Organ'''.</li> <li>Then select the '''AUDIO''' tab. You should now see '''ASIO_NINJAM'''. Make the necessary connections. You should now be able to perform in the session...</li></ol>  '''NOTE:''' When you are performing, you are creating on ogg file of your performance, which is saved on your computer! This is useful, since '''you may want to test to see if you are recording in the session''', although there may not be other members present. You can always listen to the recording afterwards to confirm you are being heard. '''WARNING: Due to the latency of connections, you need to be completedpatient and listen to the ENTIRE recording, before assuming that you did not record!''' FYI... 

= Using '''= Installing and Running Ninjam''' Server ==