My Big Midi Template For Composing in Digital Performer

Tim Smolens shares his 100+ midi track template for composing in Digital Performer that contains all the basic instruments and synthesizers necessary for sketching out midi demos. Tim shares a demo sequence that scratches the surface of the template. This setup is also very CPU efficient and Tim shares how he accomplished this since so many virtual instruments these days take up a lot of RAM.
Please consider joining our conservatory on Patreon.
/ hccmusic
#midi #digitalperformer #motu ‪@motuTV‬ ‪@daviddas‬ #musicproduction #musicengineer #musiccomposer #daw

[@mihinimcjohnson]

Nice video! Can you do a video on the backend of this template? Routing and bussing and how to bounce to each stem to audio?

[@gleeb941]

I’m figuring out DP myself right now so this was a huge help and very entertaining

[@TimSmolens]

It is a deep program with a bit of a steep learning curve. Subscribe to my channel for more such lesson forthcoming.

[@Isabellaaskaan]

15:17 hey that's Telstar 😃

[@TebogoMotlhale]

if you were using Steinberg HALion as your sound-player pluign, it would be ONE plugin loaded, but shared by (Not just 16) but 64 completely separate Midi tracks, whereby EACH of these 64 completely separate midi tracks has the freedom to play its own/preferred sound out of the SINGLE HALion sound (VSTi) plugin.

[@DocBooger]

Cool stuff man! Those gain based plugins make a huge difference on an otherwise dull instrument plugin

[@Fuchsia_tude]

My Big Fat MIDI Template

[@TimSmolens]

I think I like your name better, perhaps I will change it to that!

[@raenoldparkin]

Noob question. Does bouncing a midi track down to audio track free up space? Example, of I have a Kontakt drum track I am happy with, and bouncing it do wave audio and deleting the midi track.

[@TimSmolens]

Well it doesn't free up space because the audio file is bigger than the midi file by a long shot, but it can free up RAM and processing power because it is no longer having to process the samples from that instrument. Does that makes sense?

[@pablogomez631]

When I read the title of the video, I thought it could help me solve the problems I am currently having with DP and my large template. But I quickly realized that the template on this video (100+ tracks) is actually not that big. My template includes more than 4000 midi tracks, and around 600 VIs (Kontakt, Opus, UVI, Sine, etc.). I was able to get all my strings and percussion libraries (the template file, “empty”, is already 2.2 Gb), but when I try to keep adding the other families, I get massive memory leaks (the RAM taken up surpasses 200 Gb on the Activity Monitor). If I don't "force quit" DP, the whole thing collapses and my iMac hard crashes. My system is 3.8 GHz 8-Core Intel Core i7, 128 Gb of RAM. Anyway, I will keep trying..

[@TimSmolens]

Yes I am aware that there are film composers and people such yourself that have much bigger templates and I should have probably not used the word huge. Lol. Unfortunately I think DP still has some major bugs to fix and I am hoping they get on it very quickly. Thanks for leaving comments and I hope you figure it out. On such a big template do you disable the virtual instruments you are not using in a particular sequence to free up RAM?

[@pablogomez631]

@@TimSmolens Yes. All VIs are disabled and all samples are purged. No audio tracks recorded. The template is completely empty. Its size corresponds merely to the empty midi tracks (routed and ready to go), and the VIs.