Difference between revisions of "How to Collaborate On-line"

From CDOT Wiki
Jump to: navigation, search
Line 19: Line 19:
  
  
'''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...
+
'''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... No doubt, the swap file is smaller than the actual file, and thus easier to transfer between computer systems. Also, this swap file is useful for backup purposes (eg. in case of accidental disconnection from your remote editing session)...
  
  

Revision as of 13:29, 8 July 2010

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 other group members...

Like the saying goes, "The result is greater than the sum of all of the parts"...

There are several methods to collaborate online with other users using Ardour and Ninjam...


Using Ardour session-exchange

The problem with collaborating online with Ardour is that the files that are generated when you record an auditory product 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" that file to save space) a simple 5 minute song with just percussion and bass guitar could take up somewhere between 90 Mb to 120 Mb of hard disk space... Imagine posting that file on the cloud, or making available on a distribution server!


If you are not concerned with collaborating simultaneously on a project, there is a python script (program) that will will allow the user to visually share ongoing Ardour projects for collaboration with other online users of Ardour. The name of this program 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 users, 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 doubt, all of the original files are shared with the other users, but as other users add their own contributions to the song, then only the snapshot needs to be shared, thus saving space and transmission time. This is an efficient method of collaborating a song via 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... No doubt, the swap file is smaller than the actual file, and thus easier to transfer between computer systems. Also, this swap file is useful for backup purposes (eg. in case of accidental disconnection from your remote editing session)...



Using Ninjam

To be completed...