GitHub for Music: Setting up a DAW Session for GitHub
 |
| GitHub Octocat Illustrations by Tom Ray |
For about 7 years, we've been using GitHub to collaborate on full DAW files remotely, and I've been going over how we do it.
In the last post, I explained what Git does and the version control basics, which is about how GitHub is capable of sharing these full DAW sessions between musicians.
Now I want to explain how we set up the DAW session for GitHub.
Setting up a recording session for GitHub
So now, let's get into actually setting up a DAW project for GitHub.
Start by talking about getting a GitHub repository ready for the DAW project that we're gonna be recording on.
What is a Repository?
It's kind of a project folder where changes and history are stored and tracked.
On the GitHub website, this folder is laid out like a webpage showing the structure inside. But when you download the repository, it is saved as a folder on your computer, and that downloaded folder is what will sync this session to the repository on GitHub.com.
(Related post: GitHub For Music: What Git Does - Version Control Basics)
You need to have the same DAW setup as your collaborators
The important thing to remember is that everybody you're collaborating with should have the same DAW setup.
That means the same version of the software that you're using, the same plugins, the same everything. Otherwise, if somebody has, for instance, a newer version of the DAW program, then when they download the repository and open the session, it's going to update the session to that newer version, and people on the older version of the software won't be able to open it any longer.
And a similar example using plugins, if you have a plugin that you're using that they don't, then it's gonna give them an error that there's a plugin missing.
That is why we use Ubuntu Studio, which is actually a Linux operating system, that's a production suite for artists and musicians. It comes pre-installed with all the programs and plug-ins we use, like the open-source DAW Ardour. So when the rest of the band members use the repository, they have all of the same software and plugins that I do.
Create a GitHub Repository and "clone" it
To create a repository for your recording session, go to GitHub.com and click on the "New" button to create a new repository and then name it. If you don't have a GitHub account, you'll need to create one.
Now we need to clone this repository to our computer. Cloning a repository is essentially downloading the GitHub repository from the website and saving it as a folder on your desktop.
GitHub Desktop App
The easiest way to clone the repository is to use the GitHub desktop app. The app will be a program you download to your computer that will connect to the repository and sync your changes to GitHub.com.
So once GitHub Desktop has been connected to our GitHub account and the repository has been "cloned" to the computer, we are going to continue using GitHub Desktop to manage the uploading and downloading of the changes we're gonna make in this repository.
Create a DAW session in the downloaded/cloned GitHub folder
Now that I've cloned this repository locally onto my desktop, I can then create a brand new DAW session in this folder and start recording.
Let's say I recorded a drum part, and now I want to share it with the guitar player so he can add guitar to the track. But so far, the recording still only exists in the GitHub folder on my desktop. Nothing has been shared to the online repository yet because syncing to GitHub is not automatic; it's controlled by you.
More later...
So next time, I will explain how I upload these DAW session changes to the GitHub.com repository that I will be sharing with the guitar player.
Download My GitHub For Music Process
GitHub for Music Collaboration With A Full DAW Is Possible... If You Use It Incorrectly!
This document explains my full method on how to use GitHub for collaborating on music projects with full DAW sessions.
The document outlines an unconventional way to use GitHub for music collaboration.
