Page 1 of 3

Template Ideas

Posted: Sun Feb 28, 2016 4:40 pm
by PoliticalBonobo
I'm working on a creating a template project in DP9, so I can be faster and more efficient with my projects. However, I don't have a need (or desire) to simply have every plugin I own and every orchestral sample I own to be loaded. I prefer to only have the plugins and samples I want for the current project. This is what I was thinking:

-Create a V-Rack chunk for each plugin that uses samples or groups of samples (brass section, string quartet, etc.). I would only activate these chunks on an as-needed basis, or if working in another project I would Load the needed chunk.

-MIDI tracks will be routed to these V-Rack instruments and kept in folders in the Sequence

-Each track (audio, MIDI, and AUX) will be bussed to an audio track for final bouncing to be ready for mixing. It took me forever last project to go through and route/bounce all my tracks to prep for mixing. I might keep a "bank" of pre-routed audio tracks. My hope is to cut down on messing with busses entirely throughout a project.


Does anyone have any recommendations or better ideas? Again, I don't want to load every sample I own into every project.

Re: Template Ideas

Posted: Sun Feb 28, 2016 5:29 pm
by Henry Robinett
I have different templates for different uses. I have a songwriter template for constructing songs with VIs, Kontakt, Battery, Falcon, Superior Drummer, Ivory, etc and the associated MIDI set up, guitar and audio tracks set up. Then I have a template for recording lessons for students, another for recording my various bands live in the studio or remotely.

Set up is so time consuming. I have complicated headphone cue mixes that it saves a ton of time setting it up before hand.


All the best,
www.henryrobinett.com
Check out my latest CD on iTunes.
I Have Known Mountains by Henry Robinett
https://itun.es/us/pi6C_

Re: Template Ideas

Posted: Sun Feb 28, 2016 5:58 pm
by PoliticalBonobo
Henry Robinett wrote:I have different templates for different uses. I have a songwriter template for constructing songs with VIs, Kontakt, Battery, Falcon, Superior Drummer, Ivory, etc and the associated MIDI set up, guitar and audio tracks set up. Then I have a template for recording lessons for students, another for recording my various bands live in the studio or remotely.

Set up is so time consuming. I have complicated headphone cue mixes that it saves a ton of time setting it up before hand.
Thanks for the info. Do you load all of your VIs and libraries in that one songwriter template or do you have multiple songwriter templates?

Re: Template Ideas

Posted: Sun Feb 28, 2016 6:07 pm
by Henry Robinett
I have a few different songwriter templates. But mostly they're just saved updates. I have different interfaces and use multiple. I generally use three ULN-8, sometimes less. Sometimes I use Battery instead of SD. Or sometimes Steven Slate Drums.


All the best,
www.henryrobinett.com
Check out my latest CD on iTunes.
I Have Known Mountains by Henry Robinett
https://itun.es/us/pi6C_

Re: Template Ideas

Posted: Mon Feb 29, 2016 8:22 am
by bayswater
PoliticalBonobo wrote:-Create a V-Rack chunk for each plugin that uses samples or groups of samples (brass section, string quartet, etc.). I would only activate these chunks on an as-needed basis, or if working in another project I would Load the needed chunk.

-MIDI tracks will be routed to these V-Rack instruments and kept in folders in the Sequence

-Each track (audio, MIDI, and AUX) will be bussed to an audio track for final bouncing to be ready for mixing. It took me forever last project to go through and route/bounce all my tracks to prep for mixing. I might keep a "bank" of pre-routed audio tracks. My hope is to cut down on messing with busses entirely throughout a project.
That's pretty much how my templates ended up after a lot of attempts. The one thing I did differently to reduce clutter, is to route audio from VIs directly to an audio track for the bounce, rather than via an Aux. The audio tracks have to have monitoring mode on to make that work, and latency has to be low.

Not sure what you mean about not loading every sample you own. Would that even be possible with any modern library? I have most VIs in a V-Rack, all deactivated, but set up to load a few commonly used sounds when they are activated.

Re: Template Ideas

Posted: Mon Feb 29, 2016 5:28 pm
by PoliticalBonobo
What do you do if you have effects or processing on that audio track that's ready for bounce? When you record onto those tracks, won't you be missing those effects?

I assumed for most people's orchestral libraries that they have every instrument loaded. Maybe they do using only one articulation or something.

Re: Template Ideas

Posted: Mon Feb 29, 2016 6:33 pm
by bayswater
PoliticalBonobo wrote:What do you do if you have effects or processing on that audio track that's ready for bounce? When you record onto those tracks, won't you be missing those effects?
Short answer is I don't. Apply effects to the VI outputs before rendering to audio. I use this setup to get a final set of dry audio tracks, and then apply effects while mixing.
PoliticalBonobo wrote: I assumed for most people's orchestral libraries that they have every instrument loaded. Maybe they do using only one articulation or something.
I'm probably not understanding what you mean. I don't load up instruments I'm not using.

