Skip to main content

Self-Producing an EP Pt.1: Demos

To jump right in, I started working with a few friends on an EP for our band. Now that it's coming to a close, I thought it might be a useful for me to document the process involved from the beginning, and useful information I've gathered along the way to help me get through things quicker and better on my next attempt at something like this.

At the point where I started piecing a few demo tracks together, I'd been using Reaper for a while and I was using EZMix and EZDrummer as my primary plugin set while making a few acoustic tracks. I subscribed to and and for a few minutes a day would have a dig through for whatever information was new.

This was pretty straight forward, I sat and tried out a few riff ideas (being primarily a guitarist), when something sounded good I'd record it into Reaper and apply a guitar preset to it, of which there are some great ones that just sound good straight away. I'd then track it again and pan hard (100% left for one and 100% right for the other) and then do some fixing on timing issues quickly.
Looping the riff, EZDrummer would be the next stop to find and tweak a drum loop that fit and drop it into the track directly. I preferred this to using the timeline in EZDrummer so I could just grab entire sections and copy/paste/move/delete easily without having to open it up and fiddle.
Somewhere in the middle of the guitar and drums getting put down I'd add one of the EZMix mastering presets to the master FX in Reaper. Something stylistically approximate. Then it's a case of grabbing the bass guitar and putting some bass down too.

To start putting a song together, I'd use the project as a bit of a sketchbook, and spend a few hours listening to what's there and just move along the timeline a bit and put some more ideas in or variations of previous ones until it seems like all the pieces of something more complete are there. This can be a bit trickier if there are time signature or tempo changes but it just takes a bit more time.

Things that seemed to be important factors for me:
  • Getting as much down for a demo as possible at once made for more consistent demos. A couple of them I just sat down at 1pm on a Sunday and worked for a 3-4 hours and got the full thing demo'd ready for presenting.
  • Making sure there were presets effects chains that could be dropped straight onto instruments to get something that sounded good right away, instead of getting caught up fiddling. There are many free plugins for guitars/drums out there that sound good so it doesn't really matter what you use, as long as you can just apply a 'distorted guitar' preset and be happy and carry on. It also means that when you've finished the demo it just sounds good already and doesn't need any real mixing before you share it.
  • Not second guessing things. It's easy to get stuck in "maybe it doesn't fit", etc. just run with what's there, you can always save another version. Get version 1 to done.
  • Having a Reaper template ready to go, with tracks for all the instruments with the correct VSTs already loaded and a click track etc. is the way to go here to maximise the time spent writing and not fiddling with software. 
With other commitments it took me a month to get all 5 demos down into a form where I'd shared them and we'd started talking about them. There were no vocals present at this point as there was still some indecision about what we would do on that front. In the future I'd get something down as a starting point for development.


Popular posts from this blog

Constructing a Trie in F#

This post might get a bit more context next week, but essentially, in continuation of looking at data structures in F# and C# I picked prefix trees (tries) as the next step. A trie is similar to a BST except the search is cumulative. A simple example would be building a spellchecker. The spell checker can use the structure to see if a word exists quickly and efficiently.

It works by creating a new node for each part of the word, using existing nodes if they're already in place. You can see in this diagram an example structure after an insertion of several words.

In the above diagram the words ANT, AND, BATS have been added into the data structure. You'll notice that the word BATS can also be the word BAT and that becomes a part of the structure, setting a value at each node to state if this is a place that a word terminates.

1 2 3 4// Node type for storing a trie. typeTrieNode=|Nodeofchar*TrieNodelist*bool|RootofTrieNodelist
I defined the type to have 2 options. The root node,…

A Docker Experiment

Containers are a topic that have been rising in occurrence for me, for the last year or so. From using them as part of the architecture at work or for various pet projects friends have been working on. I figured it was time to experiment myself and get to grips with what people have been talking about. It seemed like a good idea to find some introductory material that would give me an overview of its uses without delving too far into the details so I could see what it actually was, so I found a PluralSight course about Docker, specifically “Docker and Containers:The Big Picture”. This gave a nice overview of what Docker is, and more importantly what it was trying to achieve and how to use it. With a bit more of an understanding, I wanted to use it for something, preferably something familiar. I decided to try setting up ElasticSearch and Kibana containers, where Kibana would visualize the ElasticSearch data. I used bits of this article along the way as a guide, if you'd prefer a more…

Self-Producing an EP Pt.5: Mixing

After some discussion we opted to mix it ourselves for a few reasons.

It's our first EP, it's not going to be heard by a huge amount of people and while it's important that it sounds good, it's expensive to get done properly and we might be able to manage 'good enough' on our own with a lot of work.Mixing as an online service seems to be the main way to go for small/starting out bands and that seems too creatively detached. There are many stories floating around of people who've sent things off for mixing and the mixer has a much different idea of how it sounds.
Maybe it's not the best choice, but it seemed an acceptable risk that we would at least attempt to have it 'look' how we want and it be a bit wonky than potentially end up with something we're not happy with in a different way. The benefit would have been being able to just ship the stems off and make it someone else's problem instead of weeks of being unsure while swimming in the…