Share your music and get feedback.
Den Haag, Netherlands
About me
Sound Design and Composition for linear and interactive media @ link

I like making music and virtual instruments based on acoustic sources. I do dj sets and live stuff.
link - ThorLtd
link - Sound Design - portfolio/CV
My Gear
PC, Komplete, recording gear
Electronic Music tutorial: Making your own DAW templates
Store Written June 05 2011 , Tags: daw, templates, workflow
Making templates (in any form) is always a good time saver. So what makes a good template? One important aspect (and much overlooked) is to keep it open – meaning you should not add any colourisation that might not be needed. Sometimes it’s an important part of the work-flow, and you might have some distortion you end up putting on there anyway. Then of course it saves time.

A good example of a bad template is the standard FL studio template. On start up a template is loaded with some drum samples in the sequencer, each with their own fx channel. Nothing too fancy. But, there’s a limiter on the master channel. What a way to start. Fl sure chipped in their fair share of loudness war tactics.
So, be moderate with coloring fx, and stay away from dynamic crushing. A template is very useful for engineers and sound designer. But for musicians it can be a great time saver too. These days techniques are as much par of the sound of an artist as a hook or time signature. From extreme NY compression (sidechain) to dubstep wobbles (LFO). So all these interesting techniques require the same settings, for every project. Since they only modulate a parameter.

Setting Up Your Templates

Instead of spending time tweaking ghost parameters to set up a blank template from scratch, select some tracks that have good mixer routing settings. Make sure you the tracks are exemplary of the stuff you work on. I.e a dubstep template with reverb on 2 sends, a splitted kicks channel, a autofilter channel, or a media template with 5.1 surround settings. A recording template with a couple of alternative metronomes and your channel routed etc. I’ll keep this 100% DAW independent, but this stuff should translate pretty much 1:1.
Delete all audio and midi instruments etc. Clean any unwanted channels (delete or replace by>none). After the clean up all your audio and midi vsts should be gone and you are left with the routing that once made that project sound the way it sounds. The temptation is to leave those great fx chains in place. However, try to keep it to a minimum. Coloration, like mentioned before, is not wanted in abundance. Just the fundamentals. Otherwise you’ll miss out on sonic and creative ideas. Since you dont need to browse trough different fx, try different settings, you won’t get inspired and you’ll end up chasing that magic setting.
Rather make sure the chains are correctly EQ’ed, panned and that the dynamics are relative to the overall mix. This sounds as abstract as it is. That’s the inevitable with templates Just see this as a way to get rid of those standard DAW templates and have some proper time saving starting points. Using existing projects as basis.

Stages
Incorporating different stages in you work-flow is a much seen technique with electronic music production these says. Getting that huge sound involves re sampling and extensive tweaking. Using multiple stages in your templates allows you to speed up that process. To keep an eye on the feel of the song, you can load a mix of the sounds as a guide. Basically you work from a main template. Then you render loops and midi and load those in side projects with their own specialized template. This can be very useful when you want to do frequency splitting on 3 different drum loops and give each band their own extensive fx chain. So, if you feel like making lots of crazy bass edits with a lot of modulation on the synth and fx. Make a template that will exploit your cpu. Load in the midi from the main project and go from there.
Exemplary worklow
Main template – sketch (beats and meoldy mockup) [stage start]
Bass template – midi or audio from main (bass edits) [stage side]
Main template – incl new bass lines (resampling) [stage beta]
Drum template – fx chains on drum and perc groups (freq splitting etc) [stage side]
Main template – incl new drums and perc (mixing with bass etc) [stage beta]
Mastering – DIY Pre mastering engineering (setting your mix ) [stage done! ]

I hope this was useful guys, let me know how you do it, or if you have any suggestions/questions.
Comments
I dont use templates as much as I should. Tbh I rarely used things like resampling and separately processing drums and basslines as I was just using midi and not really using audio so much. Now I have a decent interface I'm recording my synths into live and using its processing power all the time to tweak my synth audio.
Doing all my processing in one place has meant some projects are killing my wee PC, its struggling to cope with all the effects chains and I'm having to freeze tracks and stuff to keep up. So I guess now is a good time to take your advice and setup some templates for doing that - having one for bass and one for drums etc sounds like a good idea, mental note - *must not be so lazy in future* Thanks for the insight mate.
I think your confusing channel save states with entire templates. Firstly deleting instruments, and MIDI channels? The whole purpose of a template is to have your studio setup already ready to go. Why should I clutter up the order of channels I have adding on my MIDI outs later, when I know I'm going to be using them at some point in the project? Perhaps you don't use much analog gear, but I'm always putting my modular to use on either bass lines, fx or add on parts.

In FL Studio the channel save states are found by RT clicking the channel name in the mixer window and selecting File > Open mixer track state, or Save mixer track state.

Like I was saying earlier, FL Studio has a channel feature called save state, which saves your current mixer channel effects, effect settings and volumes ect. You don't need a "mastering template" when you can simply save a save state of the mixer channel then depending on what your hunting for just load that up on the channel your working on.

For example, I have save states for my vocal effects which includes different eq / comp / reverb settings. I don't really use multiple mics but if I did I'm sure I would have different save states for each mic.
Cheers replicalix, glad you like it.

@chrisallen: I would be loading multiple channels states on multiple channels and I would still have cluttered projects after one cycle of resampling. Try to see it as a way to have a enhanced workflow for complex projects involving resampling etc.


Signup to comment
You must be a member to reply or post. signup or login