Re: Template Ideas

Posted: Wed Mar 16, 2016 6:50 pm
by PoliticalBonobo
bayswater wrote:
PoliticalBonobo wrote:What do you do if you have effects or processing on that audio track that's ready for bounce? When you record onto those tracks, won't you be missing those effects?
Short answer is I don't. Apply effects to the VI outputs before rendering to audio. I use this setup to get a final set of dry audio tracks, and then apply effects while mixing.
PoliticalBonobo wrote: I assumed for most people's orchestral libraries that they have every instrument loaded. Maybe they do using only one articulation or something.
I'm probably not understanding what you mean. I don't load up instruments I'm not using.
One thing I'm worrying about running into as I create template V-Racks is bussing. How do you manage bussing? I'm wondering how it's going to work when I load V-Racks (say drums) but have already filled up my busses because of templates.

Re: Template Ideas

Posted: Wed Mar 16, 2016 7:27 pm
by bayswater
V-Racks don't change the way you do bussing. Run busses from VIs and to and from tracks and Auxes just as you would if these objects were not in a V-Rack. Naming the busses in the Bundles window helps keep track of them. Just set up bussing in the template, then turn off the V-Rack in the Chunks window before saving as a template.

Re: Template Ideas

Posted: Wed Mar 16, 2016 7:35 pm
by PoliticalBonobo
bayswater wrote:V-Racks don't change the way you do bussing. Run busses from VIs and to and from tracks and Auxes just as you would if these objects were not in a V-Rack. Naming the busses in the Bundles window helps keep track of them. Just set up bussing in the template, then turn off the V-Rack in the Chunks window before saving as a template.
That's pretty much what I've been doing, but I'm worried about running out of busses. I've almost used all of them between pianos, quartet, and guitars v-racks (with 2 send tracks in each v-rack). What happens when I am in this project template and want to add say, a drums V-Rack? I could be overthinking this....

Re: Template Ideas

Posted: Wed Mar 16, 2016 8:07 pm
by FMiguelez
PoliticalBonobo wrote: That's pretty much what I've been doing, but I'm worried about running out of busses. I've almost used all of them between pianos, quartet, and guitars v-racks (with 2 send tracks in each v-rack). What happens when I am in this project template and want to add say, a drums V-Rack? I could be overthinking this....
Really?

How many busses are you using now? Are you using DP's maximum allowed?

If you are, then you might need to rethink your bussing and overall signal structure :?

Re: Template Ideas

Posted: Wed Mar 16, 2016 8:29 pm
by PoliticalBonobo
I'm up to 52 busses out of 64! (That's the max, right?)
I have pianos and string quartet routed through VEP, and each instrument going to an aux than an final audio track (for final bouncing). So that's 2 busses (stereo) each instrument, followed by busses to auxes, followed by busses to the final audio tracks.
64 busses is really only 32 stereo tracks, which doesn't seem like THAT much when factoring aux's and sends and such.

Re: Template Ideas

Posted: Wed Mar 16, 2016 8:33 pm
by bayswater
PoliticalBonobo wrote:I'm up to 52 busses out of 64! (That's the max, right?)
I have pianos and string quartet routed through VEP, and each instrument going to an aux than an final audio track (for final bouncing). So that's 2 busses (stereo) each instrument, followed by busses to auxes, followed by busses to the final audio tracks.
64 busses is really only 32 stereo tracks, which doesn't seem like THAT much when factoring aux's and sends and such.
No, the max is not 64. See the web site section on specs.

Maximum mono busses: 198
Maximum stereo busses: 99

Re: Template Ideas

Posted: Wed Mar 16, 2016 8:52 pm
by FMiguelez
PoliticalBonobo wrote:I'm up to 52 busses out of 64! (That's the max, right?)
I have pianos and string quartet routed through VEP, and each instrument going to an aux than an final audio track (for final bouncing).
There's your culprit right there. You're duplicating and using redundant bundles because of the aux tracks. Why don't you buss VEP directly to audio tracks instead? Muuuuuuch easier and efficient!

Re: Template Ideas

Posted: Wed Mar 16, 2016 9:25 pm
by PoliticalBonobo
FMiguelez wrote: There's your culprit right there. You're duplicating and using redundant bundles because of the aux tracks. Why don't you buss VEO directly to audio tracks instead? Muuuuuuch easier and efficient!
I guess I'll do it that way. The only thing is I won't be able to bounce with tracks with effects/processing applied, since those will be on the audio tracks :(