I have four templates, all of them exist only for speeding along the gainstaging and monitoring process. All of them have a spectrum analyzer and pre/post gain db meters, a disabled limiter for WIP rendering, and a dynamic range/loudness meter on the master. The first just has the faders on the first 30 channels turned down to -30 db with some gain as an insert on the master to compensate. The second is the same as the first, but with a console emulation set up on each channel and tied into the master properly for that plugin. The third and fourth are similar to the first two, but the gain on the master channel uses a bitshift gain that is more transparent, but less precise.
I used to have templates... helps if you forget things and saves time, but could limit your creative workflow and leaves less room for experimentation - It is a double edged blade but the most fun part of production is mixing it up... excuse the pun.
i know this is an old ass thread but i probably missed it.
i use a few templates, one for each of the potential jobs at hand.
they do not contain routing, sends, inserts e.t.c. (apart from on the master) though, since this changes every time for me. i use them to get my layout and settings where i want them.
the inserts on the master are utilities such as frequency analysers, meters e.t.c.
I wish I had some better templates.
I am realising again and again that anything that emulates an SSL console in use is helpful.
For a long time I used a template of plugins on my master, but lately I moved that to a group so I can leave a few items out of it. But that's very similar to doing DSP grouping on a console.
And the thing is, in sound engineering school they taught us how the SSL consoles were so advanced and people made so many hits on them. The only thing different about them besides just being good quality components was that there was a compressor/limiter in EACH channel! That may not sound amazing now, with computers, but back then that was astounding.
So now, what I'm going to do is create a track template where every track has everything it would need in a pro console plus some nice extras. I'm thinking like my best VST EQs, my best spectrum analysers, and my best limiter... all on each channel.
And then a few group channels designated for mono / bass LFE, and a different group buss for stereo front.
It's interesting to be essentially going back to classical mixing, almost. I'm kind of excited about this because I know it will work.
In DAW I like to have it all empty and basic to the core, similar to having a blank page in any text editor. But what I do is I make instrument/effect racks in Live with mapped macros. Super fun to drop an entire chain of something on a track and see what will happen, especially when I don't remember real origins of that effect rack but it's in my user library.
I use a template for Live, with 16 channels for Maschine and 4+1 Busses for Kick, Snare, Toms, Hats which go into a drum sum bus . Another busses for Basses, Synths, Samples, Guitar and Vocals. So I can make multitrack exports as Live backing tracks.
I think Live's default is a blank MIDI and blank audio track (somebody correct me if I'm retarded). I'm pretty sure all I've ever done is changed the MIDI to a drum rack to save an obvious step.
Experimenting with overwriting defaults (devices / effects included) is fun until it becomes impractical and you just want something basic, imo
can you not load from a selection of templates in live? in most DAWs you can, so you can have the complex template with devices and effects without writing over the basic "ground up" template.
a workaround would be to save the template as a project, as long as you dont accidentally ctrl+s over it